Agent Skill
In Your Own Words skill
in-your-own-wordsmichael-denyer/pstack-claudeplugins/pstack/skills/in-your-own-words/SKILL.md
Restate in your own words what you think the user's goals are and what problem they're trying to solve. Use for /in-your-own-words.
always on
36 tokname + description
once used
21 tokSKILL.md body
bundled files
0
repo stars
3.3kGitHub
Install the In Your Own Words skill
Skills CLI (Claude Code, Codex, Cursor and others)
npx skills add https://github.com/michael-denyer/pstack-claude --skill in-your-own-words
Claude Code, by hand (all projects)
git clone --depth 1 https://github.com/michael-denyer/pstack-claude.git /tmp/pstack-claude mkdir -p ~/.claude/skills cp -R /tmp/pstack-claude/plugins/pstack/skills/in-your-own-words ~/.claude/skills/in-your-own-words
For one project only, copy the folder into .claude/skills/ in that project instead. The agent picks it up when a task matches its description.
What it costs your context
Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.
| When | What loads | Cost |
|---|---|---|
| Every session | Name and description | 36 tok |
| When the agent uses it | The SKILL.md instructions | 21 tok |
| Only if opened | No bundled files | — |
Until it is used, in-your-own-words costs about 38× less than the median MCP server we measured (1,363 tokens on every turn). Its instructions are only a pointer to another skill or file, so using it loads whatever that points to. Installing all 65 skills from michael-denyer/pstack-claude would load 3,163 tokens of descriptions. Skills vs MCP study
Checks
Our checks found nothing to flag: it follows the Agent Skills specification's naming and size guidelines and doesn't pipe downloads into a shell.
Checked 2026-10-22 · method
More skills from michael-denyer/pstack-claude
- architectmichael-denyer/pstack-claude
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
3.3k52 tok idle · 1,615 in use - arenamichael-denyer/pstack-claude
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
3.3k58 tok idle · 1,321 in use - automate-memichael-denyer/pstack-claude
Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via plugin-dev:skill-development + unslop, optionally pulling fresh evidence from recent transcripts.
3.3k72 tok idle · 1,755 in use - babysitmichael-denyer/pstack-claude
Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.
3.3k61 tok idle · 1,057 in use - benchmark-checklistmichael-denyer/pstack-claude
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.
3.3k53 tok idle · 1,107 in use - blast-radiusmichael-denyer/pstack-claude
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.
3.3k87 tok idle · 867 in use - bromichael-denyer/pstack-claude
Restate the last message in plain human language, with no jargon. Use for /bro or when asked to say it plainly.
3.3k28 tok idle · 30 in use - correctmichael-denyer/pstack-claude
Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.
3.3k68 tok idle · 461 in use