marketplace-analysis
Use when reviewing plugin quality, auditing plugins, analyzing the marketplace, checking plugins against Anthropic standards, or evaluating plugin architecture - provides systematic analysis methodology with validation framework
What this skill does
# Marketplace Analysis Analyze Claude Code plugins to achieve Anthropic-level quality standards. ## Core Philosophy **Anthropic Quality Bar**: Same or more functionality with leaner, more efficient implementation. **Principles:** - Systems thinking over point fixes - Elegant simplicity over feature accumulation - Proven improvements over assumptions - Deletion over addition ## Analysis Process ### 1. Quick Scan - Count plugins and components - Note obvious issues (large files, naming inconsistencies) - Flag files >500 lines ### 2. Deep Analysis (per plugin) 1. Read SKILL.md files - check trigger phrases, writing style 2. Read agent descriptions - check triggering examples 3. Read commands - check argument handling 4. Check hooks - validate event usage 5. Map interactions - how components work together ### 3. Cross-Plugin Analysis - Find redundancy across plugins - Check consistency (naming, patterns, styles) - Identify gaps and conflicts ### 4. Reference Validation For each skill, verify bundled references exist: 1. **Extract paths from SKILL.md:** - `references/*.md` mentions - `scripts/*.sh` or `scripts/*.py` mentions - Markdown links: `[text](relative/path)` 2. **Validate each path:** - Resolve relative to skill directory - Check file exists with Glob - Flag missing as "broken reference" 3. **Report:** - Missing references = Priority 1 errors - Orphaned files (exist but not referenced) = Priority 3 notes ## Anti-Overengineering Checks Before proposing ANY change: 1. Is this simpler than the original? 2. Does this solve a real problem? 3. Would a new user understand this? 4. Can I remove instead of add? **Red flags:** - Adding abstraction for one use case - "Might need this later" reasoning - Recommending deletion based on filename alone ## Output Format ```markdown ## Priority 1: High Impact, Low Effort - [ ] [Change] - [Why] - [Expected impact] - [How to validate] ## Priority 2: Medium Impact ... ## Priority 3: Consider Later ... ``` Each recommendation includes validation approach. ## References For detailed guidance: - **`references/skill-design-standards.md`** - **Official Anthropic skill-creator guide** (authoritative source for skill structure, frontmatter, progressive disclosure) - **`references/quality-standards.md`** - Quality criteria checklist, anti-patterns (includes summary of official standards) - **`references/measuring-improvements.md`** - Metrics, user testing, validation templates - **`references/output-patterns.md`** - Template and examples patterns for consistent output - **`references/workflows.md`** - Sequential and conditional workflow patterns Use `scripts/analyze-metrics.sh` for consistent metric collection. ## Consulting Documentation Verify best practices via `claude-code-guide` subagent before claiming something is "wrong." ## Applying Changes When implementing improvements: 1. **Before any changes:** Create TodoWrite items for each improvement 2. **Apply changes:** Use Edit tool, one logical change at a time 3. **MANDATORY verification:** Use `core:verification` skill before claiming complete 4. **Evidence required:** Run validation commands, report actual output **Never claim "improved" or "fixed" without verification evidence.**
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.