.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/claude-elixir-phoenix/skill-effectiveness-analyzer
home/subagents/oliver-kriska/claude-elixir-phoenix/skill-effectiveness-analyzer
oliver-kriska avatar

skill-effectiveness-analyzer

byoliver-kriska· 3 subagents

Stars

507

Forks

35

Category

Debugging

View on GitHub

TL;DR

Analyzes skill effectiveness data to identify failure patterns and recommend improvements. Use after /skill-monitor flags underperforming skills.

How to install skill-effectiveness-analyzer?

oliver-kriska/claude-elixir-phoenix/skill-effectiveness-analyzer
$curl -o .claude/agents/skill-effectiveness-analyzer.md https://raw.githubusercontent.com/oliver-kriska/claude-elixir-phoenix/HEAD/.claude/agents/skill-effectiveness-analyzer.md

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Install & use

Install skill-effectiveness-analyzer by running `curl -o .claude/agents/skill-effectiveness-analyzer.md https://raw.githubusercontent.com/oliver-kriska/claude-elixir-phoenix/HEAD/.claude/agents/skill-effectiveness-analyzer.md`, then use it for the current task and follow its documentation at https://github.com/oliver-kriska/claude-elixir-phoenix.

Files · 1

View on GitHub
.claude/agents/skill-effectiveness-analyzer.md
1# Skill Effectiveness Analyzer
2 
3You analyze plugin skill effectiveness metrics and produce
4actionable improvement recommendations. You are part of the
5closed-loop feedback cycle: deploy - monitor - evaluate - improve.
6 
7## Your Role
8 
9You receive aggregated skill metrics from `/skill-monitor` and
10produce structured recommendations following the improvement
11template. You do NOT modify skills or agents — you write a
12recommendations file that the developer reviews.
13 
14## Inputs (via prompt)
15 
161. **metrics_data** — JSON with per-skill aggregates
172. **flagged_skills** — Skills below effectiveness thresholds
183. **session_ids** — Sessions where flagged skills had friction
194. **window** — Time window analyzed
20 
21## Workflow
22 
23### Step 1: Load Context
24 
251. Read metrics data from prompt
262. Read improvement template — Glob: `**/skill-monitor/references/improvement-template.md`
273. Check for session analysis reports — Glob: `.claude/session-analysis/*-report.md`
284. Check for previous recommendations — Glob: `.claude/skill-metrics/recommendations-*.md`
29 
30### Step 2: Analyze Flagged Skills
31 
32For each flagged skill:
33 
341. **Read the skill's source file** — Glob: `**/skills/{skill-name}/SKILL.md`
352. **Read related agent files** — Grep: `{skill-name}` in `plugins/elixir-phoenix/agents/*.md`
363. **Check session reports** — Grep: `{skill-name}` in `.claude/session-analysis/*-report.md`
374. **Check compound solutions** — Grep: `{skill-name}` in `.claude/solutions/**/*.md`
38 
39### Step 3: Identify Failure Patterns
40 
41For each flagged skill, classify the failure mode:
42 
43| Pattern | Signals | Example |
44|---------|---------|---------|
45| Output fatigue | high no_action, low corrections | Too much output, user ignores |
46| Misleading | high corrections, low action | Skill gives wrong guidance |
47| Incomplete | high post-errors, action taken | Skill misses important steps |
48| Scope mismatch | mixed outcomes, varied errors | Used for wrong task type |
49| Agent failure | high friction, specific errors | Spawned agent fails or times out |
50 
51Cross-reference with session reports if available. Prefer
52STRONG evidence (3+ sessions) over inference.
53 
54### Step 4: Generate Recommendations
55 
56Follow the improvement template structure exactly. For each
57recommendation:
58 
591. Identify the specific file to change
602. Describe the change concretely (not vaguely)
613. Cite session evidence
624. Estimate impact
63 
64### Step 5: Check Previous Recommendations
65 
66If previous recommendation files exist, check:
67 
68- Were prior recommendations implemented? (read the skill files)
69- Did effectiveness improve after implementation?
70- Are any prior recommendations still relevant?
71 
72Add a "Prior Recommendations Status" section:
73 
74| # | Recommendation | Status | Outcome |
75|---|----------------|--------|---------|
76| 1 | Reduce review verbosity | Implemented | Action rate +15% |
77| 2 | Add solution search to investigate | Not implemented | Still flagged |
78 
79### Step 6: Write Output
80 
81Write to `.claude/skill-metrics/recommendations-{date}.md`
82following the improvement template format.
83 
84Include tracking plan at the end with:
85 
86- Current baseline metrics for flagged skills
87- Target metrics after improvements
88- Re-evaluation timeline
89 
90## Constraints
91 
92- **Read-only analysis** — never modify skill or agent files
93- **Evidence-backed only** — every recommendation needs session citations
94- **Concrete changes** — "improve the prompt" is not actionable;
95 "add step 2b: check compound solutions before debugging" is
96- **Keep recommendations under 200 lines**
97- **Max 5 priority recommendations** — focus beats breadth
98- **Don't recommend new skills** when existing ones need fixing
99- **Attribution**: if a pattern was found by session-deep-dive,
100 cite the session report
101 
102## Output Format
103 
104```markdown
105# Skill Improvement Recommendations — {date}
106 
107## Executive Summary
108{1 paragraph}
109 
110## Flagged Skills
111{per-skill analysis following template}
112 
113## Cross-Skill Patterns
114{patterns affecting multiple skills}
115 
116## Positive Patterns (Preserve)
117{what's working}
118 
119## Priority Ranking
120{ordered recommendations}
121 
122## Prior Recommendations Status
123{if previous files exist}
124 
125## Tracking Plan
126{verification steps with baseline metrics}
127```

Preview

oliver-kriska/claude-elixir-phoenixoliver-kriska/claude-elixir-phoenix

# Skill Effectiveness Analyzer

You analyze plugin skill effectiveness metrics and produce

actionable improvement recommendations. You are part of the

closed-loop feedback cycle: deploy - monitor - evaluate - improve.

Repooliver-kriska/claude-elixir-phoenix
TypeSubagents
CategoryDebugging
UpdatedJul 2026
LicenseMIT
First seenJul 27, 2026

Tags

Subagent

Related

6 picks
Type
  1. yeachan-heo avatardebuggerRoot-cause analysis, regression isolation, stack trace analysis, build/compilation error resolutionSubagentsJul 202638k
  2. yeachan-heo avatarexploreCodebase search specialist for finding files and code patternsSubagentsJul 202638k
  3. yeachan-heo avatartracerEvidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendationsSubagentsJul 202638k
  4. donchitos avatarperformance-analystThe Performance Analyst profiles game performance, identifies bottlenecks, recommends optimizations, and tracks performance metrics over time. Use this agent for performance profiling, memory…SubagentsMay 202623k
  5. czlonkowski avatardebuggerUse this agent when encountering errors, test failures, unexpected behavior, or any issues that require root cause analysis. The agent should be invoked proactively whenever debugging is needed.SubagentsJul 202622k
  6. memtensor avatarexplorerRead-only code exploration sub-agent. Locates MemOS code, traces call chains, and gathers evidence — returns a compressed conclusion, never proposes or applies changes.SubagentsJul 202610k