This repository stores reusable skills for coding agents.
The goal is to keep these skills in one trusted place, then retrieve or copy them into other repositories when needed. This avoids pulling instructions from unknown sources and makes it easier to review what an agent is allowed to load.
skills/
caveman/
SKILL.md
fill-pr-template/
SKILL.md
grill-me/
SKILL.md
grill-with-docs/
SKILL.md
ADR-FORMAT.md
CONTEXT-FORMAT.md
handoff/
SKILL.md
llm-council/
SKILL.md
tdd/
SKILL.md
deep-modules.md
interface-design.md
mocking.md
refactoring.md
tests.md
tutor/
SKILL.md
REFERENCE.md
EXAMPLES.md
write-a-rule/
SKILL.md
write-a-skill/
SKILL.md
Each skill lives in its own directory. The required entry point is SKILL.md.
Some skills also include supporting documentation that is referenced from the
main skill file.
| Skill | Purpose |
|---|---|
caveman |
Enables an ultra-compressed communication mode that keeps technical accuracy while reducing filler and token usage. |
fill-pr-template |
Drafts a pull request description from the current branch diff, commits, and repository PR template. |
grill-me |
Stress-tests a plan or design by asking focused questions until the decision tree is clear. |
grill-with-docs |
Stress-tests a plan against project language and documentation, then updates CONTEXT.md and ADRs as decisions are made. |
handoff |
Writes a compact handoff document so another agent or future session can continue the work. |
llm-council |
Runs any decision or tradeoff through a council of 5 independent AI advisors, anonymous peer-review, and chairman synthesis. |
tdd |
Guides test-driven development with a red-green-refactor loop and behavior-focused tests. |
tutor |
Explains codebase architecture, technological choices (ADRs), mathematical equations, and algorithms, teaches concepts with interactive quizzes, and exports/synchronizes explored knowledge to a Notion workspace. |
write-a-rule |
Helps create or edit .agents/rules/*.md files with YAML frontmatter, scoped globs, and concise project-specific guidance. |
write-a-skill |
Helps create new skills with the expected structure, metadata, and supporting files. |
From the repository where you want to use the skills, copy either all skills or
one specific skill into .agents/skills.
npx skills@latest add Vlor999/skillsAn interface will ask you what you want. You'll be able to pick the ones that makes sense for you
mkdir -p .agents/skills
git clone --depth 1 --filter=blob:none --sparse https://github.com/Vlor999/skills.git /tmp/coding-agent-skills
git -C /tmp/coding-agent-skills sparse-checkout set skills
cp -R /tmp/coding-agent-skills/skills/* .agents/skills/Replace tdd with the skill you want:
mkdir -p .agents/skills
git clone --depth 1 --filter=blob:none --sparse https://github.com/Vlor999/skills.git /tmp/coding-agent-skills
git -C /tmp/coding-agent-skills sparse-checkout set skills/tdd
cp -R /tmp/coding-agent-skills/skills/tdd .agents/skills/If you prefer an npx style command, you can use degit to copy a single
skill directory:
mkdir -p .agents/skills
npx degit Vlor999/skills/skills/tdd .agents/skills/tddReplace tdd with any available skill name.
Ask your coding agent to use the skill by name:
Use the tdd skill to implement this feature test-first.
Or:
Use grill-me to challenge this design before we implement it.
If your agent supports a global skills directory, you can copy these skills
there instead of copying them into each project. Keep the full skill directory,
not only SKILL.md, because some skills depend on sibling reference files.
Treat skills as executable instructions for an agent. Before installing or copying a skill into another repository, review:
SKILL.md- Any referenced files in the same skill directory
- Any scripts or assets bundled with the skill
This repository is intended to be the reviewed source of truth. Prefer copying skills from here instead of downloading random prompts or instructions directly into project repositories.
Recommended practices:
- Keep skills small and readable.
- Avoid hidden behavior or unnecessary scripts.
- Prefer plain Markdown instructions unless a deterministic helper script is truly useful.
- Review changes in pull requests before using updated skills in sensitive repositories.
- Copy only the skills a repository needs.
Use write-a-skill to create new skills and write-a-rule to create or update repository rule files under .agents/rules/.
At minimum, create:
skills/my-skill/
SKILL.md
SKILL.md should start with front matter:
---
name: my-skill
description: Brief description of what the skill does. Use when the user asks for specific trigger cases.
---Keep the description clear and specific. It is what the agent sees when deciding whether to load the skill.
When changing a skill:
- Edit the skill in
skills/<skill-name>/. - Keep supporting files next to the skill that uses them.
- Review the diff carefully, especially instructions that allow file edits, shell commands, network access, or credentials.
- Copy the updated skill into any repositories that should use the new version.
This repository does not install skills automatically. It is a source repository for reviewed skill definitions that can be copied into coding-agent environments.