Skill Creator
athola
61 published skills · 4,823 GitHub stars across the catalog. View on GitHub ↗
development-workflow
detailed development workflow with modular patterns for git, code review, testing, documentation, and deployment
escalation-governance
Guide to deciding whether to escalate from a lower model (haiku/sonnet) toa higher model (sonnet/opus).Triggers: model escalation, haiku to sonnet, sonnet to opus, reasoning depth,task complexity, model selection, capability trade-offUse when: evaluating whether to escalate models, facing genuine complexityrequiring deeper reasoning, novel patterns with no existing solutions,high-stakes decisions requiring capability investmentDO NOT use when: thrashing without investigation - investigate root cause first.DO NOT use when: time pressure alone - urgency doesn't change task complexity.DO NOT use when: "just to be safe" - assess actual complexity instead.NEVER escalate without investigation first. This is the Iron Law.
hook-authoring
Complete guide for writing Claude Code and SDK hooks with security-first design.Triggers: hook creation, hook writing, PreToolUse, PostToolUse, UserPromptSubmit,tool validation, logging hooks, context injection, workflow automationUse when: creating new hooks for tool validation, logging operations for audit,injecting context before prompts, enforcing project-specific workflows,preventing dangerous operations in productionDO NOT use when: logic belongs in core skill - use Skills instead.DO NOT use when: complex multi-step workflows needed - use Agents instead.DO NOT use when: behavior better suited for custom tool.Use this skill BEFORE writing any hook. Check even if unsure.
hooks-eval
detailed hook evaluation framework for Claude Code and Agent SDK hooks.Triggers: hook audit, hook security, hook performance, hook compliance,SDK hooks, hook evaluation, hook benchmarking, hook vulnerabilityUse when: auditing existing hooks for security vulnerabilities, benchmarkinghook performance, implementing hooks using Python SDK, understanding hookcallback signatures, validating hooks against compliance standardsDO NOT use when: deciding hook placement - use hook-scope-guide instead.DO NOT use when: writing hook rules from scratch - use hookify instead.DO NOT use when: validating plugin structure - use validate-plugin instead.Use this skill BEFORE deploying hooks to production.
makefile-dogfooder
Analyze and enhance Makefiles for complete user functionality coverage.Triggers: Makefile analysis, Makefile gaps, missing targets, plugin release,Makefile coverage, build targets, make dogfood, plugin qualityUse when: analyzing Makefile completeness before releasing plugins, identifyinggaps during plugin maintenance, scoring Makefiles against best practices,verifying Makefiles support standard developer workflowsDO NOT use when: writing initial Makefiles from scratch.DO NOT use when: debugging specific build target failures.DO NOT use when: creating custom non-standard build systems.Use this skill BEFORE releasing any plugin to verify Makefile coverage.
shared-patterns
Reusable patterns and templates for Claude Code skill and hook development.Triggers: validation patterns, error handling, testing templates, workflow patterns,shared patterns, reusable templates, DRY patterns, common workflowsUse when: creating new skills or hooks that need consistent patterns, implementingvalidation logic, setting up error handling, creating test scaffolding,referencing standard workflow structuresDO NOT use when: pattern is specific to one skill only.DO NOT use when: pattern is still evolving - wait for stability.DO NOT use when: pattern is context-dependent requiring variations.Reference these patterns to validate consistency across the ecosystem.
skill-authoring
Guide to effective Claude Code skill authoring using TDD methodology andpersuasion principles.Triggers: skill authoring, skill writing, new skill, TDD skills, skill creation,skill best practices, skill validation, skill deployment, skill complianceUse when: creating new skills from scratch, improving existing skills withlow compliance rates, learning skill authoring best practices, validatingskill quality before deployment, understanding what makes skills effectiveDO NOT use when: evaluating existing skills - use skills-eval instead.DO NOT use when: analyzing skill architecture - use modular-skills instead.DO NOT use when: writing general documentation for humans.YOU MUST write a failing test before writing any skill. This is the Iron Law.
feature-review
Feature review and prioritization with RICE/WSJF/Kano scoring. Creates GitHub issues for suggestions.Triggers: feature review, prioritization, RICE, WSJF, roadmap, backlogUse when: reviewing features or suggesting new featuresDO NOT use when: evaluating single feature scope - use scope-guard.
scope-guard
Prevents overengineering through worthiness scoring, opportunity cost comparison,and branch threshold monitoring.Triggers: scope creep, overengineering, worthiness score, branch size, YAGNI,feature evaluation, scope validation, anti-overengineering, opportunity costUse when: evaluating features during brainstorming, planning new functionality,branches approach size limits (1000/1500/2000 lines, 15/25/30 commits)DO NOT use when: feature is already approved and in progress.DO NOT use when: simple bug fixes with clear scope.Use this skill BEFORE implementing any new feature. This is NON-NEGOTIABLEfor scope control.
authentication-patterns
Authentication patterns for external services: API keys, OAuth, token management, verification.Triggers: authentication, API keys, OAuth, token management, credentialsUse when: integrating external services or implementing authentication flows
error-patterns
Standardized error handling patterns with classification, recovery, and logging strategies.Triggers: error handling, error recovery, graceful degradation, resilienceUse when: implementing error handling in production plugins
evaluation-framework
Generic weighted scoring and threshold-based decision framework for evaluatingartifacts against configurable criteria.Triggers: evaluation, scoring, quality gates, decision framework, rubrics,weighted criteria, threshold decisions, artifact evaluationUse when: implementing evaluation systems, creating quality gates, designingscoring rubrics, building decision frameworksDO NOT use when: simple pass/fail without scoring needs.Consult this skill when building evaluation or scoring systems.
mecw-patterns
MECW theory and patterns for hallucination prevention via context management. Implements 50% rule.Triggers: MECW, context window, hallucination, 50% rule, context pressureUse when: implementing context-aware systems or monitoring context pressure
progressive-loading
Context-aware progressive module loading with hub-and-spoke pattern for token optimization.Triggers: progressive loading, lazy loading, hub-spoke, module selectionUse when: optimizing skill loading or reducing upfront context usage
pytest-config
Standardized pytest configuration for plugin development with shared test patterns.Triggers: pytest configuration, conftest, fixtures, test setupUse when: setting up pytest for plugin development or creating fixtures
quota-management
Quota tracking, threshold monitoring, and graceful degradation for rate-limited API services.Triggers: quota, rate limiting, usage limits, thresholdsUse when: integrating rate-limited services or tracking API usage
service-registry
Registry pattern for managing external service connections, configurations,and health checks.Triggers: service registry, service discovery, health checks, service configuration,multi-service integration, unified execution, service managementUse when: managing multiple external services, implementing health checks,centralizing service configuration, unified service executionDO NOT use when: single service integration without registry needs.Consult this skill when implementing service registry patterns.
storage-templates
Generic template patterns and lifecycle stages for knowledge storage,configuration management, and structured documentation.Triggers: storage templates, lifecycle stages, maturity progression, namingconventions, knowledge storage, configuration templates, documentation patternsUse when: organizing knowledge storage, managing configuration lifecycle,creating structured documentation, establishing naming conventionsDO NOT use when: simple storage without lifecycle or structure needs.Consult this skill when designing storage and documentation systems.
testing-quality-standards
Shared testing quality metrics and standards for cross-plugin use. Referencedby pensive:test-review and parseltongue:python-testing.Triggers: testing standards, quality metrics, coverage thresholds, test quality,anti-patterns, testing best practices, quality gatesUse when: evaluating test quality, setting coverage thresholds, identifyingtesting anti-patterns, establishing quality standardsDO NOT use when: simple scripts without quality requirements.Consult this skill when establishing testing quality standards.
usage-logging
Session-aware usage logging for audit trails, cost tracking, and analytics with JSONL format.Triggers: usage logging, audit trails, cost tracking, session logging, analytics, structured logging, JSONLUse when: implementing audit trails, tracking costs, collecting usage analytics, managing session loggingDO NOT use when: simple operations without logging needs.Consult this skill when implementing usage logging and audit trails.
knowledge-intake
Process external resources into actionable knowledge with evaluation, storage, and application decisions.Triggers: knowledge intake, article evaluation, paper review, external resourceUse when: user shares links to articles, papers, or external resourcesDO NOT use when: searching existing knowledge - use knowledge-locator.
review-chamber
Capture and retrieve PR review knowledge in project memory palaces
github-initiative-pulse
Generate program dashboards, GitHub-ready comment digests, and CSV summariessourced from Minister's tracker data.Triggers: initiative pulse, status report, weekly update, stakeholder briefing,github dashboard, blocker radar, initiative health, program metricsUse when: creating status reports, weekly updates, stakeholder briefings,generating GitHub comment digests, tracking initiative healthDO NOT use when: release gates/readiness - use release-health-gates.DO NOT use when: project planning - use spec-kit:speckit-orchestrator.Outputs markdown digests and CSV exports for GitHub issues and PRs.
release-health-gates
Declarative release readiness checklist that mirrors GitHub checks,deployment issues, and documentation requirements.Triggers: release gates, release readiness, deployment checklist, release review,quality signals, rollout scorecard, QA handshake, deployment gatesUse when: preparing releases, validating deployment gates, conducting releasereviews, embedding release gate snippets in PRsDO NOT use when: weekly status updates - use github-initiative-pulse.DO NOT use when: code reviews - use pensive review skills.Standardizes release approvals with GitHub-aware checklists.