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 |
|---|---|---|---|---|---|
| git-syncEricTechPro/super-boardSync the current branch in one pass — commit the working tree as one commit per logical change (in the host repo's commit format, or the super-board writing standard), gate Supabase schema changes, merge-pull, resolve conflicts hunk by hunk, then push without force. Use when the user runs /git-sync or says "git-sync", "sync", "commit and push", "pull and push", or "sync my branch". | Stars: 702 | Updated | Claude CodeCodex | Verified | Install |
| pr-security-reviewEricTechPro/super-boardSecurity review of one PR's diff against its base branch — high-confidence, exploitable vulnerabilities only (injection, auth bypass, crypto and secrets, code execution, data exposure), each false-positive-filtered by a parallel sub-task. The super-qa Tester lane runs it on every PR; each finding fails QA and goes back to Build. Use when the user says "pr security review", "/pr-security-review", or wants a security pass on a branch or PR diff. Not Claude Code's built-in /security-review; for a deep whole-repo audit use security-audit. | Stars: 702 | Updated | Claude CodeCodex | Unverified | Install |
| super-boardEricTechPro/super-boardGitHub-Project-driven autonomous pipeline. Five verbs — onboard, lint, status, run, stop — that take a Project board from empty to drained across Build → QA → Review → Done lanes (labels qa · bug · feature route each card), with graceful shutdown / resume. Use when the user says "super-board", "/super-board", "drain my GitHub project", "set up the autonomous loop", "kick off the headless build/QA pipeline", or "stop super-board". | Stars: 702 | Updated | Claude CodeCodex | Verified | Install |
| super-buildEricTechPro/super-boardBuilder lane of the super-board pipeline — takes a `Ready` GitHub Project card into its own per-issue git worktree, makes the smallest safe change test-first (TDD, `ponytail` simplest-first, official docs first for third-party APIs, upgrades and auth/billing), opens a draft PR and hands it to QA and Review through the board; it never merges — merges go through the Reviewer's merge gate. Inside `super-board run` it runs as a lane agent in the in-session wave workflow (`workflows/super-board-wave.js`, no worker cap unless `max_workers` is set); standalone headless `claude -p` dispatch is legacy opt-in. Use when the user says "Super Build", "run the build loop", "/super-build", or invokes the skill. | Stars: 702 | Updated | Claude CodeCodex | Verified | Install |
| super-collectEricTechPro/super-boardFind problems in one project, verify each, write one findings doc and hand it to Matt Pocock's /to-spec then /to-tickets; 1–5 tickets go to /implement-spec, 6+ to the super-board Backlog (no /to-spec or /to-tickets installed → files straight into Backlog). Source plug-ins - sentry (app errors), posthog (exceptions, rage/dead clicks, failure events, web vitals, tracking gaps), github (issues not on the board), prs (recurring problems in merged PRs and their review comments), architecture (refactor findings), plus any custom source added in onboard (an MCP server, HTTP API, CLI command or app). Each candidate is checked by one fresh verifier first. Dry-run by default. Use when the user says "super-collect", "/super-collect", "/super-collect sentry", "collect tickets", "triage errors onto the board", "what keeps breaking", or "find refactors". | Stars: 702 | Updated | Claude CodeCodex | Verified | Install |
| super-qaEricTechPro/super-boardSuper QA canonical workflow for functional bug-bash, evidence capture, and fix-ready issue filing. Crawls routes from `docs/super-qa/queue.md` with Playwright, records screenshots/logs/HARs, files product-readable issues with clear type/priority/area labels, and continues until traversal is complete or only human-gated blockers remain. Crawling is always browser-driven, but the regression test it leaves behind is written at whichever layer the defect actually lives — unit or integration in Vitest, e2e in Playwright only when the browser is the thing that broke. Use when the user says "run super-qa", "QA review", "bug bash", "verify and fix", or invokes `/super-qa`. | Stars: 702 | Updated | Claude CodeCodex | Verified | Install |
| verify-appEricTechPro/super-boardRun affected app feature checks, inspect evidence, or maintain this project's verifier when source or accepted behavior changes. | Stars: 702 | Updated | Claude CodeCodex | Verified | Install |
| super-reviewEricTechPro/super-boardReviewer lane of the super-board pipeline and standalone PR/branch readiness review — forms its own hypotheses before reading the builder's summary, remembers prior findings and re-checks each with file:line proof, runs an adversarial truth-check on non-trivial diffs, and classes every finding (Gap, Bug, Verification miss, Scope drift, Over-engineering via `ponytail:ponytail-review`). Merges only through `super-board-merge-gate.sh`, pinned to the reviewed head SHA, and routes other fixes to Super Build or Super QA via the board. Use when the user says "Super Review", "review this branch", "review loop", "make sure this is merge-ready", "PR review", or asks for code, architecture, security, QA evidence, or release-readiness judgment. | Stars: 702 | Updated | Claude CodeCodex | Verified | Install |
| ui-refine-loopEricTechPro/super-board | Stars: 702 | Updated | Claude CodeCodex | Verified | Install |
| visualEricTechPro/super-boardTurn the current work into one polished, self-contained HTML visual page — a recap of a branch's changes, a plan, a map of a folder, endpoint set, or architecture, or an interactive drill-down map of a skill pack or system (zoom, pan, click a node for details, double-click to open its inner view). Use when the user runs /visual or asks to visualise, picture, or visually recap a branch, PR, diff, plan, or part of a codebase, or to map a skill pack, its lanes, scripts, and hooks. | Stars: 702 | Updated | Claude CodeCodex | Verified | Install |
| agent-bridgeahgraber/skillsUse when an agent in one harness must create, observe, or steer one or more agents in another harness through a tmux session the user can watch. Triggers: "use an agent in another harness", "bridge to <agent>", "run <agent> in tmux", "use a different harness", "check on the external agent". Not for subagents or delegation inside the current harness (use `subagent-patterns`). | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| alt-textahgraber/skillsUse when the user shares an image, chart, diagram, screenshot, or figure and needs it described — for alt-text, accessibility, documentation, or to understand what it depicts. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| antislop-writingahgraber/skillsWrite, rewrite, or line-edit prose so it reads as a professional wrote it, not a model: clear, specific, register-appropriate, and free of AI writing tells. Apply to any prose a human will read. Triggers include "make this sound human", "remove the AI tells", "de-slop this", "does this read like ChatGPT wrote it", "humanize this draft", "rewrite this professionally", or any request to draft or sharpen an email, blog post, op-ed, report, memo, or longform message. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| api-designahgraber/skillsUse when designing, reviewing, or planning REST or GraphQL APIs — endpoint structure, schema design, versioning, error handling, pagination, URI naming, or choosing between REST and GraphQL. Also triggers for OpenAPI spec creation and API contract review. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| brainstormingahgraber/skillsUse when turning a fuzzy idea into a refined design through dialogue — across software, writing, talks, events, naming, activities, or any creative/design task. Its adversarial lenses also stress-test a plan or proposal already on the table. Triggers: 'brainstorm', 'help me think about/through', 'figure out', 'work through', 'I have this idea', 'let's design', 'flesh this out'. Domain-agnostic. Not for: open-ended ideation with no anchor ('what should I build?'), implementing from a finalized spec, narrow binary decisions ('X or Y?'), retrospective review, mechanical refactors, or reframing whether the presenting question is the "real" one. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| changelogahgraber/skillsUse when writing, updating, or generating a CHANGELOG.md — for a new release, an unreleased section update, or drafting from git history or diff. Triggers: "update the changelog", "write release notes", "what changed since X", "generate changelog for v1.2.0", "add this to the changelog", "draft unreleased section". Not for commit messages (use commit-message skill) or internal deployment runbooks. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| code-reviewahgraber/skillsUse when reviewing code changes before committing or merging — staged diffs, branch diffs, or PR readiness checks. Triggers: 'review my code', 'check these changes', 'review this branch', 'give feedback on my diff', 'is this PR ready?'. Not for implementing features, running test suites, formatting-only passes, or building understanding of a change (use teach-me). | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| commit-messageahgraber/skillsUse whenever a Conventional Commit message is being drafted — whether the user asks ("write commit message", "draft commit from staged changes", "generate conventional commit", "split this into commits") or you are about to propose one proactively after finishing work (e.g. completing tasks, wrapping up a feature, or summarizing staged changes). Invoke before writing the message inline. Not for creating commits, amending history, or full code review. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| debuggingahgraber/skillsUse when a bug, test failure, build break, regression, flaky test, or unexpected behavior appears — before proposing or attempting fixes. Triggers: "why is this failing", "this test broke", "something's wrong", "help me debug", "it works on my machine", mysterious stack traces, intermittent failures. Not for: writing new features, reviewing working code, or routine refactors. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| deep-researchahgraber/skillsUse when the user wants a deep, multi-source, fact-checked web research report on a topic too broad for a single search. Triggers: "deep research on X", "research report", "investigate thoroughly", "comprehensive findings on", "what's the current state of X", "survey the landscape of". Not for: single-fact lookups, library/API/version questions (use mcp-research), or open-ended ideation (use brainstorming). | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| editorial-reviewahgraber/skillsUse when the user wants rigorous, non-sycophantic editorial feedback on a draft, essay, blog post, or argument through back-and-forth dialogue — pressure-testing thesis, structure, argument, clarity, tone, and evidence. Triggers: "be my sparring partner", "pressure-test this draft", "poke holes in my argument", "is this ready to publish", "sharpen this post", "where is this weak". Not for one-shot copyediting, proofreading, or ghostwriting. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| formal-verificationahgraber/skillsUse when the user asks for formal verification or formal methods: writing or checking a design model (TLA+, Alloy, P, Quint), proving code against contracts (Dafny, Verus, SPARK, Frama-C, Lean, Rocq), model checking, invariants, liveness, vacuous passes, or counterexamples; deciding whether a design or requirement warrants formal verification; or keeping existing formal specs and proofs current. Not for prose requirements or "spec this out" (use sdd). | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| grill-meahgraber/skillsUse when the user wants an elicitative interview — reaching alignment on a plan, decision, or idea by drawing out their decisions, unstated opinions, silent assumptions, and thoughts they find hard to put into words, through rounds of pointed questions. Triggers: "grill me", "interview me about this", "make sure we're aligned", "make sure you understand what I want", "help me pin down the decisions", "what am I assuming", "help me figure out what I actually want". | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| handoffahgraber/skillsUse when ongoing work or conversational context must continue in a new conversation, session, or agent with no shared history. Triggers: 'handoff', 'prepare context for next chat', 'summarize for a new session', 'continue this in another conversation'. Not for same-chat status updates or repository documentation. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| interactive-notebook-demoahgraber/skillsUse when authoring or reviewing a hands-on demo, tour, or walkthrough notebook (`#%%` percent-format or Jupyter) that demonstrates a feature, library, or API and doubles as semi-interactive documentation. Triggers: "write a demo notebook", "build a feature demo", "demo this library/API", "a notebook to walk through X", "interactive docs for this feature". Not for production/analysis notebooks or pure asyncio event-loop mechanics (see python-notebooks-async). | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| mcp-researchahgraber/skillsUse when tasks require current, source-backed technical information from MCP tools. Apply for library/API questions, dependency version checks, third-party integration work, framework- or SDK-specific debugging, and any case where stale model knowledge could cause incorrect guidance. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| optimize-skillsahgraber/skillsUse when creating or refining SKILL.md-based skills, or diagnosing weak triggering (under/over-triggering, vague descriptions, bloated context, or missing workflow guidance). | Stars: 6 | Updated | Claude CodeCodex | Unverified | Install |
| proofahgraber/skillsUse when the user asks for proofreading or light copy editing while preserving original wording, tone, and order. Triggers: 'proofread', 'fix typos', 'grammar only', 'copy edit only', 'SPAG pass'. Not for rewrites, tone shifts, structural edits, or style upgrades; use antislop-writing for those requests. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| pythonahgraber/skillsUse when a Python change is about to be called done (before commit or PR) and whenever asked to review, audit, sanity-check, or clean up Python code or judge whether it meets standards. Also use at decision points the defaults cover: choosing retry/timeout/idempotency policy, config loading, pydantic placement, module boundaries, or a concurrency model. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |
| python-notebooks-asyncahgraber/skillsUse when writing or reviewing asyncio code in Jupyter notebooks or '#%%' cell workflows — structuring event-loop ownership, orchestrating async tasks, or choosing compatibility strategies. Also use when hitting RuntimeError: This event loop is already running, asyncio.run() failures in cells, or tasks silently never completing. | Stars: 6 | Updated | Claude CodeCodex | Verified | Install |