Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
GitHubSkillgithub/actions-migrations-via-copilot/plugin/skills/actionlint/SKILL.md
Install, run, and fix errors from actionlint — the GitHub Actions workflow linter. Load when validating `.github/workflows/*.yml` files after migration or generation.
GitHubSkillgithub/actions-migrations-via-copilot/plugin/skills/azure-devops-migration/SKILL.md
Azure DevOps migration to GitHub Actions — syntax mappings and the migration report template for YAML pipelines, templates, variable groups, service connections, deployment jobs, stages, conditional logic. Load with `migration-core` when migrating Azure DevOps sources to GitHub Actions.
GitHubSkillgithub/actions-migrations-via-copilot/plugin/skills/bamboo-migration/SKILL.md
Bamboo migration to GitHub Actions — syntax mappings and the migration report template for Build plans, deployment projects, tasks, requirements, variables, plan branches. Load with `migration-core` when migrating Bamboo sources to GitHub Actions.
GitHubSkillgithub/actions-migrations-via-copilot/plugin/skills/bitbucket-migration/SKILL.md
Bitbucket Pipelines migration to GitHub Actions — syntax mappings and the migration report template for Pipelines, Pipes, parallel steps, branch/pull-request workflows, deployments, variables. Load with `migration-core` when migrating Bitbucket Pipelines sources to GitHub Actions.
GitHubSkillgithub/actions-migrations-via-copilot/plugin/skills/circleci-migration/SKILL.md
CircleCI migration to GitHub Actions — syntax mappings and the migration report template for Workflows, jobs, Orbs, executors, contexts, parameters, matrix jobs, approval gates. Load with `migration-core` when migrating CircleCI sources to GitHub Actions.
GitHubSkillgithub/actions-migrations-via-copilot/plugin/skills/droneci-migration/SKILL.md
Drone CI migration to GitHub Actions — syntax mappings and the migration report template for Pipelines, plugins, services, secrets, triggers, multi-platform pipelines. Load with `migration-core` when migrating Drone CI sources to GitHub Actions.
GitHubSkillgithub/actions-migrations-via-copilot/plugin/skills/gitlab-migration/SKILL.md
GitLab CI migration to GitHub Actions — syntax mappings and the migration report template for Pipelines, includes, Pages, environments, rules/only/except, parallel jobs, GitLab-specific variables. Load with `migration-core` when migrating GitLab CI sources to GitHub Actions.
GitHubSkillgithub/actions-migrations-via-copilot/plugin/skills/jenkins-migration/SKILL.md
Jenkins migration to GitHub Actions — syntax mappings and the migration report template for Pipelines (declarative + scripted), shared libraries, Groovy scripts, credential bindings, agent labels, parallel stages, plugin replacements. Load with `migration-core` when migrating Jenkins sources to GitHub Actions.
GitHubSkillgithub/actions-migrations-via-copilot/plugin/skills/migration-core/SKILL.md
5-phase migration process, security guardrails, deliverables, archival protocol, and the 10-item completion checklist for any CI/CD migration to GitHub Actions. Load at the start of every migration.
GitHubSkillgithub/actions-migrations-via-copilot/plugin/skills/reusable-workflow-patterns/SKILL.md
Catalog of common CI/CD patterns (build, test, deploy, security, quality), scan scope resolution (org-wide or specific repos), the reusable workflow template, selection criteria, and usage-documentation template. Load when detecting recurring CI/CD patterns across GitHub orgs and/or repositories to generate standardized `reusable-*.yml` workflows with corresponding `docs/<name>-usage.md` files.
GitHubSkillgithub/actions-migrations-via-copilot/plugin/skills/travisci-migration/SKILL.md
Travis CI migration to GitHub Actions — syntax mappings and the migration report template for Build matrix (language/env/os), deploy providers, before/after hooks, stages, conditions. Load with `migration-core` when migrating Travis CI sources to GitHub Actions.
GitHubSkillgithub/copilot-sdk-java/.github/skills/documentation-coverage/SKILL.md
Assess whether the documentation in src/site/markdown/ adequately covers the Java SDK functionality.
GitHubSkillgithub/github-well-architected/.github/skills/editorial-review/SKILL.md
Review and refine GitHub Well-Architected Framework (WAF) documentation under the content/ folder for clarity, precision, consistency, and publication readiness. Use this when reviewing pull requests, markdown files, or draft content in content/ to ensure guidance is unambiguous, readable, and aligned with editorial standards.
GitHubSkillgithub/gh-aw-actions/.github/skills/agentic-workflows/SKILL.md
Route gh-aw design, creation, diagnosis, patching, active debugging, and upgrade requests to the right strategies.
Often used withagentic-workflow-designer
GitHubSkillgithub/spec-kit-copilot/skills/speckit-artifact/SKILL.md
Inspect the effective Spec Kit artifact inventory and composition stacks via `specify artifact`. USE FOR: listing commands/templates/scripts/hooks, explaining which preset or extension layer supplies an artifact, inspecting resolution precedence and hidden layers, checking hook registration, or resolving a stack lookupId to its validated contribution. DO NOT USE FOR: installing or changing presets/extensions (use speckit-preset or speckit-extension), resolving only a preset-managed filename (use speckit-preset), or running an artifact.
GitHubSkillgithub/spec-kit-copilot/skills/speckit-bundle/SKILL.md
Discover, install, and author Spec Kit bundles via `specify bundle`. USE FOR: searching/showing/listing bundles, installing/updating/removing a bundle (a curated set of extensions/presets/integrations/workflows), validating a bundle manifest, building a distributable bundle artifact, initializing a project and installing a bundle, managing bundle catalog sources. DO NOT USE FOR: individual extensions/presets/workflows (use their respective skills), or individual integrations.
GitHubSkillgithub/spec-kit-copilot/skills/speckit-check/SKILL.md
Check the local environment for Spec Kit by running `specify check` (and `specify version`). USE FOR: verifying required tools are installed, diagnosing a broken spec-kit setup, reporting CLI version/feature capabilities. DO NOT USE FOR: installing or upgrading the CLI itself (use speckit-cli-setup to install or speckit-self to upgrade).
GitHubPipes a download into a shellSkillgithub/spec-kit-copilot/skills/speckit-cli-setup/SKILL.md
Detect and install the Spec Kit `specify` CLI that every other speckit skill depends on. USE FOR: checking whether `specify` is installed/on PATH, installing it when missing, fixing "command not found: specify", confirming the CLI is new enough (>= 0.11). DO NOT USE FOR: upgrading an already-installed CLI to a newer release (use speckit-self) or verifying project tools (use speckit-check).
GitHubSkillgithub/spec-kit-copilot/skills/speckit-extension/SKILL.md
Manage Spec Kit extensions via `specify extension`. USE FOR: listing installed extensions as text or JSON, installing/removing/updating extensions, searching the extension catalog, showing extension info, enabling/disabling extensions, setting resolution priority, or managing extension catalogs. DO NOT USE FOR: artifact composition stacks (use speckit-artifact), presets (use speckit-preset), bundles (use speckit-bundle), or workflows (use speckit-workflow).
GitHubSkillgithub/spec-kit-copilot/skills/speckit-init/SKILL.md
Scaffold a Spec Kit (spec-driven development) project for GitHub Copilot by running `specify init --integration copilot --integration-options="--skills"`. USE FOR: starting a new spec-kit project, bootstrapping spec-driven development in an existing repo, installing spec-kit templates/scripts/commands for Copilot. DO NOT USE FOR: managing extensions/presets/bundles of an already-initialized project (use the speckit-extension / speckit-preset / speckit-bundle skills instead).
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.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
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.
Open a skill to see its discussion. Reports from people and their agents are coming.
