plugin-creator

Plugin plugin-creator from marketplace jamie-bitflight-skills in Jamie-BitFlight/claude_skills. Commands read from the repo's manifest — 25 days ago.

Skills (48)

• add-doc-updater

  Add 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 whe

• agent-capability-analyzer

  Runs 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 a

• agent-creator

  Create or adapt Claude Code agent definitions. Use when creating an agent, changing subagent configuration, selecting agent scope, or designing a specialized delegation role.

• agentskills

  Agent 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.

• arl

  Knowledge 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 designi

• assessment-reporting

  Format and score completed plugin assessment findings, including whether evidence admits a finding to the requested outcome. Use when a plugin assessment or review needs the standard report structure, scoring criteria, severity breakdown, marketplace-readiness result, or finding admission.

• assessor

  Assess a plugin and produce an executable refactoring design, task plan, and context manifest. Use when preparing systematic plugin refactoring.

• audit-agent-lifecycle

  Audit 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 learni

• audit-skill-completeness

  Evaluate 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-li

• audit-skill-lifecycle

  Audit skill lifecycle by tracing call chains, detecting circular dependencies, finding instruction contradictions, identifying duplicated datasets, analyzing bidirectional coherence, discovering scriptable sequences, and learning patterns. Use when checking skill coherence, validating skill workflow

• claude-plugins-reference-2026

  Claude Code plugin and marketplace router. Use when creating plugins, configuring component paths, resolving installed files, validating plugin roots, or distributing local, Git, and archive sources.

• claude-session-data-schema-reference

  Claude Code session log schema — JSONL record types, message structure, tool call/result pairing, subagent file locations, team session layout, task/plan/team configuration paths. Use when parsing ~/.claude/projects/**/*.jsonl files, writing PostToolUse hooks that measure response sizes, building se

• claude-skills-overview-2026

  Claude Code runtime skills router. Use when configuring SKILL.md frontmatter, discovery, invocation, hooks, context forks, substitutions, loading behavior, or headless skill dispatch.

• claude-subagent-reference

  Claude Code subagent runtime and plugin-agent reference. Use when creating, configuring, or debugging subagent definitions, nested spawning, startup context, model precedence, or plugin field restrictions.

• command-development

  Create and configure slash commands for Claude Code — the legacy .claude/commands/ format. Use when asked to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "intera

• component-patterns

  Decide which plugin component type to use and how to organize components at scale. Covers the component lifecycle (discovery and activation phases), decision framework for choosing between commands, skills, agents, hooks, and MCP servers, and organization patterns for each component type. Use when a

• ensemble-rule-review

  Design pattern for converting rule-following, checklist, or rubric skills into a fan-out map-reduce ensemble of parallel rigid sub-agents with corroboration-weighted merge; worker model tier and diversity are knobs matched to inference load and stakes, not fixed values. Apply when creating or refact

• ensure-complete

  Validate a completed plugin refactor against its task evidence, baseline assessment, documentation, and current validators. Use after implement-refactor or when deciding whether refactoring is complete.

• evaluate-and-tighten-skills

  Compatibility router for semantic skill tightening. Delegate goal recovery, authority, semantic conservation, evaluation contracts, and instruction optimization to Skill Lapidary rather than duplicating that system in Plugin Creator.

• feature-discovery

  Autonomous feature research and gap analysis. Use when starting /add-new-feature or analyzing existing architecture documents. Explores codebase patterns, identifies ambiguities, and produces feature-context-{slug}.md for orchestrator RT-ICA phase. Does NOT make technical decisions.

• hook-creator

  Guide for creating Claude Code plugin hooks — language selection heuristic (Node.js default, match project runtime when obvious), hooks.json configuration, event selection, prompt-based vs command hooks, ${CLAUDE_PLUGIN_ROOT} paths, stdio suppression, timeout sizing, and testing. Use when adding hoo

• hooks-core-reference

  Hook system fundamentals — all events, configuration structure, matchers per event type, environment variables, execution behavior, security, and debugging. Use when creating hooks, understanding hook events, matchers, configuration locations, environment variables, or troubleshooting hook issues.

• hooks-guide

  Cross-platform hooks reference for AI coding assistants — Claude Code, OpenAI Codex, GitHub Copilot, Cursor, Windsurf, and Amp. Covers hook authoring in Node.js (ESM and CJS) and Python, per-platform event schemas, inline-agent hooks and MCP in agent frontmatter, common JSON I/O, exit codes, best pr

