Manage Spec Kit presets via `specify preset`. USE FOR: listing installed presets as text or JSON, installing/removing presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling/disabling presets, setting resolution priority, or managing preset catalogs. DO NOT USE FOR: full artifact composition stacks (use speckit-artifact), extensions (use speckit-extension), bundles (use speckit-bundle), or workflows (use speckit-workflow).
2623d agoReviewMountCreate a free account to mount
Check for and apply Spec Kit CLI updates via `specify self`. USE FOR: checking whether a newer specify-cli release is available, previewing an upgrade with --dry-run, upgrading the CLI in place (optionally to a pinned tag). DO NOT USE FOR: checking project tools/integrations (use speckit-check) or managing extensions/presets/integrations/workflows.
2623d agoReviewMountCreate a free account to mount
Manage and run Spec Kit automation workflows via `specify workflow`. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use speckit-extension), presets (use speckit-preset), or bundles (use speckit-bundle).
2623d agoReviewMountCreate a free account to mount
Manage Spec Kit workflow step types via `specify workflow step`. USE FOR: listing built-in and custom workflow step types, installing/removing a custom step type from a catalog, searching/showing step-type info, managing step-type catalog sources. DO NOT USE FOR: running or installing whole workflows (use speckit-workflow), or bundles (use speckit-bundle).
2623d agoReviewMountCreate a free account to mount
Scan repository dependencies for known vulnerabilities using the GitHub MCP Server's Dependabot toolset and the GitHub Advisory Database. Use when asked to check dependency security, audit lockfiles, or verify packages before merging.
206mo agoReviewMountCreate a free account to mount
How to fetch the latest github/gh-aw release binary — either as the gh CLI extension (gh aw ...) or as a raw platform binary downloaded from GitHub Releases — including how to resolve the latest tag, pick the right asset, and verify its checksum.
1558d agoReviewMountCreate a free account to mount
Prepare a marketplace release, fix catalog inconsistencies, or retire a stale plugin. Use whenever asked to get a catalog ready to release, check changed plugin versions and changelogs, draft marketplace release notes including confirmed first releases with no file changes, or retire or remove a plugin from the marketplace. Don't use for a single contribution's PR draft, remote pin updates alone, or publishing without approval.
Add an outside plugin to this marketplace or deliberately update its pinned upstream release. Use whenever asked to pin, re-pin, or update an outside plugin's release, ref, or commit SHA in the catalog, including from a supplied offline snapshot. Don't use to edit a local plugin, install upstream code, or update npm dependencies.
Add a new plugin to this marketplace: its folder, plugin.json, README, CHANGELOG, catalog entry, and root README listing. Use whenever asked to add, create, scaffold, or register a new plugin in a marketplace checkout. Don't use for writing a plugin's skills or agents, editing an existing plugin, or Copilot pricing questions.
Prepare a marketplace plugin contribution or update for a pull request. Use whenever asked to get a plugin ready for a pull request, bump its version or changelog, flag compatibility changes, and write the pull request description. Don't use for a catalog-wide release, generic PRs, or publishing without approval.
Try a new or edited marketplace plugin from your current local checkout in a fresh host session before opening a pull request. Use for local development, Copilot CLI or VS Code discovery checks, and optional explicit installation checks. Don't use to publish a plugin or test a remote catalog pin.
Draft a structured pull request description in chat from supplied change notes, commit summaries, or a diff. Use when asked to write or format a general PR description or summary. Don't use for marketplace plugin submission or version/changelog bumps (use submit-plugin), scaffolding plugins, reviewing code for defects, or unrelated questions.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.
GitHubSkill