@oriro/orirocli 0.1.8 → 0.1.11

package/skills/coding-agent/SKILL.md

@@ -1,146 +1,146 @@
----
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-watermark: ORIRO
-name: coding-agent
-description: "Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup."
-metadata:
-  {
-    "oriro":
-      {
-        "emoji": "🧩",
-        "requires":
-          {
-            "anyBins": ["claude", "codex", "opencode"],
-            "config": ["skills.entries.coding-agent.enabled"],
-          },
-        "install":
-          [
-            {
-              "id": "node-claude",
-              "kind": "node",
-              "package": "@anthropic-ai/claude-code",
-              "bins": ["claude"],
-              "label": "Install Claude Code CLI (npm)",
-            },
-            {
-              "id": "node-codex",
-              "kind": "node",
-              "package": "@openai/codex",
-              "bins": ["codex"],
-              "label": "Install Codex CLI (npm)",
-            },
-          ],
-      },
-  }
----
-
-# Coding Agent
-
-Use for background feature builds, PR reviews, large refactors, and issue-to-PR loops. Do not use for simple edits, read-only lookup, ACP thread-bound work, or any run inside `~/.oriro`, `$ORIRO_STATE_DIR`, or active Oriro state dirs.
-
-## Hard rules
-
-- Always launch with `background:true`.
-- Codex and OpenCode: use `pty:true`.
-- Claude Code: no PTY; use `claude --permission-mode bypassPermissions --print`.
-- Capture a real notification route before spawning.
-- Worker must send completion/failure via `oriro message send`.
-- Do not rely on heartbeat, system events, or notify-on-exit.
-- Monitor with `process`; do not kill slow workers without cause.
-- If user asked for a specific agent, use that agent.
-- If worker fails/hangs, respawn or ask; do not silently hand-code instead.
-- Never checkout branches or run background coding agents in `~/Projects/oriro`; use an isolated checkout.
-
-## Notification block
-
-Append this shape to every worker prompt with real values:
-
-```text
-Notification route:
-- channel: <notifyChannel>
-- target: <notifyTarget>
-- account: <notifyAccount or omit>
-- reply_to: <notifyReplyTo or omit>
-- thread_id: <notifyThreadId or omit>
-
-When finished, send exactly one completion or failure message using:
-oriro message send --channel <channel> --target '<target>' --message '<brief result>'
-Add --account, --reply-to, or --thread-id only when present above.
-Do not use oriro system event or heartbeat.
-```
-
-If no trustworthy route exists, say completion auto-notify is unavailable.
-
-## Launch forms
-
-Write the worker prompt to a temp file first. This avoids shell quoting bugs when the required notification block contains quotes or newlines.
-
-```bash
-PROMPT=$(mktemp -t oriro-worker-prompt.XXXXXX)
-cat >"$PROMPT" <<'EOF'
-Task.
-<notification block>
-EOF
-printf 'prompt file: %s\n' "$PROMPT"
-```
-
-Use `$PROMPT` when launching from the same shell/session. If using a separate tool call, substitute the printed path.
-
-Codex:
-
-```bash
-bash pty:true background:true workdir:/path/repo command:"codex exec - < \"$PROMPT\""
-```
-
-Claude Code:
-
-```bash
-bash background:true workdir:/path/repo command:"claude --permission-mode bypassPermissions --print < \"$PROMPT\""
-```
-
-OpenCode:
-
-```bash
-bash pty:true background:true workdir:/path/repo command:"opencode run < \"$PROMPT\""
-```
-
-## Long issue-to-PR work
-
-1. Create/reuse a GitHub issue as durable spec.
-2. Include issue URL, repo, base branch, expected PR, proof, and notification route.
-3. Tell worker to branch, implement, test, run review until no accepted actionable findings, open PR.
-4. Return issue URL and `sessionId` immediately.
-5. Monitor with `process`; cancel through Task Registry if mirrored there.
-
-## Scratch Codex
-
-Codex needs a trusted git repo:
-
-```bash
-SCRATCH=$(mktemp -d)
-git -C "$SCRATCH" init
-PROMPT=$(mktemp -t oriro-worker-prompt.XXXXXX)
-cat >"$PROMPT" <<'EOF'
-Build X.
-<notification block>
-EOF
-printf 'prompt file: %s\n' "$PROMPT"
-bash pty:true background:true workdir:$SCRATCH command:"codex exec - < \"$PROMPT\""
-```
-
-## Process actions
-
-- `list`: running/recent sessions.
-- `poll`: status.
-- `log`: output.
-- `submit`: send input + Enter.
-- `write`: raw stdin.
-- `paste`: paste text.
-- `kill`: terminate.
-
-## Status to user
-
-- Say what started, where, and `sessionId`.
-- Update only on milestone, worker question, error, user action needed, or finish.
-- If killed, say why.
+---
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+watermark: ORIRO
+name: coding-agent
+description: "Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup."
+metadata:
+  {
+    "oriro":
+      {
+        "emoji": "🧩",
+        "requires":
+          {
+            "anyBins": ["claude", "codex", "opencode"],
+            "config": ["skills.entries.coding-agent.enabled"],
+          },
+        "install":
+          [
+            {
+              "id": "node-claude",
+              "kind": "node",
+              "package": "@anthropic-ai/claude-code",
+              "bins": ["claude"],
+              "label": "Install Claude Code CLI (npm)",
+            },
+            {
+              "id": "node-codex",
+              "kind": "node",
+              "package": "@openai/codex",
+              "bins": ["codex"],
+              "label": "Install Codex CLI (npm)",
+            },
+          ],
+      },
+  }
+---
+
+# Coding Agent
+
+Use for background feature builds, PR reviews, large refactors, and issue-to-PR loops. Do not use for simple edits, read-only lookup, ACP thread-bound work, or any run inside `~/.oriro`, `$ORIRO_STATE_DIR`, or active Oriro state dirs.
+
+## Hard rules
+
+- Always launch with `background:true`.
+- Codex and OpenCode: use `pty:true`.
+- Claude Code: no PTY; use `claude --permission-mode bypassPermissions --print`.
+- Capture a real notification route before spawning.
+- Worker must send completion/failure via `oriro message send`.
+- Do not rely on heartbeat, system events, or notify-on-exit.
+- Monitor with `process`; do not kill slow workers without cause.
+- If user asked for a specific agent, use that agent.
+- If worker fails/hangs, respawn or ask; do not silently hand-code instead.
+- Never checkout branches or run background coding agents in `~/Projects/oriro`; use an isolated checkout.
+
+## Notification block
+
+Append this shape to every worker prompt with real values:
+
+```text
+Notification route:
+- channel: <notifyChannel>
+- target: <notifyTarget>
+- account: <notifyAccount or omit>
+- reply_to: <notifyReplyTo or omit>
+- thread_id: <notifyThreadId or omit>
+
+When finished, send exactly one completion or failure message using:
+oriro message send --channel <channel> --target '<target>' --message '<brief result>'
+Add --account, --reply-to, or --thread-id only when present above.
+Do not use oriro system event or heartbeat.
+```
+
+If no trustworthy route exists, say completion auto-notify is unavailable.
+
+## Launch forms
+
+Write the worker prompt to a temp file first. This avoids shell quoting bugs when the required notification block contains quotes or newlines.
+
+```bash
+PROMPT=$(mktemp -t oriro-worker-prompt.XXXXXX)
+cat >"$PROMPT" <<'EOF'
+Task.
+<notification block>
+EOF
+printf 'prompt file: %s\n' "$PROMPT"
+```
+
+Use `$PROMPT` when launching from the same shell/session. If using a separate tool call, substitute the printed path.
+
+Codex:
+
+```bash
+bash pty:true background:true workdir:/path/repo command:"codex exec - < \"$PROMPT\""
+```
+
+Claude Code:
+
+```bash
+bash background:true workdir:/path/repo command:"claude --permission-mode bypassPermissions --print < \"$PROMPT\""
+```
+
+OpenCode:
+
+```bash
+bash pty:true background:true workdir:/path/repo command:"opencode run < \"$PROMPT\""
+```
+
+## Long issue-to-PR work
+
+1. Create/reuse a GitHub issue as durable spec.
+2. Include issue URL, repo, base branch, expected PR, proof, and notification route.
+3. Tell worker to branch, implement, test, run review until no accepted actionable findings, open PR.
+4. Return issue URL and `sessionId` immediately.
+5. Monitor with `process`; cancel through Task Registry if mirrored there.
+
+## Scratch Codex
+
+Codex needs a trusted git repo:
+
+```bash
+SCRATCH=$(mktemp -d)
+git -C "$SCRATCH" init
+PROMPT=$(mktemp -t oriro-worker-prompt.XXXXXX)
+cat >"$PROMPT" <<'EOF'
+Build X.
+<notification block>
+EOF
+printf 'prompt file: %s\n' "$PROMPT"
+bash pty:true background:true workdir:$SCRATCH command:"codex exec - < \"$PROMPT\""
+```
+
+## Process actions
+
+- `list`: running/recent sessions.
+- `poll`: status.
+- `log`: output.
+- `submit`: send input + Enter.
+- `write`: raw stdin.
+- `paste`: paste text.
+- `kill`: terminate.
+
+## Status to user
+
+- Say what started, where, and `sessionId`.
+- Update only on milestone, worker question, error, user action needed, or finish.
+- If killed, say why.

