Skill Creator
barrydobson
41 published skills · 0 GitHub stars across the catalog. View on GitHub ↗
writing-plans
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
defense-in-depth-validation
Validate at every layer data passes through to make bugs impossible
root-cause-tracing
Systematically trace bugs backward through call stack to find original trigger
systematic-debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
verification-before-completion
Run verification commands and confirm output before claiming success
devops
Foundational instructions covering core DevOps principles, culture (CALMS), and key metrics (DORA) to guide agents in understanding and promoting effective software delivery.
getting-started-with-skills
Skills wiki intro - mandatory workflows, search tool, brainstorming triggers
github-actions
Comprehensive guide for building robust, secure, and efficient CI/CD pipelines using GitHub Actions. Covers workflow structure, jobs, steps, environment variables, secret management, caching, matrix strategies, testing, and deployment strategies.
go-developer
Instructions for writing Go code following idiomatic Go practices and community standards
creating-skills
TDD for process documentation - test with subagents before writing, iterate until bulletproof
gardening-skills-wiki
Maintain skills wiki health - check links, naming, cross-references, and coverage
installing-skills-system
Fork, clone to ~/.clank, run installer, edit CLAUDE.md
testing-skills-with-subagents
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
mkdocs
Best practices for developing documentation using mkdocs.
condition-based-waiting
Replace arbitrary timeouts with condition polling for reliable async tests
test-driven-development-tdd
Write the test first, watch it fail, write minimal code to pass
testing-anti-patterns
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.