Agent Stuff skill
Armin's personal toolkit for the Pi Coding Agent: 18 skills, extensions, commands and themes, with some skills portable to other agents
- 3,192 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The skills read Apple Mail, call the Google Workspace and Sentry APIs and work with local keys
- The extensions replace the bash tool, run child processes in tmux and can trust repositories automatically
- The web-browser skill controls Chrome, while ghidra and openscad launch external programs
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/agent-stuffDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The skills read Apple Mail, call the Google Workspace and Sentry APIs and work with local keys
- The extensions replace the bash tool, run child processes in tmux and can trust repositories automatically
- The web-browser skill controls Chrome, while ghidra and openscad launch external programs
This is third-party code. Review the repository files before installing.
What it does
Agent Stuff is the npm package mitsupi for the Pi Coding Agent, assembled by the author from what he uses on his own projects. The skills directory holds separate skills with a SKILL.md and helper scripts: git commits in Conventional Commits style, working with gh, updating a changelog, rules for uv, tmux session control, Sentry event analysis, Ghidra headless analysis, Chrome automation over the DevTools Protocol, converting URLs and documents to Markdown and more. Pi extensions add commands such as /review, /goal, /todos and /session-breakdown and replace the bash tool with a version that nudges the agent toward uv. The /discuss command turns on an interview mode before planning. The author warns that most items are tuned to his own environment, so paths, credentials and defaults will need adjusting.
Who it is for. For Pi Coding Agent users and developers who want to see an experienced engineer's working skills and borrow individual ones for Claude Code.
Good fit when
- You work in the Pi Coding Agent and want a ready set of extensions: the `/todos` task list, `/goal` objectives, `/review` and `/session-breakdown` for usage analysis
- You need a `commit` skill that makes an agent write a short Conventional Commits message and never push
- An agent has to drive interactive CLIs through tmux: the `tmux` skill sends keystrokes and reads pane output
- You want an agent to use `uv` instead of pip and poetry: there is a `uv` skill and command interceptors
- You need a model of a well-built skill with scripts inside, such as `web-browser` over the DevTools Protocol or `sentry`
Not a fit when
- You need a general package with no ties to its author: the anachb and oebb-scotty skills work with Austrian transport, and trust-github-repos trusts repositories of earendil-works and mitsuhiko
- You do not use Pi: the TypeScript extensions and themes target Pi, and only the skills and commands work from other agents
- You expect paths and keys to work untouched: the author warns they need adjusting, especially for apple-mail and google-workspace
- You want a supported distribution: this is a personal repository, not a product
Example request
Use the commit skill and commit the current changes in the src folder, no push neededLimitations
The package is built for Pi and the author's own environment, so paths, credentials and defaults will need adjusting. Some skills are tied to macOS (apple-mail, the no-sleep extension on caffeinate) or to specific services (VOR AnachB, ÖBB Scotty, Sentry, Google Workspace). The extensions are written in TypeScript and loaded by Pi straight from the paths in package.json. The license is Apache-2.0. Skills are separate folders, but some call their own scripts and external programs (Ghidra, OpenSCAD, tmux), so copy a skill folder whole.
How to disable. Delete the copied skill folders from the agent's skills directory. In Pi, remove the `mitsupi` package from the package list. If you enabled the uv extension, also remove the pip, pip3, poetry, python and python3 interceptors from PATH.
FAQ
How do I install Agent Stuff in Pi?
The package is published to npm as `mitsupi`, and the manifest in package.json hands Pi the extensions, skills, themes and commands directories. The README gives no command for attaching the package, so look in the Pi documentation.
Can I use the Agent Stuff skills in Claude Code?
Yes, the skills sit in folders with a SKILL.md and scripts, and you can copy them into the agent's skills directory one by one. The author describes the collection as commands he uses with agents, mostly Claude. The Pi extensions will not work there.
What does the uv extension do?
It replaces the bash tool with a version that is aware of `uv`, injects shims for Python commands and blocks common workflows that skip `uv`. The shims for pip, pip3, poetry, python and python3 live in the intercepted-commands folder.
Which skills in the set are the most general?
`commit`, `github`, `update-changelog`, `uv`, `tmux`, `summarize` and `web-browser` suit any project. The `anachb`, `oebb-scotty`, `ghidra` and `openscad` skills are narrow and useful only for their topic.
What does the /discuss command do?
It turns on interview mode: the agent first inspects the project, asks focused questions in short rounds and stops when the plan is clear enough to implement.
Discussion
No questions or reviews yet.
Related
SkillsBuilder Skills
Skills for agents
A set of small skills from Builder.io for agent work habits: visual plans and diff recaps, docs-first checks, cross-agent review and clean status updates
Tech Leads Club Agent Skills
Agent Skills
A vetted skill registry with a CLI that installs into twenty-plus agents and an MCP server for on-demand skill lookup
The author's personal set: shared agent rules and dozens of skills for GitHub, the browser, macOS, messaging and releases, plus a sync script
A mirror of Lauren Tan's pstack set from Cursor: over 50 skills, the poteto-mode with 23 playbooks and 24 principles for strict agent work on code
A Pi Coding Agent profile for 1C development: ASK, PLAN and BUILD modes, specialized subagents, per-configuration knowledge and optional MCP tools
APM
APM (Agent Package Manager)
A package manager for AI agent context: skills, prompts and MCP servers install with one command across supported agents
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| Agent Stuff (this entry) | no | 3,192 | |
| pi-skills | no | 2,639 | everyday skills for Pi: web search, Gmail, Calendar and YouTube, while Agent Stuff leans toward engineering work and Pi extensions |
| Skills for real engineers by Matt Pocock | no | 301,555 | small composable skills for TDD, diagnosis and review, while Agent Stuff adds scripts, extensions and themes |
| pi-extensions | no | 731 | more than thirty separately installed extensions for the Pi Coding |
README in short
The README opens with a caveat that this is Armin's personal package for the Pi Coding Agent, published to npm as mitsupi. The manifest exposes four directories to Pi: extensions, skills, themes and commands. It then lists commands (one so far, /discuss), 18 skills with a short purpose each, 18 extensions with their hotkeys and commands, three themes and support files: interceptors for uv, a script for analyzing edits and the npm publishing workflow. It ends with how to install dependencies and where the changelog lives.
README badge
Original SKILL.md
--- name: commit description: "Read this skill before making git commits" --- Create a git commit for the current changes using a concise Conventional Commits-style subject. ## Format `<type>(<scope>): <summary>` - `type` REQUIRED. Use `feat` for new features, `fix` for bug fixes. Other common types: `docs`, `refactor`, `chore`, `test`, `perf`. - `scope` OPTIONAL. Short noun in parentheses for the affected area (e.g., `api`, `parser`, `ui`). - `summary` REQUIRED. Short, imperative, <= 72 chars, no trailing period. ## Notes - Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs. - Do NOT include breaking-change markers or footers. - Do NOT add sign-offs (no `Signed-off-by`). - Only commit; do NOT push. - If it is unclear whether a file should be included, ask the user which files to commit. - Treat any caller-provided arguments as additional commit guidance. Common patterns: - Freeform instructions should influence scope, summary, and body. - File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise. - If arguments combine files and instructions, honor both. ## Steps 1. Infer from the prompt if the user provided specific file paths/globs and/or additional instructions. 2. Review `git status` and `git diff` to understand the current changes (limit to argument-specified files if provided). 3. (Optional) Run `git log -n 50 --pretty=format:%s` to see commonly used scopes. 4. If there are ambiguous extra files, ask the user for clarification before committing. 5. Stage only the intended files (all changes if no files specified). 6. Run `git commit -m "<subject>"` (and `-m "<body>"` if needed).