Skills for AI Coding Agents
A curated collection of skills for AI coding agents. A skill packages domain-specific knowledge and, optionally, runnable scripts that an agent can read and execute to perform a well-defined task — for example, removing speaker notes from a PowerPoint file.
Agents discover a skill by reading its SKILL.md, then follow the instructions and invoke the bundled scripts as needed.
Note
Start with the GitHub Copilot example below. See the Skills installation guide for other agents, installation scopes, local checkouts, and native marketplace/plugin methods.
Repository structure
.
├── AGENTS.md # Guidance for AI coding agents working in this repository
├── docs/ # Installation and maintenance guides
└── skills/
└── <skill-name>/
├── README.md # Required: human-facing overview, installation, and usage
├── SKILL.md # Required: skill description and usage instructions
├── plugin.json # Required: individual Copilot plugin metadata
├── thumbnail.png # Optional: rendered thumbnail
├── thumbnail.svg # Optional: editable thumbnail source
└── scripts/ # Optional: supporting scripts the skill runs
- Each skill lives in its own directory under
skills/<skill-name>/. <skill-name>is lowercase, hyphen-separated (kebab-case), e.g.pptx-denote.- Every skill directory must contain
README.md,SKILL.md, andplugin.json. The README introduces the skill, explains individual installation, and provides a usage example;SKILL.mdremains the authoritative agent instructions. The skill frontmatter name and plugin name must match the directory; the plugin's"skills": "./"exposes that directory'sSKILL.md. - Supporting code goes in a
scripts/subdirectory inside the skill. - Skills may include additional subdirectories for supporting resources, such as reference documents, templates, or rules, as documented in their
SKILL.md.
Available skills
| Skill | Description |
|---|---|
create-prd | Generate or update a product requirements document (PRD) from user-provided context and interviews to fill missing details. |
create-tdd | Generate or update a technical design document (TDD) from a required PRD and TRD through design proposals and adaptive interviews, with references to existing ADRs. |
create-trd | Generate or update a technical requirements document (TRD) as a PRD companion through adaptive interviews, asking to create a PRD first when missing. |
localizations | Localize content into the supported target locales using locale-specific rules. |
pptx-denote | Remove all slide notes from a PowerPoint presentation using the python-pptx library. |
Using a skill
-
Open a skill's README from the table above for an overview and individual installation, or install the collection using the instructions below.
-
Open the skill's
SKILL.mdand read the How it works section. -
Ask your agent to use the skill.
For example, ask GitHub Copilot CLI:
Use the pptx-denote skill to remove speaker notes from "my-presentation.pptx".
Installing skills
With GitHub Copilot CLI installed, add this repository as a marketplace, then install the collection's plugin from it:
copilot plugin marketplace add justinyoo/skills
copilot plugin install justinyoo-skills@justinyoo-skills
The justinyoo-skills plugin includes all skills in this collection. Alternatively, after registering the marketplace, browse and install an individual skill:
copilot plugin marketplace browse justinyoo-skills
copilot plugin install <skill-name>@justinyoo-skills
Replace <skill-name> with a listed name, such as create-prd. Choose the collection or individual plugins to avoid installing the same skill twice. For direct plugin installation, the npx skills method, local checkouts, and other coding agents, see the installation guide.
Adding a new skill
Assisted authoring with create-skill (recommended)
Use the external create-skill skill with your coding agent. Reuse an installation already available to the agent; if it is missing, obtain approval before installing it on demand. For GitHub Copilot:
npx skills add jongio/skills --skill create-skill -g --agent github-copilot
For other agent identifiers, see the installation guide. Then ask your agent to use create-skill, for example:
Use create-skill to create a skill named <skill-name> for <task>.
Use this repository's skills/ layout and preserve its existing custom content.
Let the skill collect missing requirements and produce a dry-run preview. Review the proposed files, target paths, prerequisites, and registration changes before approving the exact plan. Keep the helper external: do not add a bundled create-skill installation, repository-management framework, or authoring step to CI.
Manual authoring (fallback)
If the helper is unavailable or you prefer to author the skill directly:
- Create
skills/<skill-name>/. - Add a
SKILL.mdwith valid YAML frontmatter (name,description). - Add a
README.mdexplaining what the skill is for, how to install it with GitHub Copilot CLI, and one realistic usage prompt. Link toSKILL.mdfor the workflow and the shared installation guide for other methods. - Add
plugin.jsonwith the same skill name, a version matching its marketplace entry, and"skills": "./". - Place any executable code under the skill's
scripts/directory and document the exact invocation inSKILL.md. - List prerequisites (libraries, tools) and how to install them.
- Keep the skill self-contained, single-purpose, and idempotent where possible.
With either method, follow the skill-change checklist to keep the README, marketplace entries, plugin metadata, and any applicable dependency configuration consistent. See AGENTS.md for authoring conventions.
Repository maintenance
See repository maintenance for the skill-change checklist, dependency-free local repository tests, optional static skill linting, and CI behavior.
This repository contains the authored skills and their distribution manifests, not a bundled repository generator or create-skill installation. GitHub Actions installs the pinned validation tools into its temporary runner directory. GitHub Pages is not configured.
Contributing
Contributions of new skills are welcome. Follow the conventions in AGENTS.md and keep each skill focused on a single, well-defined task.