Skip to content
Agentmart
Submit a tool

pi-primitive-check

Use when evaluating proposed Pi customisation work against built-in Pi primitives before implementation, especially extensions, packages, slash commands, and…

Skill by victorhg

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/victorhg-pi-primitive-check

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when evaluating proposed Pi customisation work against built-in Pi primitives before implementation, especially extensions, packages, slash commands, and workflow ideas.

Use cases: productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/pi-primitive-check

What's inside

Skill name
pi-primitive-check
Description
Use when evaluating proposed Pi customisation work against built-in Pi primitives before implementation, especially extensions, packages, slash commands, and workflow ideas.
License
MIT
Compatibility
Requires the Pi coding-agent monorepo docs and source tree.
Instructions
50 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Pi Primitive Check

Use this before implementing speculative Pi customisation ideas. The
goal is to avoid building a parallel abstraction when Pi already has a
primitive.

## Workflow

1. Restate the underlying user need, separate from the proposed
   solution.
2. Search local Pi docs for overlapping primitives, especially
   commands, session features, SDK APIs, extension events, tools,
   skills, and TUI APIs.
3. Search this repo for existing built-ins and `packages/pi-*` that
   already address the need.
4. Classify the proposal:
   - use existing Pi primitive
   - document or wrap existing primitive
   - compose existing primitives
   - implement new feature
5. If overlap exists, pause and ask the user to confirm before coding.

## Required local sources

Read relevant files from the installed Pi docs before deciding:

- Main documentation: `/opt/homebrew/lib/node_modules/@earendil-works/pi-coding-agent/README.md`
- Additional docs: `/opt/homebrew/lib/node_modules/@earendil-works/pi-coding-agent/docs`
- Examples: `/opt/homebrew/lib/node_modules/@earendil-works/pi-coding-agent/examples`

Prefer targeted `rg` over broad reading, then read the relevant docs
fully enough to verify behavior.

## Output format

```md
Primitive check:

- User need:
- Existing Pi primitives:
- Existing Pi customisation pieces:
- Overlap/risk:
- Recommendation:
- Confirm before build:
```

Keep the recommendation direct. If the answer is “do not build this”,
say so.

From victorhg/pi-dev, MIT.

More from victorhg/pi-dev

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jul 9, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from victorhg

Cite this page

pi-primitive-check skill. Agent Mart. https://agentmart.dev/skills/victorhg-pi-primitive-check (last updated 2026-10-24)