Menu
SKILL.md, skill frontmatter/descriptions, activation triggers, agent definitions, or command/agent instructions. Not for Pi slash-command placement; use pi-command.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Pi extensions and tool policy: extensions/*.ts, hooks, registerTool, promptGuidelines, registerCommand, footer/status UI, tool_result, session hooks, or subprocesses. Not for slash-command placement; use pi-command.
README, CHANGELOG, docs/, RFCs, ADRs, guides, or Markdown structure. Not for prose cleanup or archival work.
Prose cleanup for filler, hype, vague claims, repetition, detection tells, or uncited specifics. Not for Markdown architecture or archival work.
Requirements, user stories, acceptance/verification criteria, or testable outcomes. Not for PRD drafting (/prd) or Pi /goal prompts.
Use for /prd-it or to draft, refine, or review a Product Requirements Document. Not for acceptance criteria, planning, or Pi /goal prompts.
Pi session, trace, metrics, routing, workflow-friction, workflow-telemetry, usage, or local JSONL analysis with DuckDB. Use for aggregating or correlating Pi runtime logs. Not for adding telemetry, generic SQL/database design, or non-Pi logs.
| name | skills-engineer |
| description | SKILL.md, skill frontmatter/descriptions, activation triggers, agent definitions, or command/agent instructions. Not for Pi slash-command placement; use pi-command. |
| Work | Use |
|---|---|
| Skill content, descriptions, activation triggers, agent definitions | skills-engineer |
| Pi slash commands, prompt templates, command placement | pi-command |
| General documentation prose | docs |
Startup context reads skill metadata first. Keep descriptions narrow and bodies concise; put specialized detail behind clearly named subfiles only when needed.
---
name: skill-name
description: "Specific trigger scope. Use when ... Not for ..."
---
name matches the directory and uses kebab-case.description names concrete triggers and excludes neighboring skills.# Title.pi/AGENTS.md; reserve AGENTS for repository-wide rules that apply regardless of loaded resources.Good triggers are exact: file patterns, command names, artifact names, and user phrases. Add "Not for" boundaries when two skills overlap.