Index of every page on this site: llms.txt
All skills
agents365-ai avatar

/pi-prompting

@0a1679d
Run it yourself

Internal guidance for composing prompts that Pi runs (DeepSeek by default) handle reliably for coding, review, diagnosis, and research tasks

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈39 tokens for metadata: the name and description. ≈947 when used: this file.

Description uses 1.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈155 characters, or 1.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Pi Prompting

Use this skill when pi:pi-companion-forwarder needs to ask Pi for help on a non-trivial coding or investigation task.

Pi runs whatever model the user has configured. By default this plugin targets DeepSeek V4 (Pro for review, Flash for everyday tasks). The guidance below assumes the prompt may run on either a non-reasoning model (Flash) or a reasoning model (Pro). Bias toward concrete, numbered checklists rather than abstract instructions — both model classes follow those reliably.

Core rules:

  • Prefer one clear task per Pi run. Split unrelated asks into separate runs.
  • Tell Pi what done looks like. Do not assume it will infer the desired end state.
  • State explicit grounding rules whenever an unsupported guess would degrade quality.
  • Use stable XML-style tag blocks so the prompt has obvious internal structure.
  • Keep prose short. Prefer numbered checklists over paragraphs for procedural work.

Default prompt recipe:

  • <task>: the concrete job and the relevant repository or failure context. Include file paths.
  • <output_contract> (or <structured_output_contract> for JSON): exact shape, ordering, and brevity requirements.
  • <grounding_rules>: required for review, research, or anything that could drift into unsupported claims.
  • <action_safety>: required for write-capable tasks — name the directories and file kinds Pi may touch.

When to add extra blocks:

  • Coding or debugging: add <completeness_contract> listing what counts as "done" (tests pass, lint clean, files touched).
  • Review or adversarial review: rely on the shipped prompts/adversarial-review.md and prompts/review.md. Do not hand-craft another review prompt.
  • Research or recommendation tasks: add a short <sources> block listing what Pi is allowed to consult.

How to choose prompt shape:

  • Use the built-in /pi:review or /pi:adversarial-review commands when the job is reviewing local git changes. Those prompts already carry the review contract.
  • Use task when the job is diagnosis, planning, research, or implementation and you need to control the prompt more directly.
  • Use task --resume-last for follow-up instructions on the same Pi session. Send only the delta instruction instead of restating the whole prompt unless the direction changed materially.

Working rules:

  • Prefer explicit prompt contracts over vague nudges.
  • Do not raise reasoning (--effort high) by default — DeepSeek Flash will not benefit, and DeepSeek Pro takes longer. Tighten the prompt before escalating effort.
  • For tool-heavy or long-running tasks, ask Pi for brief outcome-based progress updates inside its working notes.
  • Keep claims anchored to observed evidence. If something is a hypothesis, mark it as such.

Prompt assembly checklist:

  1. Define the exact task and scope in <task>.
  2. State the output contract — JSON, bullet list, plain prose — and the maximum length.
  3. Decide whether Pi should keep going on its own judgment or stop for missing high-risk details.
  4. Add <grounding_rules> and <action_safety> only where the task needs them.
  5. Remove redundant instructions before sending the prompt.

Subagent-aware prompting

When pi-subagents is installed:

  • For tasks with parallel workstreams, prepend <available_pi_subagents> block before <task>.
  • Suggested agent routing: scout for exploration, researcher for web/docs, planner for design, worker for implementation, reviewer for code review.
  • Never suggest subagents in adversarial-review or stop-review-gate prompts (those need deterministic behavior).
  • The block is a suggestion, not a command — Pi decides whether to delegate.
  • For dedicated multi-task parallel execution, use /pi:parallel-rescue "task1" "task2" ... instead of manual prompt construction.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a structural framework and best practices for composing prompts intended for an internal AI companion. It includes security-conscious recommendations such as using XML delimiters and defining explicit action safety boundaries for file system operations. No malicious patterns were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

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

Last checked against GitHub 3 weeks ago.

Activeupdated 3 months ago
user-invocable
false

README badge

README badge for agents365-ai/365-skills/pi-prompting