Recently active skills
Trending is calculated from star growth this site has recorded itself. No history is estimated or back-filled.
Not enough history yet: 2 of 7 days recorded. Until then this list is ordered by the most recent content change.
77079 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-feedbackahgraber/skillsYou MUST use this when receiving feedback that evaluates a text-based work artifact you produced or are responsible for — code, specs, design docs, PRDs, proposals, plans, or prose — by asserting a defect, questioning a decision, supplying reasoning, or proposing a change for assessment. Also use when asked to implement external review comments that must first be assessed. Not for an unambiguous parameter choice, approval, confirmation, typo or formatting fix, or direct revision instruction that supplies no claim or rationale to evaluate. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| refactorahgraber/skillsUse when changing the structure of working code without changing its behavior: decomposing an oversized function, extracting or merging a module, collapsing a layer, breaking an import cycle. Applies when the edit is structural enough to need a plan and explicit approval before it lands. Triggers: 'refactor this', 'decompose this function', 'split this module', 'break this dependency cycle', 'extract this into', 'restructure', 'work through the deferred items'. Not for slop cleanup (use simplify), judging a change (use code-review), fixing bugs, or adding behavior. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| sddahgraber/skillsUse when the user wants any spec-driven development action — exploring before speccing, deriving specs from code or translating specs from another system, proposing a change, applying or implementing, verifying, syncing delta specs, or archiving. Triggers: 'spec this out', 'create a change', 'apply tasks', 'verify implementation', 'sync specs', 'archive change', or any mention of 'specs' or 'sdd'. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| sdd-applyahgraber/skillsUse when implementing tasks from a change's tasks.md. Triggers: "apply tasks", "implement the change", "work through tasks", "start implementing", "continue implementing", "apply the change". | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| sdd-archiveahgraber/skillsUse when completing and archiving a change after all tasks are done and specs are synced. Triggers: "archive the change", "complete this change", "close out the change", "finish the change", "archive". | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| sdd-deriveahgraber/skillsUse when deriving SDD specs from existing code or retroactively documenting implemented behavior. Triggers: "derive specs", "generate specs from code", "document this code in SDD", "retrofit specs", "spec out what's already built". | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| sdd-exploreahgraber/skillsUse when the user wants to think through ideas, investigate problems, or clarify requirements before or during any SDD path. Triggers: "explore", "think through", "help me figure out", "what should I build", "I'm not sure where to start", "let's brainstorm", "investigate this", "I want to explore". | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| sdd-proposeahgraber/skillsUse when creating a new change with all SDD artifacts — proposal, delta specs, design, and tasks. Triggers: "propose a change", "create a change for X", "I want to implement feature Y", "start a new change", "let's build X". | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| sdd-syncahgraber/skillsUse when merging delta specs from a change into the main baseline specs. Triggers: "sync specs", "merge delta specs", "update main specs", "apply the spec changes", "sync the change". | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| sdd-translateahgraber/skillsUse when translating or migrating existing specs from another tool or format (Spec Kit, Kiro, ADRs, Jira, Confluence, Word docs, or custom markdown requirements) into SDD spec format. Also use when the user says "convert these specs", "migrate to SDD", "translate from X to SDD", or "import specs". | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| sdd-verifyahgraber/skillsUse when verifying that an implementation matches a change's SDD artifacts. Triggers: "verify", "check implementation", "did I implement everything", "verify the change", "is implementation complete", "check conformance". | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| securing-codeahgraber/skillsUse when writing or reviewing code that handles external input, manages access, touches data or crypto, or changes dependencies. Triggers: endpoints, auth/authz, DB/ORM, file handling, secrets, "is this secure?", "security review". NOT for formatting, pure UI, or explaining code. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| security-deep-scanahgraber/skillsUse when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide or scoped-path security scan. Run repeated independent discovery passes over one resolved scope with worker-specific threat models, semantically merge candidates, synthesize one canonical validation threat model, then run validation, attack-path analysis, canonical JSON completion, and generated reporting once. Do not use for PRs, commits, branch diffs, or working-tree diffs. | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| security-fix-findingahgraber/skillsUse when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans. | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| security-scanahgraber/skillsUse when the user asks for a security scan or review of a repository, a scoped path (package, folder, or submodule), or a Git-backed change set (pull request, commit, branch diff, or working-tree patch). Point it at the target; it runs the full threat-model, discovery, validation, and attack-path pipeline and writes a report. Do not use to triage externally supplied findings or to fix a single finding. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| security-triage-findingahgraber/skillsUse when the user supplies existing security findings or vulnerability reports — SARIF results, CVE/GHSA or advisory text, scanner tickets, bug bounty reports, or finding artifacts — and wants static repo-impact triage. Do not use for discovery, duplicate-bug triage, validation, or fixes. | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| shell-scriptsahgraber/skillsUse when writing or reviewing Bash scripts and shell snippets, especially for shebang selection, quoting, parameter expansion ("${VAR}" style), test expressions (`[ ]` vs `[[ ]]`), ShellCheck-guided fixes, and portability decisions across POSIX sh, Bash, and zsh compatibility targets. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| show-meahgraber/skillsUse when the user needs to see something to answer the current question — a sketch of logic, runtime flow, UI structure, or file layout; a Mermaid diagram; a chart of the data at hand; a mockup, wireframe, or side-by-side comparison during a design discussion (visual brainstorming). Triggers: "show me", "sketch this", "diagram this", "draw the flow", "what does this look like", "mock this up", "wireframe", "mermaid diagram", "chart this", "plot this data", "compare these visually". Not for: building understanding that must stick — background, sequencing, self-check (use teach-me); describing an image the user supplied (use alt-text); or building a durable deliverable such as a dashboard, report, or app. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| simplifyahgraber/skillsUse to cut slop out of working code: duplication, dead code, needless indirection, comment noise, defensive padding. Point it at the current changes, a file, a directory, or the whole repo. Triggers: 'simplify this', 'clean this up', 'de-slop this code', 'strip the cruft', 'tighten this diff', 'this code is bloated', 'audit this for slop'. Not for judging correctness or merge readiness (use code-review), and not for structural change that needs a plan and approval (use refactor). | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| strudelahgraber/skillsUse when writing, debugging, or explaining Strudel live-coding music patterns — mini-notation syntax, pattern functions (fast/slow/every/off/stack), synth/sample selection, audio effects, scale/chord/voicing API, or EDM production recipes. Triggers: "write a Strudel pattern", "how do I make a bassline in Strudel", "what does .every() do", "strudel drum beat", "strudel chord voicing", any Strudel code question. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| subagent-patternsahgraber/skillsUse when dispatching development work to one or more subagents and deciding how to shape each dispatch. Triggers: "use subagents", "orchestrate subagents", "delegate to a cheaper/stronger model", "big:little" / "little:big", "verifier / adversary / explorer / oracle subagent", "run this with subagents", "get an independent second opinion". Not for: the parallel code-review path (use `code-review`), or driving a separate agent CLI non-interactively. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| synthesizeahgraber/skillsUse when distilling the through-line gist of one or more sources — the spine, argument, tension, or recurring frame running through a set of documents, notes, research, or transcripts, OR across the ideas within a single rich piece — into a few concise paragraphs. Triggers: "synthesize", "what's the through-line/gist", "extract the insight", "pull these together". Not for faithful summary or condensation that covers what a source says, nor for comparisons or catalogs where enumeration is the deliverable. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| teach-meahgraber/skillsUse when the user wants to be taught a subject, not just answered — "teach me X", "help me learn X", "help me understand X", "help me grok X", "explain how X works", "quiz me on X", "I keep bouncing off X" — where X can be anything: a historical period, a statistical method, music theory, a poem, a legal concept, a cooking technique, a library, a codebase, or a code change. Change-focused asks belong here too: "explain this diff/PR/branch", "walk me through this change", "onboarding doc for this change", "teach me what changed", "help me/my team understand this PR". Spans a quick in-chat lesson up to a saved, dated lesson artifact. Not for: a quick factual answer (just answer), needing only to see a shape or sketch (use show-me), writing a commit message (use commit-message), or reviewing code for defects (use code-review). | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| writing-docstringsahgraber/skillsUse when writing, rewriting, or auditing Python docstrings that a documentation site is generated from, or when docstrings are long, narrate the code, or leave a reader of the generated reference unable to find their way. Triggers - "audit the docstrings", "docstring slop", "docstrings as documentation", "the API reference reads badly", "rewrite these docstrings". | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| writing-testsahgraber/skillsUse when writing or reviewing tests in any language, or diagnosing a suite that is slow, brittle, or hard to read. Triggers: "write tests", "how should I test this", "what kind of test", "test is flaky/fragile", "should I mock this", "test is hard to read". Python-specific practices (mocking, pytest, async) are included in `references/python-testing.md`. | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| ask-mattJarvvski/jjfxAsk which skill or flow fits your situation. A router over the skills in this repo. | Stars: 41 | Updated | Claude CodeCodex | Verified | Install |
| claude-handoffJarvvski/jjfxHand the current conversation off to a fresh background agent that picks up the work immediately. | Stars: 41 | Updated | Claude CodeCodex | Verified | Install |
| code-reviewJarvvski/jjfxReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X". | Stars: 41 | Updated | Claude CodeCodex | Verified | Install |
| codebase-designJarvvski/jjfxShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary. | Stars: 41 | Updated | Claude CodeCodex | Verified | Install |
| design-an-interfaceJarvvski/jjfxGenerate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice". | Stars: 41 | Updated | Claude CodeCodex | Verified | Install |