Content & Media

Guides Claude in creating well-structured SKILL.md files following best practices. Provides clear guidelines for naming, structure, and content organization to make skills easy to discover and execute.

This skill should be used when the user asks to "analyze my product", "research competitors", "find feature gaps", "create feature request", "prioritize backlog", "generate PRD", "plan roadmap", "what should we build next", "competitive analysis", "gap analysis", "sync issues", or mentions product management workflows. Provides AI-native PM capabilities for startups with signal-based feature tracking, the WINNING prioritization filter, and GitHub Issues integration with deduplication.

Universal challenge tracker with flexible cadence, intelligent insights, and cross-challenge learning detection. Use when user wants to track any personal challenge - learning, habits, building, fitness, creative, or custom. Supports daily, weekly, or N-day check-ins with type-adaptive preferences, backlog, and context files.

Systematic approach for creating minimal-change, reversible implementation plans. Claude invokes this skill when transforming requirements/research into executable blueprints. Emphasizes simplicity, safety, and clear verification steps.

Arma Reforger Workbench workflow, testing guidelines, and debugging patterns

Delegate tasks to external LLM services (Gemini, Qwen) with quota, logging, and error handling.Triggers: delegate task, external LLM, gemini, qwen, large context, offloadUse when: tasks exceed context window or need cheaper processingDO NOT use when: task requires Claude's reasoning.

Design, manage, and evolve digital gardens as living knowledge bases withinmemory palaces.Triggers: digital garden, knowledge base, linking, note curation, content lifecycle,garden maintenance, bidirectional links, knowledge evolutionUse when: managing note collections, creating link structures, maintainingknowledge bases, tending garden health and growthDO NOT use when: creating memory palace structures - use memory-palace-architect.DO NOT use when: evaluating new knowledge - use knowledge-intake.Consult this skill when cultivating and maintaining digital gardens.

Guide to formatting review deliverables for consistency, ensuring findingsare comparable across different types of analysis.Triggers: report formatting, deliverable structure, consistent output, reviewoutput, findings format, report template, output consistencyUse when: formatting final review outputs, ensuring consistent deliverablestructure, making findings comparable across reviewsDO NOT use when: capturing evidence during analysis - use evidence-logging.DO NOT use when: reviewing changes - use diff-analysis or review-core first.Consult this skill when formatting final review deliverables.

Construct temporary, session-specific memory palaces for complex projectsand conversations.Triggers: session context, project memory, conversation state, temporary storage,session palace, context preservation, complex project, extended conversationUse when: working on complex multi-step projects, preserving context acrossinterruptions, tracking session-specific stateDO NOT use when: permanent knowledge structures needed - use memory-palace-architect.DO NOT use when: searching existing knowledge - use knowledge-locator.Consult this skill for session-scoped temporary knowledge structures.

Gemini CLI delegation workflow implementing delegation-core for Google's Gemini models.Triggers: gemini cli, gemini delegation, google gemini, 1M context, large file analysis,gemini batch, gemini summarization, gemini extractionUse when: delegation-core selected Gemini, need Gemini's 1M+ token context window,batch processing or large document summarization requiredDO NOT use when: deciding which model to use - use delegation-core first.DO NOT use when: gemini CLI not installed or authenticated.Consult this skill when implementing Gemini-specific delegation workflows.

Systematically uncover and fix bugs using language-specific expertise andreproducible evidence.Triggers: bug hunting, defect detection, debugging, fix verification, bug fix,regression check, error investigation, defect documentationUse when: deep bug hunting needed, documenting defects, verifying fixes,systematic debugging requiredDO NOT use when: test coverage audit - use test-review instead.DO NOT use when: architecture issues - use architecture-review.Use this skill for systematic bug hunting with evidence trails.

Detect codebase bloat through progressive analysis: dead code, duplication, complexity, and documentation bloat.Triggers: bloat detection, dead code, code cleanup, duplication, redundancy, codebase health, technical debt, unused codeUse when: preparing for refactoring, context usage is high, quarterly maintenance, pre-release cleanupDO NOT use when: actively developing new features, time-sensitive bug fixes.DO NOT use when: codebase is < 1000 lines (insufficient scale for bloat).Progressive 3-tier detection: quick scan → targeted analysis → deep audit.

Audit Makefiles for duplication, portability, and idiomatic GNU Make usage.Triggers: Makefile review, build system, GNU Make, portability, deduplication,pattern rules, automatic variables, dependency graphUse when: auditing Makefiles, reviewing build system, checking portability,eliminating recipe duplicationDO NOT use when: creating new Makefiles - use abstract:make-dogfood.DO NOT use when: architecture review - use architecture-review.Use this skill for Makefile audit and optimization.

Evaluate and upgrade test suites with TDD/BDD rigor, coverage tracking,and quality assessment.Triggers: test audit, test coverage, test quality, TDD, BDD, test gaps,test improvement, coverage analysis, test remediationUse when: auditing test suites, analyzing coverage gaps, improving testquality, evaluating TDD/BDD complianceDO NOT use when: writing new tests - use parseltongue:python-testing.DO NOT use when: updating existing tests - use sanctum:test-updates.Use this skill for test suite evaluation and quality assessment.

Consolidate README content using language-aware exemplars, internal doc linkage,and reproducible evidence.Triggers: README update, documentation refresh, readme structure, exemplar research,language-aware docs, readme modernization, project documentationUse when: README requires structural refresh, adding features to documentation,aligning readme with exemplar standards, improving project presentationDO NOT use when: updating inline docs - use doc-updates.DO NOT use when: consolidating ephemeral reports - use doc-consolidation.Run git-workspace-review first to capture repo context.

Scope-focused PR code review that validates against original requirements androutes out-of-scope findings to GitHub issues.Triggers: PR review, pull request review, scope validation, requirement compliance,backlog triage, code review, blocking issuesUse when: reviewing PRs, validating against requirements, triaging findingsto backlog, preventing overengineeringDO NOT use when: preparing PRs - use pr-prep instead.DO NOT use when: deep code review - use pensive:unified-review.Use this skill for scope-focused PR reviews.

Evaluate codebase architecture against ADRs, coupling rules, and team guardrails.Triggers: architecture review, ADR audit, coupling analysis, design review,principle checks, Law of Demeter, architecture assessmentUse when: reviewing architecture decisions, auditing ADR compliance, analyzingcoupling, validating design principlesDO NOT use when: selecting architecture paradigms - use archetypes skills.DO NOT use when: API surface review - use api-review.Use this skill for architecture assessment and compliance.

Methodology for categorizing changes, assessing risks, and creating summariesfrom any changeset.Triggers: diff analysis, changeset review, risk assessment, change categorization,semantic analysis, release preparation, change summary, git diffUse when: analyzing specific changesets, assessing risk of changes, preparingrelease notes, categorizing changes by type and impactDO NOT use when: quick context catchup - use catchup instead.DO NOT use when: full PR review - use review-core with pensive skills.Use this skill for systematic change analysis with risk scoring.

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.

Update documentation with writing guideline enforcement, consolidation detection, and accuracy verification.Triggers: documentation update, docs update, ADR, docstrings, writing guidelines, readme update, debloat docsUse when: updating documentation after code changes, enforcing writing guidelines, maintaining ADRsDO NOT use when: README-specific updates - use update-readme instead.DO NOT use when: complex multi-file consolidation - use doc-consolidation.Use this skill for general documentation updates with built-in quality gates.