pstack

In the author's own words, from each skill's SKILL.md — showing the first 30 of 50 files.

• architect

  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.

  skills/architect/SKILL.md on GitHub (opens in a new tab)

• arena

  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.

  skills/arena/SKILL.md on GitHub (opens in a new tab)

• automate-me

  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 create-skill + unslop, optionally pulling fresh evidence from recent transcripts.

  skills/automate-me/SKILL.md on GitHub (opens in a new tab)

• blast-radius

  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', or reviewing a small diff you don't trust.

  skills/blast-radius/SKILL.md on GitHub (opens in a new tab)

• bro

  Restate the last message in plain human language, with no jargon.

  skills/bro/SKILL.md on GitHub (opens in a new tab)

• create-verification-skill

  Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.

  skills/create-verification-skill/SKILL.md on GitHub (opens in a new tab)

• figure-it-out

  Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.

  skills/figure-it-out/SKILL.md on GitHub (opens in a new tab)

• how

  Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

  skills/how/SKILL.md on GitHub (opens in a new tab)

• interrogate

  Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.

  skills/interrogate/SKILL.md on GitHub (opens in a new tab)

• maintain-verification-skill

  Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".

  skills/maintain-verification-skill/SKILL.md on GitHub (opens in a new tab)

• make-bot-ui

  Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

  skills/make-bot-ui/SKILL.md on GitHub (opens in a new tab)

• no-comments

  Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

  skills/no-comments/SKILL.md on GitHub (opens in a new tab)

• poteto-mode

  poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

  skills/poteto-mode/SKILL.md on GitHub (opens in a new tab)

• principle-attack-the-premise

  Apply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it.

  skills/principle-attack-the-premise/SKILL.md on GitHub (opens in a new tab)

• principle-boundary-discipline

  Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

  skills/principle-boundary-discipline/SKILL.md on GitHub (opens in a new tab)

• principle-build-the-lever

  Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.

  skills/principle-build-the-lever/SKILL.md on GitHub (opens in a new tab)

• principle-encode-lessons-in-structure

  Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.

  skills/principle-encode-lessons-in-structure/SKILL.md on GitHub (opens in a new tab)

• principle-exhaust-the-design-space

  Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

  skills/principle-exhaust-the-design-space/SKILL.md on GitHub (opens in a new tab)

• principle-experience-first

  Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

  skills/principle-experience-first/SKILL.md on GitHub (opens in a new tab)

• principle-fix-root-causes

  Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.

  skills/principle-fix-root-causes/SKILL.md on GitHub (opens in a new tab)

• principle-foundational-thinking

  Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.

  skills/principle-foundational-thinking/SKILL.md on GitHub (opens in a new tab)

• principle-guard-the-context-window

  Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.

  skills/principle-guard-the-context-window/SKILL.md on GitHub (opens in a new tab)

• principle-laziness-protocol

  Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

  skills/principle-laziness-protocol/SKILL.md on GitHub (opens in a new tab)

• principle-make-operations-idempotent

  Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

  skills/principle-make-operations-idempotent/SKILL.md on GitHub (opens in a new tab)

• principle-migrate-callers-then-delete-legacy-apis

  Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

  skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md on GitHub (opens in a new tab)

• principle-minimize-reader-load

  Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.

  skills/principle-minimize-reader-load/SKILL.md on GitHub (opens in a new tab)

• principle-model-the-domain

  Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.

  skills/principle-model-the-domain/SKILL.md on GitHub (opens in a new tab)

• principle-never-block-on-the-human

  Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.

  skills/principle-never-block-on-the-human/SKILL.md on GitHub (opens in a new tab)

• principle-outcome-oriented-execution

  Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.

  skills/principle-outcome-oriented-execution/SKILL.md on GitHub (opens in a new tab)

• principle-prove-it-works

  Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'

  skills/principle-prove-it-works/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• taste-skillby Leonxlnx Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages 114k stars · 1 skill
• Wazaby tw93 🥷 Engineering habits you already know, turned into skills AI assistants like Claude Code, Codex and Cursor can run. 7.6k stars · 8 skills
• geo-sleuthby Oldcircle An agent skill that finds where a photo was taken — OpenStreetMap geometry, elevation skylines, satellite imagery and street view — and sho… 6.9k stars · 1 skill
• agent-skills-platformby FrancyJGLisboa Build tested agent skills and govern their lifecycle through a user-defined marketplace: evidence, discovery, updates, rollback, quarantine… 2.4k stars · 6 skills
• ponytailby DietrichGebert Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote. 190k stars · 6 skills
• agent-skillsby addyosmani Production-grade engineering skills for AI coding agents. 117k stars · 25 skills