Skip to content

Make skills repo agent-agnostic#10

Open
huewood wants to merge 6 commits intomainfrom
hugh/skills-rework
Open

Make skills repo agent-agnostic#10
huewood wants to merge 6 commits intomainfrom
hugh/skills-rework

Conversation

@huewood
Copy link
Copy Markdown

@huewood huewood commented Feb 19, 2026

Reframes the repo as a general collection of AI coding agent skills rather than something pi-specific. Skills are standalone markdown files that work with Claude Code, Codex, Cursor, Windsurf, pi, or any agent that loads markdown context.

README

  • Relative links on all skill and extension entries
  • Extensions clearly labelled as pi-only TypeScript plugins
  • New Setup — Skills (with Claude, Codex, etc) section covering slash commands (Claude Code, Cursor, Windsurf), skills directories (Codex's .agents/skills/, Claude Code's .claude/skills/), @-imports in CLAUDE.md, and direct prompt reference
  • New Setup — pi (skills + extensions) section with full install options (local path, GitHub URL, manual settings.json), explanation of what pi loads, update workflow, and links to the pi website and repository

multi-review

  • Remove hardcoded pi -p CLI invocation
  • Remove broken reference to a non-existent code-review skill
  • Sub-agent step is now tool-agnostic (describe what to do, not which CLI)
  • Replace Opus / Codex labels with Model A / Model B throughout

Reframes the repo as a general collection of AI coding agent skills
rather than pi-specific. Skills are now documented as standalone
markdown files usable with Claude Code, Codex, Cursor, Windsurf, pi,
or any agent that loads markdown context.

- README: new Setup section with agent-specific wiring instructions
  (slash commands, skills directories, @-imports, direct reference, pi)
- README: relative links on all skill and extension entries
- README: extensions clearly labelled as pi-only
- multi-review: remove pi CLI invocation and broken code-review skill
  reference; make sub-agent step tool-agnostic; replace Opus/Codex
  labels with Model A/Model B throughout
- package.json: update description and keywords

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
@huewood huewood self-assigned this Feb 19, 2026
huewood and others added 5 commits February 19, 2026 15:17
The package.json is pi's package manifest — the keywords and description
are consumed by pi tooling, not for general discovery. Shouldn't have
touched it.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Add full install options (local path, GitHub URL, manual settings.json),
explain what pi does with the package once installed (skills as slash
commands, extensions as hooks/tools), and clarify the update workflow.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
pi is fundamentally different — it uses a package manager and loads both
skills and extensions. Split Setup into two distinct top-level sections:
- "Setup — other agents (skills only)" for symlink/reference approaches
- "Setup — pi (skills + extensions)" for the package install workflow

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple thoughts on this:

  • Leaving the models and command to run the sub-agents unspecified will make the skill less token efficient as the model has to figure out how to do this every time, and also potentially makes each run less consistent. I get wanting the idea is to make it not pi-specific, but it makes it less efficient when we do that.
  • Maybe it makes more sense to make a more minimal change to this skill that says something along the lines of "If these two models are not available then choose the next most appropriate ones from the models that are available"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While skills are largely portable, extensions (at least as they exist in this repo) are very much a pi-specific thing since they hook into pi's extensions API.

Copy link
Copy Markdown
Author

@huewood huewood Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes correct. This PR doesn't change that; actually better explains it in the readme.md no?

Copy link
Copy Markdown
Contributor

@nishantdesai nishantdesai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating the details to reflect what the repo is actually about. Skills are after all agent agnostic.

Copy link
Copy Markdown
Collaborator

@pweiskircher pweiskircher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't care overly much either way. I thought this would be good so we can use the pi isntall of a gitrepo and have extensions and stuff but I can deal with whatever!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants