The catalog
612,213 rows, by stacks then stars
Testing for xss vulnerabilities with burpsuite
galyarderlabs/galyarder-framework/skills/testing-for-xss-vulnerabilities-with-burpsuite Skill
20★ repoIdentifying and validating cross-site scripting vulnerabilities using Burp Suite's scanner, intruder, and repeater tools during authorized security assessments.
Tracking threat actor infrastructure
galyarderlabs/galyarder-framework/skills/tracking-threat-actor-infrastructure Skill
20★ repoThreat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a
galyarderlabs/galyarder-framework/skills/ubiquitous-language Skill
20★ repoExtract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
galyarderlabs/galyarder-framework/skills/ui-ux-designer Skill
20★ repoUse when user experience, visual flow, interaction quality, or interface coherence needs a dedicated design-oriented pass.
Using galyarder agent framework
galyarderlabs/galyarder-framework/skills/using-galyarder-agent-framework Skill
20★ repoUse when legacy prompts or old framework sessions refer to the pre-rebrand Galyarder Agent Framework operating guide and need the modern equivalent behavior.
galyarderlabs/galyarder-framework/skills/using-galyarder-framework Skill
20★ repoUse when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
galyarderlabs/galyarder-framework/skills/using-git-worktrees Skill
20★ repoUse when legacy prompts or older framework flows reference `using-git-worktrees` and you need the modern runtime to resolve that capability cleanly.
Validating backup integrity for recovery
galyarderlabs/galyarder-framework/skills/validating-backup-integrity-for-recovery Skill
20★ repoUse when recovery planning requires verification that backups are restorable, complete, and safe to trust before an incident or recovery event.
galyarderlabs/galyarder-framework/skills/vercel-react-best-practices Skill
20★ repoReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
galyarderlabs/galyarder-framework/skills/vercel-react-expert Skill
20★ repoUse when legacy prompts or older framework flows reference `vercel-react-expert` and you need the modern runtime to resolve that capability cleanly.
Verification before completion
galyarderlabs/galyarder-framework/skills/verification-before-completion Skill
20★ repoUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
galyarderlabs/galyarder-framework/skills/web-design-guidelines Skill
20★ repoUse when website or web app UI work needs practical design guidance for hierarchy, layout, readability, responsiveness, and interaction quality.
galyarderlabs/galyarder-framework/skills/write-a-prd Skill
20★ repoCreate a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
galyarderlabs/galyarder-framework/skills/writing-plans Skill
20★ repoUse when you have a spec or requirements for a multi-step task, before touching code
galyarderlabs/galyarder-framework/skills/writing-skills Skill
20★ repoUse when creating new skills, editing existing skills, or verifying skills work before deployment
mehrad-dm/mastermind/skills/explain Skill
20★ repoUse when an internal package, module, or shared component has little or no usage documentation and people (or future AI sessions) keep using it wrong: "document this", "write docs for our library", onboarding someone onto an internal API, or handing a package to another team.
mehrad-dm/mastermind/skills/handoff Skill
20★ repoUse when work needs to survive losing context, before a /clear on a long task, when pausing something unfinished, when handing over to a teammate or the next session, when the context window is filling up on multi-day work, or when a long multi-step task starts re-covering ground it already finished. Not the project's decision history across weeks: that's `roadmap`.
mehrad-dm/mastermind/skills/help Skill
20★ repo⚗️ Experimental — A markdown brain that gives your AI coding tools judgment and rigor: sharp defaults, real decisions, and the discipline to verify before saying done. For Claude Code, Cursor and Codex. It improves itself over time.
mehrad-dm/mastermind/skills/init Skill
20★ repoUse on the first substantive work in a project MasterMind isn't set up for yet, when the user says "init", "initialize", "set up MasterMind", "onboard", "get me ready", or when no field pack matches the project's detected stack.
mehrad-dm/mastermind/skills/lab Skill
20★ repo⚗️ Experimental — A genius-builder brain for your AI coding tools: sharp defaults, real judgment, and the discipline to check their own work. For Claude Code, Codex, Cursor & Copilot. Just markdown; it improves itself over time.
mehrad-dm/mastermind/skills/learn Skill
20★ repoUse when a task depends on tech you don't actually know, an unfamiliar library, a fast-moving framework, a tricky API, an unfamiliar codebase: or whenever "I think it works like…" is load-bearing. Just-in-time and task-scoped; distinct from levelup, which updates the durable knowledge base.
mehrad-dm/mastermind/skills/levelup Skill
20★ repo⚗️ Experimental — A markdown brain that gives your AI coding tools judgment and rigor: sharp defaults, real decisions, and the discipline to verify before saying done. For Claude Code, Cursor and Codex. It improves itself over time.
mehrad-dm/mastermind/skills/perf Skill
20★ repoUse when something is slow — "why is this slow", "optimize this", "make it faster", jank, lag, a slow query, slow page load, slow render, slow build, high memory, a timeout. Not for correctness bugs; that's debug.
mehrad-dm/mastermind/skills/persona Skill
20★ repoUse when the user wants code written in the documented public style of a named engineer they admire: "write this like Dan Abramov", "make it read like Kent C. Dodds", "in the style of that OSS author". For a public figure with a real body of work; a private colleague's style is `signature` (quarantine-gated). A lens on taste, never impersonation.
mehrad-dm/mastermind/skills/prompt Skill
20★ repoUse ONLY when the user explicitly asks to improve a prompt aimed at an AI: "improve my prompt", "fix this prompt", "how should I ask for this", "make this prompt better". A prompt pasted to be answered or executed is a task, not a rewrite request: do that task instead. About prompts for an AI, not about optimizing code.
mehrad-dm/mastermind/skills/qa Skill
20★ repoUse after finishing a feature or fix to confirm it actually works, when the user says "test this", "does it work", "verify this", "QA it", or before shipping something that has never been driven end-to-end. Also when the user asks for tests to be written or wants to work test-first.
mehrad-dm/mastermind/skills/report Skill
20★ repoUse when the user asks for a written record of what was done: "write it up", "give me a report", "summarize what you changed", "document this cycle": or at the end of a build/QA cycle ONLY if the project's cycle-report preference is on. Off by default: never produce one unprompted, and skip it for a one-line change.
mehrad-dm/mastermind/skills/route Skill
20★ repo⚗️ Experimental — A markdown brain that gives your AI coding tools judgment and rigor: sharp defaults, real decisions, and the discipline to verify before saying done. For Claude Code, Cursor and Codex. It improves itself over time.
mehrad-dm/mastermind/skills/signature Skill
20★ repo⚗️ Experimental — A markdown brain that gives your AI coding tools judgment and rigor: sharp defaults, real decisions, and the discipline to verify before saying done. For Claude Code, Cursor and Codex. It improves itself over time.
mehrad-dm/mastermind/skills/spec Skill
20★ repoUse when the ask is ambiguous, the scope is unclear, terms are being used inconsistently, the work spans multiple files, or it will be handed to another session. Symptoms: "make it better", "add the thing", or disagreement about what's in scope. Skip for a clear one-line change.
mehrad-dm/mastermind/skills/spike Skill
20★ repoUse when the right approach is genuinely unknown and reality will teach faster than planning — a risky unvalidated assumption, an unfamiliar integration, "will this even work", "try something quick". The result is explicitly throwaway and does not ship.
helderberto/agent-skills/skills/build Skill
20★ repoImplement one phase of a plan — reads the plan, finds the next incomplete phase, implements it with feedback loops, marks checkboxes, offers a commit (one phase per invocation). Use after /plan when a plan exists at `.specs/plans/<slug>.md`, or when the user asks to build or implement the next phase. Don't use for ad-hoc changes with no plan (use /tdd) or to check progress (use /test).
helderberto/agent-skills/skills/code-review Skill
20★ repoReview a GitHub Pull Request for bugs, security, performance, and code quality. Use when user asks to review a PR or wants pull request feedback. Don't use for reviewing local uncommitted changes, creating new PRs, or merging branches.
helderberto/agent-skills/skills/code-simplify Skill
20★ repoSimplify working code without changing behavior — reduce complexity, remove dead abstractions, favor clarity over cleverness. Use when code works but is harder to read or maintain than it should be, or the user asks to "simplify", "clean up", "reduce complexity", or "make this clearer". Don't use to add features or backfill tests (use /tdd or /fortify), design a new interface (use /codebase-design), or review a PR (use /code-review).
helderberto/agent-skills/skills/codebase-design Skill
20★ repoShared 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.
helderberto/agent-skills/skills/commit Skill
20★ repoGroup unstaged changes into atomic commits by concern, following repository style. Use when user asks to "commit", "create a commit", "commit changes", or "/commit". Don't use for pushing (that belongs to /ship) or creating pull requests.
helderberto/agent-skills/skills/create-adr Skill
20★ repoRecord an Architecture Decision Record (ADR) — a 1–3 sentence note capturing what was decided and why. Use when user says "create an ADR", "record this decision", "/create-adr", or just decided something architecturally significant. Don't use for forward-looking specs (use /spec) or general repo conventions (use CLAUDE.md).
helderberto/agent-skills/skills/create-pull-request Skill
20★ repoCreate a GitHub pull request — fills the repo's PR template, conventional-commit title, ticket refs. Draft mode via `--draft`.
helderberto/agent-skills/skills/create-skill Skill
20★ repoCreate new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill, or asks "make a skill for X". Don't use for benchmarking or optimizing a skill's triggering with evals (use skill-creator), or for one-off prose edits to an existing skill.
helderberto/agent-skills/skills/deps-audit Skill
20★ repoCheck dependencies for known vulnerabilities and staleness. Use when user asks to "audit dependencies", "/deps-audit", "check for vulnerabilities", or wants to check dependency health. Don't use for reviewing code quality.
helderberto/agent-skills/skills/diagnose Skill
20★ repoDisciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
helderberto/agent-skills/skills/domain-modeling Skill
20★ repoActively build and sharpen a project's domain model — challenge terms, pin down a ubiquitous language, and write the glossary and decisions down as they crystallize. Use when the user wants to define domain terminology, resolve ambiguous terms, or when another skill needs the shared vocabulary. Don't use for recording a single architectural decision (use /create-adr) or explaining existing code (use /explain-code).
helderberto/agent-skills/skills/e2e Skill
20★ repoWrite end-to-end tests for user flows using Cypress. Use when user asks to "write e2e tests", "/e2e", "add Cypress tests", or wants to test a user flow end-to-end. Don't use for unit tests, component tests, or projects using Playwright, Puppeteer, or other non-Cypress frameworks.
helderberto/agent-skills/skills/explain-code Skill
20★ repoExplains code with visual diagrams and analogies. Use when explaining how code works, walking through a codebase area, or when the user asks "how does this work?" Don't use for modifying code, fixing bugs, generating new implementations, or multi-session concept learning (use /teach).
helderberto/agent-skills/skills/fortify Skill
20★ repoFortify existing code by splitting large functions, adding edge-case coverage, and backfilling unit tests. Use when user asks to "fortify", "harden", "bulletproof", "make robust", "make solid", "strengthen", "add missing tests", "split functions", or wants to improve reliability of existing code. Don't use for new features (use tdd), refactoring plans, or code review (use code-review).
helderberto/agent-skills/skills/frontend-ui-engineering Skill
20★ repoFront-load UI construction decisions — component boundary and prop API, where state lives, data/async, the required UI states (loading/empty/error), responsive behavior, and accessibility by construction. Use when creating or refactoring a component, page, or design-system primitive. Don't use for pure logic (tdd), throwaway direction exploration (prototype), generic module design (codebase-design), or auditing finished UI (a11y-audit/perf-audit/visual-validate).
helderberto/agent-skills/skills/grill-me Skill
20★ repoA relentless interview to sharpen a plan or design. Use when the user wants to stress-test a plan, pressure-test assumptions, or says "grill me" or "poke holes in this". Don't use for code review (use /code-review) or gathering initial requirements (use /spec).
helderberto/agent-skills/skills/handoff Skill
20★ repoCompact the current conversation into a handoff document for another agent to pick up. Use when the user wants to hand off, transfer context to a fresh session, or says "write a handoff". Don't use to summarize for the current session (just answer) or to brief on plan progress (use /test).
helderberto/agent-skills/skills/harden Skill
20★ repoHarden code proactively against vulnerabilities at the boundary where untrusted input enters the system. Use when implementing auth, handling user input, storing or transmitting sensitive data, integrating external APIs, adding file uploads, or any code that crosses a trust boundary. Don't use for reactive secret scanning (use `safe-repo`) or dependency CVE checks (use `deps-audit`).
helderberto/agent-skills/skills/i18n Skill
20★ repoAudit internationalization coverage and find hardcoded strings. Use when user asks to "check i18n", "/i18n", "find hardcoded strings", "check translations", or wants to verify translation coverage. Don't use for backend string extraction, non-frontend code, or projects without an i18n library.
helderberto/agent-skills/skills/lint Skill
20★ repoRun linting and formatting checks. Use when user asks to "run linter", "/lint", "check linting", "fix lint errors", or requests code linting/formatting. Don't use for running tests or type-checking only.
helderberto/agent-skills/skills/perf-audit Skill
20★ repoAudit frontend bundle size and performance. Use when user asks to "audit performance", "/perf-audit", "analyze bundle", "check bundle size", or wants to find performance bottlenecks. Don't use for backend performance, database query optimization, or projects without a frontend build step.
helderberto/agent-skills/skills/plan Skill
20★ repoTurn a spec into a multi-phase implementation plan using tracer-bullet vertical slices. Use after /spec when a spec exists at `.specs/specs/<slug>.md`, or when the user asks to break work into phases or slices. Don't use without a spec, or for single-file changes with obvious scope.
helderberto/agent-skills/skills/prose-fix Skill
20★ repoFix prose formatting, typos, and clarity issues in markdown or text files. Use when user asks to "fix dashes", "fix typos", "clean up text", "improve sentences", or "/prose-fix". Don't use for code style, linting, or full rewrites.
helderberto/agent-skills/skills/prototype Skill
20★ repoBuild a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to explore or compare design directions before committing, or says "prototype", "mock up", or "try a few approaches". Don't use for production implementation (use /build or /tdd).
helderberto/agent-skills/skills/research Skill
20★ repoInvestigate a question against primary sources and capture the findings as a cited Markdown file. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent. Don't use for implementing against pinned dependency versions (use source-driven) or searching the current codebase (use grep/explore).
helderberto/agent-skills/skills/resolving-merge-conflicts Skill
20★ repoResolve an in-progress git merge or rebase conflict by recovering each side's intent, then finishing the merge. Use when a merge or rebase is mid-conflict, git reports conflicted files, or the user asks to resolve conflicts. Don't use for preventing future conflicts, general git operations, or rewriting history where nothing is conflicted.
helderberto/agent-skills/skills/review Skill
20★ repoOrchestrated REVIEW phase — fan out parallel, read-only reviewers over a diff (scope-detected audit skills AND independent agent lenses), then consolidate into one severity-ranked verdict. Use for a full pre-ship review, "review/validate this PR", or "spawn agents to review". Don't use to implement fixes (use /build or /tdd), for a single focused audit or one-lens pass (call it directly, e.g. /a11y-audit, /code-review), or to triage existing reviewer comments (use /triage-review).
helderberto/agent-skills/skills/revise Skill
20★ repoStructurally edit and improve article drafts — reorder sections, tighten arguments, improve clarity. Use when user asks to "revise", "improve my article", "edit my draft", or "/revise". Don't use for typo fixes or formatting (use prose-fix), code documentation, or non-article content.
helderberto/agent-skills/skills/safe-repo Skill
20★ repoCheck for sensitive data in repository. Use when user asks to "check for sensitive data", "/safe-repo", or wants to verify no company/credential data is in the repository. Use `--diff` mode to scope to staged + unstaged changes only (e.g., before commit). Don't use for general code review, adding .gitignore entries, or scanning non-git directories.