Menu
An example custom skill.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | skill |
| description | An example custom skill. |
An example custom skill. See references/template.md for an example of a
nested file that the agent can read at runtime.
An example custom skill version for demonstration.
Reviews the work just done and updates CLAUDE.md, agent memories, and subagent MD files to reflect any new conventions, packages, resources, or patterns discovered. Run after completing any significant implementation task.
Plans and scaffolds Anthropic API endpoints as Terraform resources/data sources without a task management tool. TRIGGER when: user says "implement GitHub issues", references a range of GitHub issues to implement (e.g. "issues 52 to 57"), asks to parallelize implementation of multiple resources/data sources, or says "implement all [API name] APIs" or "work on a new API" (e.g. /v1/skills, /v1/environments). Generates GitHub issues and branches if they to not already exist — one per resource/data source — ready for sequential or parallel implementation.
Plans and scaffolds Anthropic API endpoints as Terraform resources/data sources for Vibe Kanban. TRIGGER when: user says "implement GitHub issues", references a range of GitHub issues to implement (e.g. "issues 52 to 57"), asks to parallelize implementation of multiple resources/data sources, or says "implement all [API name] APIs". Creates Vibe Kanban issues, workspaces, and fires parallel agents — one per resource/data source.
Updates the GitHub PR description for the current branch based on the work done in the current Claude session. Use after any meaningful change to a PR (feature, fix, refactor, docs). Invoked automatically when Claude stops if an open PR exists for the current branch. Also works inside Vibe Kanban worktrees (vk/* branches) by resolving the PR via the VK issue context.
Creates a branch named from the work done, commits all changes with a detailed conventional-commit message, pushes to GitHub, and opens a PR (or updates the existing PR description if one already exists) whose title and body come directly from the commit message.
