jaktestowac/awesome-copilot-for-testers / plugins/creating-skills/skills/creating-skills
creating-skills
VerifiedCreates GitHub Copilot skills with reusable workflows, companion resources, and validation gates. Use when packaging repeatable expertise into a `SKILL.md` folder, deciding what belongs in the skill body versus resources, or producing install-ready skill examples for a team or collection.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.2 KB |
| resources/SKILL.example.md | markdown | 1.9 KB |
| resources/SKILL.template.md | markdown | 1.5 KB |
| resources/skill-quality-checklist.md | markdown | 1.7 KB |
resources/skill-quality-checklist.md
View on GitHub# Skill Quality Checklist
Use this checklist before finalizing a GitHub Copilot skill.
## Discovery and naming
- [ ] The folder name and frontmatter `name` match exactly.
- [ ] The name describes an activity, not just a topic.
- [ ] The description explains both what the skill does and when to use it.
- [ ] The description includes realistic trigger phrases or contexts.
## Skill body
- [ ] The introduction is concise and explains the purpose clearly.
- [ ] The body teaches a repeatable workflow.
- [ ] The workflow is concrete enough to execute without inventing missing steps.
- [ ] The skill defines what a good outcome looks like.
- [ ] The skill ends with a clear definition of done or completion criteria.
## Supporting resources
- [ ] Templates, examples, or checklists exist when they reduce ambiguity.
- [ ] Resource filenames are descriptive.
- [ ] Supporting files stay one level deep from the skill root.
- [ ] The `SKILL.md` body links to supporting files instead of duplicating them.
## Separation of concerns
- [ ] The skill does not try to define an agent personality.
- [ ] The skill does not duplicate repository instructions that should always apply.
- [ ] The skill does not act like a prompt that only kicks off one narrow command.
## Final handoff
- [ ] The bundle is install-ready.
- [ ] The skill is distinct from other nearby skills.
- [ ] The skill would still make sense to someone who did not author it.
## Smells that should trigger a rewrite
- a vague name like `helpers`, `best-practices`, or `playwright`
- a description that never says when to use the skill
- a huge `SKILL.md` with buried examples and no resource files
- a workflow made of slogans instead of actions
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |