All authors
Claude Skills by Jamie-BitFlight
github.com/Jamie-BitFlight284 skills0 installs362 views
- Impact MeasurementQuantitative cost measurement for technical research — token injection costs, payload sizes, context window consumption, and file-level counts from actual repo files. Use when a technical-researcher orchestrator needs the cost dimension of adding or changing something: how many tokens will it inject, how big are the artifacts, what is the context window impact? This is NOT blast-radius analysis (which files break) — it covers size, tokens, and performance cost only.Votes: 0GitHub stars: 67
- Implement FeatureUse when the plan_ref returned by add-new-feature is provided. Executes the SAM implementation loop — opens an attempt per ready task, dispatches each to a specialist agent in parallel, settles and judges what comes back, manages bookend tasks (T0 baseline capture and TN verification), and tracks concerns and contract violations per task. Drives task state through the work ledger via the SAM CLI.Votes: 0GitHub stars: 67
- Implementation ManagerManages feature implementation task state via SAM MCP tools. Use when querying task status, listing ready tasks, dispatching tasks for execution, updating task timestamps, or coordinating multi-task feature rollout. Activated by the /dh:execution orchestrator to track progress — also activates directly when managing tasks.Votes: 0GitHub stars: 67
- InteropRoutes a Superpowers plan file through the /work-backlog-item pipeline and writes SAM task back-references and chunk annotations into the original plan. Use when given a path to a Superpowers plan file via $ARGUMENTS and needing to create a linked backlog item plus SAM task plan.Votes: 0GitHub stars: 67
- Kage BunshinSpawn and manage persistent interactive Claude Code CLI sessions with bidirectional communication via tmux. Provides spawn, send, read, status, list, and kill subcommands for orchestrating parallel peer sessions. Uses built-in --worktree and --tmux flags. Sessions stay alive for multi-turn steering. Triggers on "spawn claude session", "launch separate claude", "peer session", "inter-session communication", "shadow clone", "kage bunshin".Votes: 0GitHub stars: 67
- Meta Workflow Graph RefreshEntry point for refreshing the DH workflow graph. Use when skills, agents, Mermaid flowcharts, MCP tools, or artifact flows change and docs/dh-workflow-graph.json must remain current.Votes: 0GitHub stars: 67
- Multi Perspective ReviewUse when a diff needs four parallel perspective reviewers (Security, Performance, Quality, Accessibility). Creates an ephemeral SAM plan, collects structured verdicts, synthesizes them into one deduplicated cross-referenced punch list, prints one summary line per perspective, and exits non-zero if any perspective returns REJECT. SKIP is a passing outcome.Votes: 0GitHub stars: 67
- Planner Rt IcaSame reverse-thinking method as dh:rt-ica (see dh:rt-ica or dh-glossary for the definition), but localizes any MISSING input to the affected task only, as a non-blocking information-completeness pre-pass before task decomposition and plan generation. Use when grooming backlog items, generating plans, decomposing tasks under uncertainty, or working in brownfield and refactor scenarios. Produces completeness summary (APPROVED-FOR-PLANNING, APPROVED-WITH-GAPS, or BLOCKED-FOR-PLANNING), missing i...Votes: 0GitHub stars: 67
- PlanningUse when Stage 1 Discovery is complete and design must begin — transforms the ARTIFACT:DISCOVERY into an actionable ARTIFACT:PLAN via RT-ICA prerequisite verification. Produces approach, components, success criteria, acceptance tests, and risks. Blocks on missing prerequisites before design proceeds.Votes: 0GitHub stars: 67
- Research NoteSynthesis step in the multi-angle technical research pipeline. Receives structured outputs from all four research angles (api-state, ecosystem-research, impact-measurement, codebase-auditor), applies cross-angle signal weighting and conflict resolution, and produces a single synthesized Research section. Invoked by the technical-researcher orchestrator after all angle skills complete. Returns content to the orchestrator — does not write to the backlog.Votes: 0GitHub stars: 67
- Review Verdict ContractLoad the shared verdict, punch-list, SKIP, and gate schema used by the dh multi-perspective review orchestrator, reviewers, and synthesizer. Use only when one of those components must produce, parse, validate, or gate review results.Votes: 0GitHub stars: 67
- Rt IcaWorks backward from the stated goal through its prerequisite chain — what must exist to reach the goal, then what each of those requires, back to the current state — classifying each prerequisite as AVAILABLE, DERIVABLE, or MISSING, and blocking planning until nothing is MISSING. Use before creating plans, delegating to agents, or defining acceptance criteria. Activates on specs, PRDs, tickets, RFCs, architecture designs, and multi-step engineering tasks. Always pass `#N` or an inline goal — ...Votes: 0GitHub stars: 67
- Setup Skill DiscoveryUse when creating or updating the project skill discovery config — generates or regenerates .dh/skill_discovery.yaml by scanning the repo to infer tech stack, inventorying installed skills via npx skills list, loading candidate skill content before suggesting, and writing a config-driven skill injection file. Triggers on /dh:setup-skill-discovery invocations and programmatic --auto calls from add-new-feature Phase 3.Votes: 0GitHub stars: 67
- Start TaskUse when executing a task the orchestrator dispatched — reads the task and its orchestrator response from the work ledger, loads task-level skills, implements against acceptance criteria, records divergences and the completion report as task sections, and closes the attempt. Triggers on task execution within the implement-feature loop or when an agent picks up a specific task from a plan.Votes: 0GitHub stars: 67
- Subagent ContractWhere a dispatched step puts its output, and how it signals state upstream.Votes: 0GitHub stars: 67
- Task DecompositionDecomposes a contextualized plan into atomic, independently executable tasks with complete embedded context, registered through the plan API. Use after SAM Stage 3 Context Integration produces the contextualized plan artifact — when the plan is ready for task generation with CLEAR ordering, CoVe checks, and dependency graphs for parallel execution.Votes: 0GitHub stars: 67
- Test Failure MindsetUse when investigating failing tests or deciding whether to change the test or product. Validate test expectations against authoritative intent, trace product and test boundaries, and require evidence for the correction rather than automatic code fixes or test dismissal.Votes: 0GitHub stars: 67
- Validation ProtocolScientific validation protocol for verifying fixes work through observation, not assumption. Use when claiming a bug fix, code change, refactoring, or implementation is complete — enforces reproduce-broken-state then define-success-criteria then apply-fix then verify-outcome. Success means observing intended behavior, not absence of errors.Votes: 0GitHub stars: 67
- Verify DoneRigorous self-assessment checklist before marking any task as complete. Use when about to claim task completion, before final commit, when user asks "is it done?", or when transitioning from implementation to reporting. Prevents premature completion claims by requiring evidence for every assertion.Votes: 0GitHub stars: 67
- Work Backlog ItemUse when creating, grooming, planning, or closing a backlog item. Bridges backlog items to SAM planning with issue, project, and milestone tracking against the configured backend. Activates on interactive browsing with no arguments, loading an item by issue reference or title match to run grooming and SAM planning, autonomous unattended runs that substitute evidence-derived decisions for clarifying questions, a quick path for one-file fixes where full grooming is disproportionate, dismissing ...Votes: 0GitHub stars: 67
- Work MilestoneExecutes a groomed milestone with parallel kage-bunshin sessions in isolated worktrees. Use when a milestone has been groomed and /groom-milestone has produced a dispatch plan. Reads the dispatch plan, creates an integration branch, spawns one kage-bunshin (independent claude -p process) per wave item in its own worktree — each session is a full orchestrator with the Agent tool. Sequentially merges worktree branches, relays wave discoveries to subsequent waves, then lands the integration bran...Votes: 0GitHub stars: 67
- Dot DashUse when starting, stopping, or checking the dot-dash live session dashboard — a real-time browser UI that monitors all active Claude Code sessions, streams transcripts, and supports prompt injectionVotes: 0GitHub stars: 67
- Fastmcp Client CliQuery and invoke tools on MCP servers using fastmcp list and fastmcp call. Use when you need to discover what tools a server offers, call tools, or integrate MCP servers into workflows.Votes: 0GitHub stars: 67
- Fastmcp CreatorUse when building, extending, or debugging FastMCP v4 (or v3) Python MCP servers. Activates on FastMCP tool/resource/prompt creation, provider and transform implementation (CodeMode, Tool Search), auth setup (MultiAuth, PropelAuth, KeycloakProvider), client SDK usage, FastMCPApp and Generative UI server building, fastmcp-slim client-only installs, nginx reverse proxy deployment, Prefab Apps, OTEL observability, testing, and v3→v4 migration. Grounded in official FastMCP v4 docs plus locally-ve...Votes: 0GitHub stars: 67
- Fastmcp Python TestsWrite and evaluate effective Python tests using pytest. Use when writing tests, reviewing test code, debugging test failures, or improving test coverage. Covers test design, fixtures, parameterization, mocking, and async testing.Votes: 0GitHub stars: 67
- RtfpUse when asked to find a rage moment, analyze a direct transcript path, or analyze a session time range. RTFP finds the strongest instruction-following failure in Claude or Codex sessions and renders a rage receipt.Votes: 0GitHub stars: 67
- Gitlab SkillUse when designing or validating GitLab CI/CD and automatic release lifecycles, inspecting pipeline and job state read-only, composing non-interactive merge-request commands, or setting up protected refs and release credentials. Also covers reusable components and inputs, GitLab Functions, gitlab-ci-local, glab command composition, and GitLab Flavored Markdown. For pipeline execution or retry requests, provide inspection and command drafting while leaving execution to the operator.Votes: 0GitHub stars: 67
- Holistic Linting OrchestratorCompatibility routing for callers that previously used the holistic-linting orchestrator workflow. Use only when an existing caller explicitly invokes this skill.Votes: 0GitHub stars: 67
- Holistic Linting ResolverCompatibility route for existing callers that supply files/scope or quality-gate evidence and need diagnosis and resolution.Votes: 0GitHub stars: 67
- Holistic LintingDiscover and run configured quality gates for requested or changed work, preserve diagnostics as evidence, route failures to the appropriate causal/domain capability, and verify corrections. Use for linting, formatting, type-checking, configured hook checks, or pre-completion quality verification.Votes: 0GitHub stars: 67
- LitellmWhen calling LLM APIs from Python code. When connecting to llamafile or local LLM servers. When switching between OpenAI/Anthropic/local providers. When implementing retry/fallback logic for LLM calls. When code imports litellm or uses completion() patterns.Votes: 0GitHub stars: 67
- LlamafileWhen setting up local LLM inference without cloud APIs. When running GGUF models locally. When needing OpenAI-compatible API from a local model. When building offline/air-gapped AI tools. When troubleshooting local LLM server connections.Votes: 0GitHub stars: 67
- Orchestrator Discipline Meta DocsOrchestrator discipline plugin documentation index. Load when needing to read about orchestration patterns, delegation rules, or context window management.Votes: 0GitHub stars: 67
- Orchestrator DisciplineOrchestrator context window discipline enforcement. Prevents the orchestrator from reading source files it will not edit, running diagnostic commands that waste context, and rationalizing delegation bypasses. Use when setting up orchestrator guardrails, reviewing delegation discipline, or diagnosing context window waste in multi-agent workflows. Activates PreToolUse hooks that surface decision points before source file reads and diagnostic command execution.Votes: 0GitHub stars: 67
- Perl Cpan EcosystemThis skill should be used when the user asks to install Perl modules, use cpanm, create a cpanfile, manage Perl dependencies, set up Carton, configure local lib, or mentions CPAN, cpanminus, module installation, or Perl package management.Votes: 0GitHub stars: 67
- Perl DevelopmentThis skill should be used when the user asks to "write a Perl script", "create Perl code", "modern Perl best practices", "Perl 5.30+", "use strict warnings autodie", or mentions Perl pragmas, subroutines, error handling, or scripting patterns. Provides comprehensive Perl 5.30+ development guidance.Votes: 0GitHub stars: 67
- Perl Environment SetupThis skill should be used when the user asks to "install perlbrew", "set up Perl environment", "install Perl version", "manage Perl versions", "switch Perl version", "install plenv", or mentions Perl version management, development environment setup, or multiple Perl installations.Votes: 0GitHub stars: 67
- Perl LintThis skill should be used when the user asks to lint Perl code, run perlcritic, check Perl style, format Perl code, run perltidy, or mentions Perl Critic policies, code formatting, or style checking.Votes: 0GitHub stars: 67
- Perl TestingThis skill should be used when the user asks to write Perl tests, test Perl code, use Test More, run prove, create test suite, mock Perl, or mentions Perl testing, TAP, Test Class, Test Deep, or test-driven development in Perl.Votes: 0GitHub stars: 67
- Perl ValidateThis skill should be used when the user asks to "validate Perl script", "check Perl syntax", "verify Perl code", "/perl-validate", or mentions script validation, compile check, security review, or best practice compliance for Perl code.Votes: 0GitHub stars: 67
- Example SkillIllustrative Claude Code skill configuration. Use when learning the basic SKILL.md shape; follow the canonical runtime reference for the current field inventory.Votes: 0GitHub stars: 67
- Add Doc UpdaterAdd automated documentation updater to any Claude skill. Creates a Python sync script that downloads upstream docs, processes markdown for AI consumption, and maintains local cache with configurable refresh. Collects template variables, then delegates implementation through 5-phase workflow. Use when adding auto-updating reference documentation to plugins or skills.Votes: 0GitHub stars: 67
- Agent Capability AnalyzerRuns the description-drift experiment — spawns all Claude Code agents simultaneously to collect self-reported capabilities, then compares them against static frontmatter descriptions to reveal how reliable orchestrator routing based on descriptions actually is. Use when measuring description drift across the agent fleet, re-running the capability collection experiment, analyzing a specific agent's self-reported capabilities, or auditing whether frontmatter descriptions accurately reflect agen...Votes: 0GitHub stars: 67
- Agent CreatorCreate or adapt Claude Code agent definitions. Use when creating an agent, changing subagent configuration, selecting agent scope, or designing a specialized delegation role.Votes: 0GitHub stars: 67
- AgentskillsAgent Skills portable format router. Use when creating cross-client skills, validating portable frontmatter, packaging skills for upload or API use, or implementing skill discovery and activation.Votes: 0GitHub stars: 67
- ArlKnowledge reference for Autonomous Refinement Loop research — pattern research into prerequisites for autonomous execution without synchronous human blocking gates. Defines failure categories, prerequisites, and conditions for replacing human judgment with machine-verifiable checks. Use when designing or evaluating autonomous agent loops, gate conditions, or HOOTL execution patterns.Votes: 0GitHub stars: 67
- Assessment ReportingFormat and score completed plugin assessment findings without starting another assessment workflow. Use when a plugin assessment needs the standard report structure, scoring criteria, severity breakdown, or marketplace-readiness result.Votes: 0GitHub stars: 67
- AssessorAssess a plugin and produce an executable refactoring design, task plan, and context manifest. Use when preparing systematic plugin refactoring.Votes: 0GitHub stars: 67
- Audit Agent LifecycleAudit agent lifecycle — validates agent execution capability against configuration. Accepts plugin path, runs 8 semantic audits (capability vs config alignment, skill loading correctness, inter-agent contracts, prompt contradictions, tool sufficiency, dead agents, scriptable patterns, pattern learning), writes reports to .plugin-creator/audits/. Use when auditing agent lifecycle, checking agent capabilities, verifying tool access, finding dead agents, validating agent contract alignment, or c...Votes: 0GitHub stars: 67
- Audit Skill CompletenessEvaluate a single skill's quality against its stated purpose. Classifies the skill's purpose type, then scores applicable quality categories — universal dimensions always apply; structural dimensions (scripts, references, assets) are scored only when warranted by the skill's purpose. A focused 20-line behavioral skill with no bundled resources scores fully on all applicable categories. Use when auditing skill quality, checking marketplace readiness, evaluating skill completeness, performing p...Votes: 0GitHub stars: 67