All skills
agents365-ai avatar

/pi-cli-runtime

@46ff06f

Internal helper contract for calling the pi-companion runtime from Claude Code

Use this Skill: https://skilld.dev/gh/agents365-ai/365-skills/pi-cli-runtime

This session only. Nothing lands on disk.

SKILL.md

≈24 tokens always: the name and description. ≈739 when used: this file.

Pi Runtime

Use this skill only inside the pi:pi-companion-forwarder subagent.

Primary helper:

  • node "${CLAUDE_PLUGIN_ROOT}/scripts/pi-companion.mjs" task "<raw arguments>"

Execution rules:

  • The rescue subagent is a forwarder, not an orchestrator. Its only job is to invoke task once and return that stdout unchanged.
  • Prefer the helper over hand-rolled git, direct Pi CLI strings, or any other Bash activity.
  • Do not call setup, review, adversarial-review, status, result, or cancel from pi:pi-companion-forwarder.
  • Use task for every rescue request, including diagnosis, planning, research, and explicit fix requests.
  • You may use the pi-prompting skill to rewrite the user's request into a tighter Pi prompt before the single task call.
  • That prompt drafting is the only Claude-side work allowed. Do not inspect the repo, solve the task yourself, or add independent analysis outside the forwarded prompt text.
  • Leave --effort unset unless the user explicitly requests a specific effort.
  • Leave model unset by default. Add --model only when the user explicitly asks for one (e.g. deepseek-v4-pro, deepseek-v4-flash).
  • Default to a write-capable Pi run by adding --write unless the user explicitly asks for read-only behavior or only wants review, diagnosis, or research without edits.

Command selection:

  • Use exactly one task invocation per rescue handoff.
  • If the forwarded request includes --background or --wait, treat that as Claude-side execution control only. Strip it before calling task, and do not treat it as part of the natural-language task text.
  • If the forwarded request includes --model, pass the model id through to task unchanged.
  • If the forwarded request includes --effort, pass it through to task.
  • If the forwarded request includes --resume, strip that token from the task text and add --resume-last.
  • If the forwarded request includes --fresh, strip that token from the task text and do not add --resume-last.
  • --resume: always use task --resume-last, even if the request text is ambiguous.
  • --fresh: always use a fresh task run, even if the request sounds like a follow-up.
  • --effort: accepted values are off, minimal, low, medium, high, xhigh, max. The alias none maps to off.
  • task --resume-last: internal helper for "keep going", "resume", "apply the top fix", or "dig deeper" after a previous rescue run.

Safety rules:

  • Default to write-capable Pi work in pi:pi-companion-forwarder unless the user explicitly asks for read-only behavior.
  • Preserve the user's task text as-is apart from stripping routing flags.
  • Do not inspect the repository, read files, grep, monitor progress, poll status, fetch results, cancel jobs, summarize output, or do any follow-up work of your own.
  • Return the stdout of the task command exactly as-is.
  • If the Bash call fails or Pi cannot be invoked, return nothing.

Source: SKILL.md on GitHub

No alerts16d3 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill instructs the agent to act as a proxy for an internal tool, executing a local script with raw user input. This pattern creates a potential attack surface for indirect prompt injection and command manipulation because user-provided text is concatenated into a shell command without explicit sanitization or escaping instructions.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

Signed by skilld at 46ff06f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 10 hours ago.

Activeupdated 4 weeks ago
user-invocable
false

README badge

README badge for agents365-ai/365-skills/pi-cli-runtime