package/skills/communication/comm-business-writing/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 ORIRO.ai
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 ORIRO.ai
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/communication/comm-business-writing/SKILL.md

@@ -1,67 +1,67 @@
----
-watermark: ORIRO
-name: comm-business-writing
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-description: >
-  Business writing — emails, reports, proposals, executive summaries, and
-  professional communication. Evidence-based writing techniques for clarity
-  and persuasion. Sources: Plain Language Guidelines (US Gov, CC0), Purdue OWL (free).
----
-
-# Business Writing
-
-## Core principles
-
-**Clarity:** One idea per sentence. Short sentences (average 15-20 words).
-**Brevity:** Cut every unnecessary word. "Due to the fact that" → "because."
-**Active voice:** "The team completed the project" not "The project was completed by the team."
-**Specific over vague:** "Revenue increased 23% in Q3" not "Revenue improved significantly."
-
-## Email structure
-
-**Subject line:** Specific and actionable. "Action needed: Q3 budget approval by Friday" not "Budget."
-**Opening:** State purpose in first sentence. Skip "I hope this email finds you well."
-**Body:** One topic per email. Three sentences max per paragraph.
-**Closing:** Clear next action. Who does what by when.
-
-```
-Subject: Decision needed: vendor contract renewal — respond by Dec 15
-
-Hi Sarah,
-
-I need your approval to renew our contract with Acme Corp for 2024.
-
-The contract (attached) runs $45,000/year — same terms as last year.
-If approved, I'll sign and return by December 20 to lock in our rate.
-
-Please reply with your approval or any questions.
-
-Best,
-Marcus
-```
-
-## Report structure
-
-**Executive summary:** Written last. One page maximum. Decision-makers read only this.
-Key elements: Problem → Method → Findings → Recommendation.
-**Body:** Data and analysis supporting executive summary.
-**Appendices:** Detailed data, methodology, raw numbers.
-
-## Proposals
-
-**Problem statement:** What pain does the client have? How big is it?
-**Proposed solution:** What specifically will you do?
-**Evidence:** Why will it work? Case studies, data.
-**Investment:** Cost, timeline, deliverables.
-**Call to action:** Clear next step.
-
-## Plain language rules
-
-Use common words: "use" not "utilize," "start" not "commence," "help" not "facilitate."
-Define acronyms on first use.
-Use headers, bullets, and numbered lists for scanability.
-Test with target reader before finalizing.
-
-Sources: Plain Language Guidelines (plainlanguage.gov — CC0), Purdue OWL (owl.purdue.edu — free),
-On Writing Well by Zinsser (principles)
+---
+watermark: ORIRO
+name: comm-business-writing
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+description: >
+  Business writing — emails, reports, proposals, executive summaries, and
+  professional communication. Evidence-based writing techniques for clarity
+  and persuasion. Sources: Plain Language Guidelines (US Gov, CC0), Purdue OWL (free).
+---
+
+# Business Writing
+
+## Core principles
+
+**Clarity:** One idea per sentence. Short sentences (average 15-20 words).
+**Brevity:** Cut every unnecessary word. "Due to the fact that" → "because."
+**Active voice:** "The team completed the project" not "The project was completed by the team."
+**Specific over vague:** "Revenue increased 23% in Q3" not "Revenue improved significantly."
+
+## Email structure
+
+**Subject line:** Specific and actionable. "Action needed: Q3 budget approval by Friday" not "Budget."
+**Opening:** State purpose in first sentence. Skip "I hope this email finds you well."
+**Body:** One topic per email. Three sentences max per paragraph.
+**Closing:** Clear next action. Who does what by when.
+
+```
+Subject: Decision needed: vendor contract renewal — respond by Dec 15
+
+Hi Sarah,
+
+I need your approval to renew our contract with Acme Corp for 2024.
+
+The contract (attached) runs $45,000/year — same terms as last year.
+If approved, I'll sign and return by December 20 to lock in our rate.
+
+Please reply with your approval or any questions.
+
+Best,
+Marcus
+```
+
+## Report structure
+
+**Executive summary:** Written last. One page maximum. Decision-makers read only this.
+Key elements: Problem → Method → Findings → Recommendation.
+**Body:** Data and analysis supporting executive summary.
+**Appendices:** Detailed data, methodology, raw numbers.
+
+## Proposals
+
+**Problem statement:** What pain does the client have? How big is it?
+**Proposed solution:** What specifically will you do?
+**Evidence:** Why will it work? Case studies, data.
+**Investment:** Cost, timeline, deliverables.
+**Call to action:** Clear next step.
+
+## Plain language rules
+
+Use common words: "use" not "utilize," "start" not "commence," "help" not "facilitate."
+Define acronyms on first use.
+Use headers, bullets, and numbered lists for scanability.
+Test with target reader before finalizing.
+
+Sources: Plain Language Guidelines (plainlanguage.gov — CC0), Purdue OWL (owl.purdue.edu — free),
+On Writing Well by Zinsser (principles)

package/skills/communication/comm-cross-cultural/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 ORIRO.ai
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 ORIRO.ai
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.