Tools

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

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.

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.

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.

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.

Consolidates ephemeral LLM-generated markdown files into permanent documentation.Triggers: consolidate docs, untracked reports, ephemeral files, git cleanup,report consolidation, knowledge extraction, REPORT.md files, ANALYSIS.md filesUse when: you have untracked *_REPORT.md or *_ANALYSIS.md files, git statusshows markdown artifacts that shouldn't be committed, preparing PR and needto clean up working artifacts, preserving insights from code reviewsDO NOT use when: files are already in docs/ or skills/ locations.DO NOT use when: files are intentionally temporary scratch notes.DO NOT use when: source files have no extractable value.Merges valuable content into permanent documentation, then deletes source files.

Shared infrastructure and patterns for imbue analysis skills.Triggers: imbue patterns, todowrite patterns, evidence formats, analysis workflows,shared templates, imbue infrastructureUse when: other imbue skills need common patterns, creating new analysis skills,ensuring consistency across imbue pluginDO NOT use directly: this skill is infrastructure for other imbue skills.This skill provides shared patterns consumed by other imbue skills.

Lightweight preflight checklist for verifying repo path, staged changes, anddiffs before other workflows.Triggers: git status, preflight, workspace check, staged changes, diff review,git verification, repo stateUse when: verifying workspace state before other git operations, checkingstaged changes, preflight checks before commits or PRsDO NOT use when: full commit workflow - use commit-messages instead.DO NOT use when: full PR preparation - use pr-prep.Use this skill as foundation for git workflows.

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.

Shared infrastructure and patterns for spec-kit specification-driven development.Triggers: spec-kit patterns, tech-stack patterns, checklist dimensions,artifact structure, specification infrastructure, shared templatesUse when: developing new spec-kit skills, referencing standard patterns,ensuring consistency across specification workflowsDO NOT use directly: this skill is infrastructure for other spec-kit skills.Provides reusable patterns consumed by all spec-kit commands and skills.

Compose processing stages using a pipes-and-filters model for ETL, mediaprocessing, or compiler-like workloads.Triggers: pipeline architecture, pipes and filters, ETL, data transformation,stream processing, CI/CD pipeline, media processing, batch processingUse when: data flows through fixed sequence of transformations, stages can beindependently developed and tested, parallel processing of stages is beneficialDO NOT use when: selecting from multiple paradigms - use architecture-paradigms first.DO NOT use when: data flow isn't sequential or predictable.DO NOT use when: complex branching/merging logic dominates.Consult this skill when designing data pipelines or transformation workflows.

Combine multiple media assets (GIFs, videos) into composite tutorials.Supports vertical/horizontal layouts and sequential stitching.Triggers: combine media, stitch gifs, composite, merge recordingsUse when: combining terminal and browser recordings into a single tutorial

Python testing with pytest, fixtures, mocking, and TDD workflows.Triggers: pytest, unit tests, test fixtures, mocking, TDD, test suite, coverage,test-driven development, testing patterns, parameterized testsUse when: writing unit tests, setting up test suites, implementing TDD,configuring pytest, creating fixtures, async testingDO NOT use when: evaluating test quality - use pensive:test-review instead.DO NOT use when: infrastructure test config - use leyline:pytest-config.Consult this skill for Python testing implementation and patterns.

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.

Shared infrastructure and reusable modules for all pensive review skills.Triggers: pensive patterns, review workflow, output templates, quality checklists,pensive infrastructure, shared review patternsUse when: other pensive skills need common patterns, creating new review skills,ensuring consistency across pensive pluginDO NOT use directly: this skill is infrastructure for other pensive skills.This skill provides shared patterns consumed by other pensive skills.

CI/CD and operations practices including GitHub Actions, Kubernetes, and operational tooling. Use when working with deployment and infrastructure.

Prepare a pull request by validating the workspace, running quality gates,summarizing changes, and drafting the PR template.Triggers: PR preparation, pull request, quality gates, PR template, PR summary,branch preparation, merge requestUse when: preparing PRs for submission, running quality gates, draftingPR descriptions and templatesDO NOT use when: reviewing existing PRs - use pr-review instead.DO NOT use when: just generating commit messages - use commit-messages.Use this skill for PR preparation.

Workflow rules for task execution, respecting user code, and git commits. Use when planning or executing development tasks.

Manages practice rules. Use when user states a preference or approach, or asks to add/modify rules for coding, architecture, tooling, or best practices.