Skill Creator
axiomantic
28 published skills · 15 GitHub stars across the catalog. View on GitHub ↗
fun-mode
Use when starting a session and wanting creative engagement, or when user says '/fun' or asks for a persona
fact-checking
Use when reviewing code changes, auditing documentation accuracy, validating technical claims before merge, or user says "verify claims", "factcheck", "audit documentation", "validate comments", "are these claims accurate".
fixing-tests
Use when tests are failing, test quality issues were identified, or user wants to fix/improve specific tests
documentation-updates
Use after modifying library skills, library commands, or agents to ensure CHANGELOG, README, and docs are updated
instruction-optimizer
Use when instruction files (skills, prompts, CLAUDE.md) are too long or need token reduction while preserving capability
instruction-engineering
Use when: (1) constructing prompts for subagents, (2) invoking the Task tool, or (3) writing/improving skill instructions or any LLM prompts for maximum effectiveness
emotional-stakes
Use when writing subagent prompts, skill instructions, or any high-stakes task requiring accuracy and truthfulness
spellbook-auditing
Meta-audit skill for spellbook development. Spawns parallel subagents to factcheck docs, optimize instructions, find token savings, and identify MCP candidates. Produces actionable report.
merge-conflict-resolution
Use when git merge or rebase fails with conflicts, you see 'unmerged paths' or conflict markers (<<<<<<< =======), or need help resolving conflicted files
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable
using-lsp-tools
Use when mcp-language-server tools are available and you need semantic code intelligence for navigation, refactoring, or type analysis
worktree-merge
Use when merging parallel worktrees back together after parallel implementation with interface contracts
implementing-features
Use when building, creating, or adding functionality. Triggers: "implement X", "build Y", "add feature Z", "create X", "start a new project", "Would be great to...", "I want to...", "We need...", "Can we add...", "Let's add...". Also for: new projects, repos, templates, greenfield development. NOT for: bug fixes, pure research, or questions about existing code.
debugging
Use when debugging bugs, test failures, or unexpected behavior. Supports --scientific and --systematic flags for direct methodology selection.
finding-dead-code
Use when reviewing code changes, auditing new features, cleaning up PRs, or user says "find dead code", "find unused code", "check for unnecessary additions", "what can I remove".
async-await-patterns
Use when writing JavaScript or TypeScript code with asynchronous operations
design-doc-reviewer
Use when reviewing design documents, technical specifications, or architecture docs before implementation planning. Performs exhaustive analysis to ensure the design is specific enough to create a detailed, coherent, and actionable implementation plan without hand-waving or ambiguity.
green-mirage-audit
Use when reviewing test suites, after test runs pass, or when user asks about test quality - performs exhaustive line-by-line audit tracing code paths through entire program, verifying tests actually validate what they claim. Outputs structured report compatible with fix-tests skill.
implementation-plan-reviewer
Use when reviewing implementation plans before execution, especially plans derived from design documents. Performs exhaustive analysis to ensure the plan is detailed enough for agents to execute without guessing interfaces, data shapes, or dependencies. Verifies timeline structure, parallel/sequential work organization, QA checkpoints, and agent responsibilities.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.