@rosetears/aili-pi 0.1.0

package/skills/minimax-xlsx/templates/minimal_xlsx/xl/styles.xml

@@ -0,0 +1,160 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<!--
+  styles.xml — The complete style system for this workbook.
+
+  Style index (cellXfs) lookup table:
+  ┌───────┬─────────────────────────────────┬────────────────┬───────────────────┐
+  │ Index │ Semantic Role                   │ Font Color     │ Number Format     │
+  ├───────┼─────────────────────────────────┼────────────────┼───────────────────┤
+  │   0   │ Default                         │ Theme (black)  │ General           │
+  │   1   │ Input / Assumption              │ Blue 000000FF  │ General           │
+  │   2   │ Formula / Computed result       │ Black 00000000 │ General           │
+  │   3   │ Cross-sheet reference           │ Green 00008000 │ General           │
+  │   4   │ Header (bold)                   │ Black bold     │ General           │
+  │   5   │ Currency input                  │ Blue 000000FF  │ $#,##0 (id=164)   │
+  │   6   │ Currency formula                │ Black          │ $#,##0 (id=164)   │
+  │   7   │ Percentage input                │ Blue 000000FF  │ 0.0% (id=165)     │
+  │   8   │ Percentage formula              │ Black          │ 0.0% (id=165)     │
+  │   9   │ Integer with commas input       │ Blue 000000FF  │ #,##0 (id=167)    │
+  │  10   │ Integer with commas formula     │ Black          │ #,##0 (id=167)    │
+  │  11   │ Year (no comma) — input         │ Blue 000000FF  │ 0 (id=1)          │
+  │  12   │ Key assumption (yellow bg)      │ Blue 000000FF  │ General + yellow  │
+  └───────┴─────────────────────────────────┴────────────────┴───────────────────┘
+
+  To add a new style:
+  1. If needed, add a <numFmt> to <numFmts> with a new numFmtId >= 164 (increment max)
+  2. If needed, add a <font> to <fonts>
+  3. If needed, add a <fill> to <fills>
+  4. Append a new <xf> to <cellXfs>, combining fontId + fillId + numFmtId
+  5. Update the count attributes on <numFmts>, <fonts>, <fills>, <cellXfs>
+  6. The new xf's index = (old cellXfs count) — use this as the s attribute on cells
+
+  CRITICAL RULES:
+  - fills[0] and fills[1] are REQUIRED BY SPEC — never remove them
+  - Do NOT modify existing <xf> entries — only append new ones
+  - AARRGGBB color format: first 2 hex digits = Alpha (00 = opaque)
+-->
+<styleSheet xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main">
+
+  <!-- ── Number Formats ─────────────────────────────────────────────────── -->
+  <!-- Built-in IDs 0-163 need NOT be declared here. Custom formats: 164+  -->
+  <numFmts count="4">
+    <!-- 164: Standard currency — positive $1,234 / negative ($1,234) / zero - -->
+    <numFmt numFmtId="164" formatCode="$#,##0;($#,##0);&quot;-&quot;"/>
+    <!-- 165: Percentage with 1 decimal place -->
+    <numFmt numFmtId="165" formatCode="0.0%"/>
+    <!-- 166: Multiplier / ratio (e.g. 8.5x for EV/EBITDA) -->
+    <numFmt numFmtId="166" formatCode="0.0x"/>
+    <!-- 167: Integer with thousands separator, no decimals -->
+    <numFmt numFmtId="167" formatCode="#,##0"/>
+  </numFmts>
+
+  <!-- ── Fonts ──────────────────────────────────────────────────────────── -->
+  <fonts count="5">
+    <!-- 0: Default (theme color, no explicit color) -->
+    <font>
+      <sz val="11"/>
+      <name val="Calibri"/>
+    </font>
+    <!-- 1: Input / Assumption — Blue -->
+    <font>
+      <sz val="11"/>
+      <name val="Calibri"/>
+      <color rgb="000000FF"/>
+    </font>
+    <!-- 2: Formula / Computed result — Black (explicit) -->
+    <font>
+      <sz val="11"/>
+      <name val="Calibri"/>
+      <color rgb="00000000"/>
+    </font>
+    <!-- 3: Cross-sheet reference — Green -->
+    <font>
+      <sz val="11"/>
+      <name val="Calibri"/>
+      <color rgb="00008000"/>
+    </font>
+    <!-- 4: Header — Bold Black -->
+    <font>
+      <b/>
+      <sz val="11"/>
+      <name val="Calibri"/>
+      <color rgb="00000000"/>
+    </font>
+  </fonts>
+
+  <!-- ── Fills ──────────────────────────────────────────────────────────── -->
+  <!-- fills[0] and fills[1] are REQUIRED by OOXML spec — DO NOT REMOVE -->
+  <fills count="3">
+    <fill><patternFill patternType="none"/></fill>
+    <fill><patternFill patternType="gray125"/></fill>
+    <!-- 2: Yellow highlight for key assumptions requiring review -->
+    <fill>
+      <patternFill patternType="solid">
+        <fgColor rgb="00FFFF00"/>
+        <bgColor indexed="64"/>
+      </patternFill>
+    </fill>
+  </fills>
+
+  <!-- ── Borders ────────────────────────────────────────────────────────── -->
+  <borders count="1">
+    <!-- 0: No borders (default) -->
+    <border>
+      <left/>
+      <right/>
+      <top/>
+      <bottom/>
+      <diagonal/>
+    </border>
+  </borders>
+
+  <!-- ── Cell Style Xfs (base styles) ──────────────────────────────────── -->
+  <cellStyleXfs count="1">
+    <xf numFmtId="0" fontId="0" fillId="0" borderId="0"/>
+  </cellStyleXfs>
+
+  <!-- ── Cell Xfs (the actual style slots referenced by <c s="N">) ──────── -->
+  <cellXfs count="13">
+    <!--  0: Default -->
+    <xf numFmtId="0" fontId="0" fillId="0" borderId="0" xfId="0"/>
+    <!--  1: Input / Assumption (blue, general format) -->
+    <xf numFmtId="0" fontId="1" fillId="0" borderId="0" xfId="0" applyFont="1"/>
+    <!--  2: Formula / Computed (black, general format) -->
+    <xf numFmtId="0" fontId="2" fillId="0" borderId="0" xfId="0" applyFont="1"/>
+    <!--  3: Cross-sheet reference (green, general format) -->
+    <xf numFmtId="0" fontId="3" fillId="0" borderId="0" xfId="0" applyFont="1"/>
+    <!--  4: Header (bold black) -->
+    <xf numFmtId="0" fontId="4" fillId="0" borderId="0" xfId="0" applyFont="1"/>
+    <!--  5: Currency input (blue + $#,##0) -->
+    <xf numFmtId="164" fontId="1" fillId="0" borderId="0" xfId="0"
+        applyFont="1" applyNumberFormat="1"/>
+    <!--  6: Currency formula (black + $#,##0) -->
+    <xf numFmtId="164" fontId="2" fillId="0" borderId="0" xfId="0"
+        applyFont="1" applyNumberFormat="1"/>
+    <!--  7: Percentage input (blue + 0.0%) -->
+    <xf numFmtId="165" fontId="1" fillId="0" borderId="0" xfId="0"
+        applyFont="1" applyNumberFormat="1"/>
+    <!--  8: Percentage formula (black + 0.0%) -->
+    <xf numFmtId="165" fontId="2" fillId="0" borderId="0" xfId="0"
+        applyFont="1" applyNumberFormat="1"/>
+    <!--  9: Integer-with-commas input (blue + #,##0) -->
+    <xf numFmtId="167" fontId="1" fillId="0" borderId="0" xfId="0"
+        applyFont="1" applyNumberFormat="1"/>
+    <!-- 10: Integer-with-commas formula (black + #,##0) -->
+    <xf numFmtId="167" fontId="2" fillId="0" borderId="0" xfId="0"
+        applyFont="1" applyNumberFormat="1"/>
+    <!-- 11: Year column input (blue + plain integer "0", no comma) -->
+    <xf numFmtId="1" fontId="1" fillId="0" borderId="0" xfId="0"
+        applyFont="1" applyNumberFormat="1"/>
+    <!-- 12: Key assumption highlight (blue on yellow — needs human review) -->
+    <xf numFmtId="0" fontId="1" fillId="2" borderId="0" xfId="0"
+        applyFont="1" applyFill="1"/>
+  </cellXfs>
+
+  <!-- ── Named Cell Styles ─────────────────────────────────────────────── -->
+  <cellStyles count="1">
+    <cellStyle name="Normal" xfId="0" builtinId="0"/>
+  </cellStyles>
+
+</styleSheet>

package/skills/minimax-xlsx/templates/minimal_xlsx/xl/workbook.xml

@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<!--
+  workbook.xml — Defines the list of sheets.
+
+  To add a new sheet:
+    1. Add a <sheet> element below with a unique sheetId and r:id
+    2. Add a matching <Relationship> in xl/_rels/workbook.xml.rels
+    3. Add an <Override> in [Content_Types].xml
+    4. Create the xl/worksheets/sheetN.xml file
+
+  Sheet name rules:
+    - Max 31 characters
+    - Cannot contain: / \ ? * [ ] :
+    - Ampersand must be escaped as &amp; in XML
+-->
+<workbook
+  xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"
+  xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships">
+  <fileVersion appName="xl" lastEdited="7" lowestEdited="7"/>
+  <workbookPr defaultThemeVersion="166925"/>
+  <bookViews>
+    <workbookView xWindow="0" yWindow="0" windowWidth="20140" windowHeight="10960"/>
+  </bookViews>
+  <sheets>
+    <!-- Add more <sheet> elements here for multi-sheet workbooks -->
+    <sheet name="Sheet1" sheetId="1" r:id="rId1"/>
+  </sheets>
+  <!-- calcId ensures Excel recalculates formulas on open -->
+  <calcPr calcId="191029"/>
+</workbook>

package/skills/minimax-xlsx/templates/minimal_xlsx/xl/worksheets/sheet1.xml

@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
+<!--
+  sheet1.xml — Worksheet data.
+
+  Cell anatomy:
+    <c r="A1" t="s" s="4"><v>0</v></c>
+          ↑      ↑   ↑    ↑
+      address  type  style  value (sharedStrings index for t="s")
+
+  Type values (t attribute):
+    s          = shared string (text) — <v> contains index into sharedStrings.xml
+    inlineStr  = inline string — use <is><t>text</t></is> instead of <v>
+    n (or omit)= number — <v> contains the raw number
+    b          = boolean — <v> is 1 (TRUE) or 0 (FALSE)
+    e          = error — <v> contains error string like #REF!
+    (no t)     = formula cell — <f> contains formula (NO leading =), <v> is cache
+
+  Formula cells:
+    <c r="B5" s="2"><f>SUM(B2:B4)</f><v></v></c>
+    Cross-sheet: <c r="C1" s="3"><f>Assumptions!B2</f><v></v></c>
+    With spaces:  <c r="C1" s="3"><f>'Q1 Data'!B2</f><v></v></c>
+
+  Style index (s attribute) — pre-built in styles.xml:
+    0 = default
+    1 = input/assumption (blue font)
+    2 = formula/computed (black font)
+    3 = cross-sheet reference (green font)
+    4 = header bold
+    5 = currency input (blue + $#,##0 format)
+    See styles.xml for the full list and how to add more.
+
+  Row r attribute must be 1-based integer.
+  Column letters: A=1, Z=26, AA=27, AZ=52, BA=53, BZ=78, etc.
+-->
+<worksheet
+  xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main"
+  xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships">
+  <sheetViews>
+    <sheetView tabSelected="1" workbookViewId="0">
+      <!-- Freeze top row as header: -->
+      <!-- <pane ySplit="1" topLeftCell="A2" activePane="bottomLeft" state="frozen"/> -->
+    </sheetView>
+  </sheetViews>
+  <sheetFormatPr defaultRowHeight="15" x14ac:dyDescent="0.25"
+    xmlns:x14ac="http://schemas.microsoft.com/office/spreadsheetml/2009/9/ac"/>
+  <!-- Column widths — uncomment and adjust as needed:
+  <cols>
+    <col min="1" max="1" width="24" customWidth="1"/>
+    <col min="2" max="10" width="14" customWidth="1"/>
+  </cols>
+  -->
+  <sheetData>
+    <!-- Replace this placeholder with actual data rows.
+         Example:
+    <row r="1">
+      <c r="A1" t="s" s="4"><v>0</v></c>
+      <c r="B1" t="s" s="4"><v>1</v></c>
+    </row>
+    <row r="2">
+      <c r="A2" t="s" s="1"><v>2</v></c>
+      <c r="B2" s="1"><v>1000</v></c>
+    </row>
+    <row r="3">
+      <c r="A3" t="s" s="2"><v>3</v></c>
+      <c r="B3" s="2"><f>B2*1.1</f><v></v></c>
+    </row>
+    -->
+  </sheetData>
+  <pageMargins left="0.7" right="0.7" top="0.75" bottom="0.75" header="0.3" footer="0.3"/>
+</worksheet>

package/skills/newsletter-generation/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: newsletter-generation
+description: Generate or edit a source-grounded newsletter issue, digest, or briefing from provided or researched sources. Use for weekly/monthly updates, curated links, executive digests, community newsletters, or "turn these sources into a newsletter"; do not use for UI landing pages, marketing campaign design, unsourced news claims, or long-form research reports.
+---
+
+# Newsletter Generation
+
+## Purpose
+
+Turn source material into a concise, useful newsletter that has a clear audience, editorial angle, attribution, and fact boundaries.
+
+## When to Use
+
+Use for:
+
+- weekly/monthly newsletters, digest emails, link roundups, or executive briefings
+- summarizing a set of URLs, release notes, issues, papers, meeting notes, or user-provided bullets
+- creating an editorial structure: subject line, intro, sections, summaries, calls to action, and source list
+
+Do not use for:
+
+- building the visual landing page or email UI; use frontend/design skills as appropriate
+- deep academic/systematic reviews; use `systematic-literature-review`
+- unsourced breaking-news claims or fake quotes
+- sending email, subscribing users, or managing mailing-list provider configuration
+
+## Workflow
+
+1. Identify audience, purpose, tone, cadence, length, and required sections.
+2. Inventory sources and mark their type: official update, primary document, issue/PR, paper, meeting note, user-provided note, or secondary article.
+3. Verify key facts against primary sources when practical. Do not turn weak evidence into confident news.
+4. Choose an editorial angle that explains why the issue matters to the audience.
+5. Synthesize related items into themes; avoid one bullet per source unless the user asked for a link list.
+6. Draft with concrete headlines, short summaries, clear attribution, and explicit calls to action.
+7. Include an `Unverified / Needs follow-up` section for claims, links, dates, or numbers not checked.
+
+## Quality Rules
+
+- No fabricated quotes, dates, metrics, product names, event details, sponsorships, or endorsements.
+- Use realistic copy, not filler text.
+- Distinguish editorial interpretation from source facts.
+- Keep source links visible unless the user requests a no-link internal memo.
+
+## Output Contract
+
+```text
+STATUS: DRAFTED | PARTIAL | BLOCKED
+
+AUDIENCE / GOAL:
+- <who this is for and what action/understanding it should create>
+
+ISSUE DRAFT:
+- Subject:
+- Preview:
+- Intro:
+- Sections:
+- Closing / CTA:
+
+SOURCES USED:
+- <source> - <what it supports>
+
+EDITORIAL NOTES:
+- <tone, angle, cuts, or assumptions>
+
+UNVERIFIED:
+- <unchecked claim/source/date or N/A>
+```
+
+## Provenance
+
+Clean-room AILI/OpenCode adaptation inspired by the public DeerFlow `newsletter-generation` skill pattern. No upstream skill text, runtime paths, tools, generated assets, provider configuration, or mailing-service assumptions are copied. Source family: [bytedance/deer-flow](https://github.com/bytedance/deer-flow), MIT License.

package/skills/oss-release-readiness/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: oss-release-readiness
+description: Run a non-destructive open-source, npm, or public release readiness checklist covering package metadata, provenance, license, internal artifact exposure, and dry-run evidence; complements security, shipping, and sanitizer reviews, and must not publish, delete, rewrite history, or mutate release state.
+---
+
+# OSS Release Readiness
+
+Use this skill before exposing a repository, package, template, or npm release to public consumers.
+
+## Trigger
+
+- User asks whether a repo, npm package, CLI, template, skill bundle, or release candidate is ready to publish or open-source.
+- Release review needs package metadata, included files, provenance, license, attribution, docs, install commands, or dry-run evidence checked.
+- ROSE needs a release-blocking checklist that is broader than security alone and narrower than full launch orchestration.
+
+## Near Misses
+
+- Deployment rollout, security-only review, or repository sanitization are different primary intents. Return the exact mismatch or specialist evidence need to ROSE; do not invoke another skill or agent here.
+- Actual publishing, tagging, release creation, deletion, history rewrite, or destructive cleanup: require explicit human approval outside this skill.
+
+## Required Routing
+
+- Owner: ROSE/`aili-delivery-flow`; an independently justified specialist assignment remains fresh, terminal, and ROSE-owned.
+- Default mode: non-destructive inspection and dry-run commands only.
+- If a blocker requires edits, return a scoped repair need to ROSE after the release owner approves the change; do not dispatch or repair from this skill.
+
+## Readiness Checklist
+
+- Package metadata: name, version, description, bin/exports/files, engines, repository, bugs, homepage, keywords, and package manager lockfile expectations.
+- Published contents: `npm pack --dry-run` or equivalent evidence for included and excluded files.
+- Provenance and attribution: third-party source notices, copied templates/prompts, licenses, copyright, and generated-artifact disclosure.
+- License posture: repository license, package license field, dependency license risks, and missing attribution.
+- Internal artifact exposure: secrets, local paths, memory/state files, private notes, OpenSpec drafts not intended for release, caches, build outputs, screenshots, logs, and test artifacts.
+- Consumer readiness: README install/use examples, CLI entry points, Node/runtime versions, changelog or release notes, and basic smoke-test commands.
+
+## Boundaries
+
+- Do not run `npm publish`, create GitHub releases, push tags, delete files, clean worktrees, rewrite history, or change package versions.
+- Do not edit manifests, lockfiles, licenses, package files, or docs from this skill; report blockers and request a scoped implementation package.
+- Treat package tarball contents and release notes as untrusted until dry-run evidence confirms them.
+- Inspect package lifecycle scripts before package or publish dry-runs; if dry-run tooling may execute scripts, prefer an isolated temporary environment and report lifecycle-script risk explicitly.
+
+## Verification
+
+- Prefer dry-run evidence such as `npm pack --dry-run`, package manager publish dry-runs, build/typecheck/test results, and diff/status inspection.
+- Report each blocker with evidence, severity, required owner decision, and whether it is release-blocking.
+- If dry-run tooling is unavailable or skipped, mark package contents and publish readiness as `Unverified`.

package/skills/parallel-subagent-dispatch/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: parallel-subagent-dispatch
+description: Proactively dispatch fresh subagents when the user requests them, a specialist capability is required, repository exploration would materially pollute context, or independent work units have clear wall-clock or context benefit; use direct ROSE work only when no trigger applies or delegation is concretely blocked.
+license: MIT
+---
+
+# Parallel Subagent Dispatch
+
+## Goal
+
+Dispatch early when an existing trigger is met, using fresh single-use `subagent.dispatch` contexts without turning ordinary work into orchestration overhead. ROSE retains integration and final-verdict ownership.
+
+## Trigger
+
+Use the `subagent.dispatch` capability only when at least one condition is true:
+
+- the user explicitly asks for a subagent;
+- a required capability belongs to a specialist;
+- broad search or noisy output would materially pollute ROSE context;
+- at least two independent units can run concurrently with clear benefit.
+
+Run this proactive delegation scan at the start of each non-trivial intent and again when changed evidence creates a new work split. When any trigger is true, dispatch before duplicating the assignment directly unless overlap, dependency, permission, ownership, or negative-benefit evidence blocks it. Otherwise work directly. Do not delegate a single straightforward task merely because a subagent exists.
+
+Every dispatch operation must pass this benefit decision independently. A prior failure, partial result, empty result, or desire to continue is not by itself a reason to dispatch another operation.
+
+## Parallelism
+
+- Default to at most two concurrent subagents; this is not a hard cap. ROSE may select a larger bounded fan-out when every lane is independent and non-overlapping, has concrete benefit and a suitable owner, and participates in an explicit join plan.
+- Launch ready independent lanes together in the same Task message when the current adapter maps `subagent.dispatch` to Task; otherwise use its equivalent single dispatch batch rather than serializing them.
+- Parallel units must not edit the same files or depend on each other's output.
+- If work overlaps or has a dependency, run it sequentially or keep it direct.
+- Do not automatically add review, test, security, or coverage agents after implementation.
+
+## Single-use sessions
+
+- Each dispatch context receives one bounded assignment and ends permanently with one terminal result or failure.
+- Never resume an old `task_id` for follow-up, clarification, continuation, repair, recheck, or additional work.
+- Do not automatically retry in a fresh session after a failed, empty, blocked, or partial result; ROSE handles the bounded gap directly or reports the blocker.
+- The same subagent role may be selected later only in a fresh dispatch invocation with no resumed context, after a fresh trigger-and-benefit decision for an independently justified assignment or changed evidence.
+- Subagents never nest or delegate. ROSE retains lifecycle, approval, integration, reconciliation, and final-verdict ownership.
+
+## Canonical packet protocol
+
+Use `.agents/skills/aili-delivery-flow/references/protocols/subagent-task-packet.md` as the single source for exact packet fields and rules. Do not restate or maintain a local field schema in this skill.
+
+Keep each packet bounded to the independently justified assignment. A packet narrows scope; it never expands effective permissions. Every subagent remains non-delegating.
+
+For A33, a packet/result carries one compact `WT-001` reference for one declared repository/cwd. It never duplicates or rebinds root, key, identity, Git, approval, operation, risk, delta, rule, command/cwd, or containment authority. Target rules are re-read at dispatch, can only narrow, and same-level conflicts block. Artifacts stay with the owning target repository.
+
+## Canonical result protocol
+
+Use `.agents/skills/aili-delivery-flow/references/protocols/subagent-result.md` as the single source for exact terminal result and finding fields. Do not restate or maintain a local result schema in this skill.
+
+ROSE checks the canonical result evidence, resolves conflicts, and owns the lifecycle, integration, and final decision. Missing or empty evidence is not completion and does not authorize resume or an automatic fresh-session retry.
+
+## Stop
+
+Do not dispatch when permission, scope, ownership, or independence is unclear. Ask the user only when the missing answer changes the task or authorization.