Claude Skills

TDD-style testing methodology for skills using fresh subagent instances to prevent priming bias and validate skill effectiveness. Triggers: test skill, validate skill, skill testing, subagent testing, fresh instance testing, TDD for skills, skill validation Use when: validating skill improvements, testing skill effectiveness, preventing priming bias, measuring skill impact on behavior DO NOT use when: implementing skills (use skill-authoring instead), creating hooks (use hook-authoring instead)

Audit shell scripts for correctness, portability, and common pitfalls. Triggers: shell script, bash, sh, script review, pipeline, exit code Use when: reviewing shell scripts, CI scripts, hook scripts, wrapper scripts DO NOT use when: creating new scripts - use attune:workflow-setup

Generate language-specific Makefile with common development targets

Systematic methodology to reduce skill file size through externalization, consolidation, and progressive loading patterns. Triggers: large skill, skill optimization, skill size, 300 lines, inline code, skill refactoring, skill context reduction, skill modularization Use when: skills exceed 300 lines, multiple code blocks (10+) with similar functionality, heavy Python inline with markdown, functions >20 lines embedded DO NOT use when: skill is under 300 lines and well-organized. DO NOT use when: creating new skills - use modular-skills instead. Consult this skill when skills-eval shows "Large skill file" warnings.

Guide to effective Claude Code skill authoring using TDD methodology and persuasion principles. Triggers: skills, validation, skill, authoring, tdd, skill authoring, skill writing, new skill, TDD skills, skill creation, skill best practices, skill validation, skill deployment, skill compliance. Use when creating new skills, improving compliance, or validating quality before deployment. Do not use for evaluating existing skills (use skills-eval) or analyzing architecture (use modular-skills). Follow the Iron Law: write a failing test before writing any skill.

Shared utilities and constants for scribe plugin skills. This module provides common patterns, word lists, and utilities used across slop-detector, style-learner, and doc-generator.

Triggers: writing style, voice, tone, style guide, exemplar, style learning Learn and extract writing style patterns from exemplar text for consistent application. Triggers: learn style, extract style, style profile, writing voice, tone analysis, style guide generation, exemplar analysis Use when: creating a style guide from existing content, ensuring consistency across documents, learning a specific author's voice, customizing AI output style DO NOT use when: detecting AI slop - use slop-detector instead. DO NOT use when: just need to clean up existing content - use doc-generator with --remediate. Use this skill to build style profiles from exemplar text.

Delegate tasks to external LLM services (Gemini, Qwen) with quota, logging, and error handling.

Configure comprehensive three-layer pre-commit quality system with linting, type checking, and testing enforcement

Gemini CLI delegation workflow implementing delegation-core for Google's Gemini models.

Multi-LLM deliberation framework for strategic decisions through pressure-based expert consultation

Transform project brief into detailed, testable specifications using spec-driven development methodology

Enforces "prove before claim" discipline - validation, testing, and evidence requirements before declaring work complete. Triggers: validation, definition-of-done, proof, acceptance-criteria, testing, completion, finished, done, working, should work, configured, ready to use, implemented, fixed, improvement validated, workflow optimized, performance improved, issue resolved. Use when claiming work is complete, recommending solutions, or finishing implementations. Do not use when asking questions or for work clearly in-progress. MANDATORY: This skill is required before any completion claim.

Surfaces expert frameworks and proven methodologies before creating OR evaluating skills, hooks, agents, or commands. Helps select approaches from domain masters. Triggers: methodology, framework, expert approach, best practices, masters, proven method, domain expertise, how should I approach, what's the best way, evaluate skill, review methodology, is this grounded, optimization check. Use when starting creation workflows, evaluating methodology gaps, or seeking domain expertise. Do not use if you already have a specific methodology or are fixing syntax/structural issues.

Generate or remediate documentation with human-quality writing and style adherence. Triggers: documentation, generate docs, write docs, technical writing, generate documentation, write readme, create guide, doc generation, remediate docs, polish content, clean up docs. Use when creating new documentation, rewriting AI-generated content, or applying style profiles. Do not use for slop detection only (use slop-detector) or learning styles (use style-learner).

Triggers: session, resume, rename, checkpoint Manage Claude Code sessions with naming, checkpointing, and resume strategies. Use when: organizing long-running work, creating debug checkpoints, managing PR reviews

Detect and flag AI-generated content markers in documentation and prose. Triggers: ai slop, ai-generated, llm markers, chatgpt phrases, claude tells, slop detection, ai cleanup, humanize text, remove ai markers, detect chatgpt, detect llm, writing quality, ai tells. Use when reviewing documentation for AI markers, cleaning up LLM-generated content, or auditing prose quality. Do not use when generating new content (use doc-generator) or learning writing styles (use style-learner).

Triggers: safety, critical, NASA, power of 10, defensive coding, assertions, bounds checking Guidelines from NASA's Power of 10 rules for writing robust, verifiable code. Adapted for general software development with context-appropriate rigor. Use when: Writing critical code paths, reviewing for robustness, improving code quality DO NOT use: As rigid requirements for all code - match rigor to consequence