• hooks-io-api

  Hook JSON input/output API reference — what data hooks receive via stdin and what JSON they can return to control Claude Code behavior. Use when writing hook scripts, checking exit code behavior, building JSON output for PreToolUse permissions, or understanding event-specific input schemas.

• hooks-patterns

  Hook recipes and working examples — plugin hooks, frontmatter hooks in skills/agents/commands, prompt-based LLM hooks, and complete code examples in Python and Node.js. Use when building hook scripts, integrating hooks into plugins, implementing prompt-based hooks, or looking for hook configuration

• implement-refactor

  Execute an assessor task file and every generated follow-up in dependency order. Use when a refactoring task file already exists.

• lint

  Use when checking skill quality, validating frontmatter before commit, or diagnosing validator warnings. Runs the plugin validator on a skill, agent, or plugin directory — reports token complexity, broken links, frontmatter issues, and structural problems. Pass the path as an argument.

• mcp-integration

  Integrate MCP servers into Claude Code plugins — covers .mcp.json configuration, plugin.json mcpServers field, server types (stdio, SSE, HTTP, WebSocket), environment variable expansion, tool naming conventions, OAuth and token authentication, security best practices, and testing workflows. Use when

• memory-and-rules

  Configure and manage Claude Code persistent memory (CLAUDE.md, auto memory, rules) across sessions. Use when setting up project memory, organizing .claude/rules/, managing auto memory files, creating CLAUDE.md with imports, debugging memory loading, or advising on memory hierarchy and best practices

• mission-statement

  Define and develop plugin mission statements — purpose, values, anti-patterns, and trade-offs. Use when creating a new plugin, auditing an existing plugin's alignment, or providing a reference for the alignment check loop to evaluate decisions against. Produces mission.json with [draft] status and w

• optimize-claude-md

  Optimize existing CLAUDE.md, SKILL.md, agent definitions, and other AI-facing files for Claude comprehension and economy. Scope: optimization of existing content only — not upstream sync, not read-only auditing. Measures baseline metrics, delegates to the ai-doc-optimizer agent with file-type-specif

• optimize

  Use when writing delegation instructions to subagents, authoring CLAUDE.md files, rules, skills, or agent definitions, or auditing existing AI-facing content for bloat. Activates on "write a rule for", "add to CLAUDE.md", "create an agent", "update memory", or any request to author AI-facing instruc

• output-style-creator

  Create, validate, and diagnose Claude Code output styles — the file that sets Claude's role, tone, and response format for every turn. Use when asked to write, bundle, or force an output style for a plugin, to set keep-coding-instructions or force-for-plugin, when a style is not taking effect or the

• plugin-creator-meta-docs

  Plugin creator documentation index. Load when needing to read about plugin validation error codes, skill creation, agent creation, or plugin structure.

• plugin-creator

  Use when creating a new Claude Code plugin from scratch — orchestrates prerequisite check, user discussion, parallel research, design with verification, atomic implementation, multi-layer validation, documentation, and final verification. For existing plugin improvement, use /plugin-creator:plugin-l

• plugin-lifecycle

  Orchestrate the full plugin development lifecycle from blank canvas to marketplace-ready. Use when creating a new plugin, improving an existing plugin, fixing validation errors, or taking a plugin through assessment, research, design, creation, debugging, optimization, and verification. Complements

• plugin-settings

  Per-project plugin configuration via .local.md files — covers the .claude/plugin-name.local.md pattern for storing user-configurable settings with YAML frontmatter and markdown body. Use when implementing plugin settings, reading YAML frontmatter from hooks, creating configuration-driven behavior, m

• prompt-optimization

  Optimize CLAUDE.md files and Skills for Claude Code CLI. Use when reviewing, creating, or improving system prompts, CLAUDE.md configurations, or Skill files. Transforms negative instructions into positive patterns following Anthropic's official best practices.

• refactor-plugin

  Start a complete plugin refactoring workflow that analyzes plugin structure, creates a refactoring plan with tasks, and guides through execution. Use when you need to refactor an entire plugin — triggers assessment, design, planning, and parallel agent execution phases.

• refactor-skill

  Assess and refactor oversized or multi-domain skills. First determines whether splitting or references/ extraction is appropriate — then executes the correct action. Use when a skill exceeds token thresholds (SK006/SK007) or covers multiple independent domains. Performs candidate assessment before a

• review-permissions

  Configure Claude Code permissions — tool approval rules, permission modes, managed policies, and sandboxing. Use when setting up permission rules, configuring allow/deny/ask policies, debugging permission prompts, deploying managed settings for organizations, or controlling Bash/Read/Edit/WebFetch/M

• shared-content-references

  Store instructional prose once and reference it from multiple skills or agents instead of duplicating it. Use when the same steps, rules, or reference material appear in two or more SKILL.md or agent files in one plugin, when deciding whether a shared doc belongs in the plugin-root docs directory or

• skill-creator

  Use when creating a new skill or updating an existing skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Activates on "create a new skill", "add a skill to plugin", or "update existing skill".

• skill-goal-extractor

  Compatibility router for skill goal recovery and authority assessment. Delegate to Skill Lapidary's establish-validatable-goals capability rather than maintaining a second goal-contract system in Plugin Creator.

• skill-sync

  Sync a skill's content against the upstream library it covers — check whether the API descriptions, version references, and SOURCE: citations inside SKILL.md and its reference files still reflect what the library actually does today. Use when a library has released updates that may have changed the

• start-refactor-task

  Start or complete a specific refactoring task from a task file. Use when a sub-agent needs to pick up a refactoring task, update its status, implement acceptance criteria, and run verification steps.

• subagent-refactoring-methodology

  Analysis criteria, transformation patterns, output format, and validation checklist for refactoring Claude Code agent prompt files. Load this skill when preparing to run the subagent-refactorer agent or when reviewing agent prompt files for structural, model optimization, or instruction quality impr

• write-frontmatter-description

  Write or tighten the description field of a skill or agent so the right one loads. Use when creating a skill or agent, when a description is vague, bloated, or missing triggers, when YAML multiline or quoting breaks the frontmatter, or when choosing between a model-invoked and a user-invoked skill.

Subagents (15)

• agent-creator

  Create or modify Claude Code agents for project, user, or plugin scope. Use when a request needs an agent definition or agent configuration change.

• ai-doc-optimizer

  Optimize AI-facing prompts, skills, agents, and CLAUDE.md with RT-ICA and CoVe checks. Use when existing instructions need clearer execution.

• analyzer

  Analyze blind comparison or benchmark results for causal differences and actionable evidence. Use after skill A/B comparisons or benchmark runs.

• comparator

  Compare two skill outputs blind and select the stronger result. Use for skill-iteration A/B evaluation.

• focused-reviewer

  Review one target against one supplied rule slice and write reducer-ready findings. Use as a parallel worker in ensemble or checklist reviews.

• grader

  Grade skill-eval transcripts and outputs against assertions. Use when an evaluation run needs evidence-based PASS/FAIL results.

• hook-creator

  Create, test, and wire Claude Code hooks at plugin, project, user, or agent scope. Use for hook events, enforcement, or context injection.

• plugin-assessor

  Assess Claude Code plugin structure, references, citations, and marketplace readiness. Use for plugin audits or pre-submission review.

• refactor-executor

  Execute approved plugin-refactoring task files with dependency-aware delegation. Use when a refactoring plan is ready for implementation.

• refactor-planner

  Create dependency-aware plugin-refactoring plans from validated findings. Use before systematic plugin improvements or SK006/SK007 remediation.

• refactor-validator

  Validate completed plugin refactors without modifying files. Use after refactoring to verify task evidence, structure, links, and regressions.

• skill-auditor

  Audit skill quality and purpose-appropriate completeness without changing skill files. Use for structural scoring, best-practice review, or eval-scenario suggestions.

• skill-content-updater

  Check skill SOURCE citations for upstream drift or execute an approved skill-sync change plan. Use during skill-sync drift and write stages.

• skill-sync-source-validator

  Validate and pre-fetch SOURCE URLs from a skill-sync change plan. Use between skill-sync synthesis and write execution.

• subagent-refactorer

  Refactor Claude Code agent definitions while preserving their executable contract. Use when agent instructions, tools, routing, or outputs need focused improvement.

MCP servers (1)

• sequential_thinking

  runs: npx -y @modelcontextprotocol/server-sequential-thinking@latest

Similar plugins