agentic-evaluator
Evaluates any repository's agentic development maturity. Use when auditing a codebase for best practices in agents, skills, instructions, MCP config, and prompts. Produces a scored report with specific remediation steps.
81
73%
Does it follow best practices?
Impact
93%
1.50xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/agentic-evaluator/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly communicates a specific, niche capability with explicit trigger guidance. It covers what the skill does (evaluates agentic maturity, produces scored reports with remediation), when to use it (auditing codebases for agentic best practices), and uses domain-specific terms that make it highly distinguishable from other skills. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'evaluates repository's agentic development maturity', 'auditing a codebase for best practices', 'produces a scored report with specific remediation steps'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Evaluates any repository's agentic development maturity', 'Produces a scored report with specific remediation steps') and when ('Use when auditing a codebase for best practices in agents, skills, instructions, MCP config, and prompts'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'repository', 'codebase', 'audit/auditing', 'agents', 'skills', 'instructions', 'MCP config', 'prompts', 'best practices', 'maturity'. Users asking about evaluating their agentic setup would naturally use several of these terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — 'agentic development maturity' evaluation is a very specific domain unlikely to overlap with general code review, linting, or other audit skills. The combination of agents, skills, MCP config, and prompts creates a clear, unique trigger profile. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
47%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive and well-structured evaluation framework with clear scoring rubrics and phased workflows, but it severely violates its own principles of conciseness and lean context. At 400+ lines, it far exceeds the 80-300 line guideline it recommends for skills, and embeds extensive reference material (research citations, best practices, remediation patterns) that should be in bundled files. The content is actionable at a process level but lacks executable tooling.
Suggestions
Reduce SKILL.md to 150-250 lines by moving the Lean Context Principle section, Size Guidelines Reference, Skill Quality Dimensions, Skill Development Best Practices, and Remediation Patterns into separate bundled reference files (e.g., lean-context.md, size-guidelines.md, remediation-patterns.md)
Remove or drastically trim the SkillsBench research citations and Anthropic guidance summaries—these are background justification, not actionable evaluation instructions
Cut the noise/signal tables in the Lean Context section; a brief 2-line summary with a reference to a bundled file would suffice
Add concrete executable examples: a sample script or command sequence for scanning artifacts, counting lines, or validating frontmatter rather than relying on natural language prompts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill is extremely verbose at ~400+ lines. It extensively explains concepts Claude already knows (what agentic patterns are, how folder structures work, what YAML frontmatter is). It includes lengthy sections on 'Lean Context Principle' with noise/signal tables, SkillsBench research citations, and best practices that are general knowledge rather than actionable evaluation steps. The irony is that a skill about lean context is itself full of noise. | 1 / 3 |
Actionability | The evaluation workflow provides concrete scoring tables with specific point values and criteria, which is actionable. However, there are no executable code examples—no scripts, no validation commands, no concrete file-parsing logic. The 'Running the Evaluator' section just shows natural language prompts rather than concrete implementation. The scoring criteria are specific enough to act on but lack executable tooling. | 2 / 3 |
Workflow Clarity | The 7-phase evaluation workflow (Discovery Scan → Foundation → Skills → Agents → Instructions → Consistency → Generate Report) is clearly sequenced with explicit scoring criteria at each phase. Each phase has a detailed rubric table with point allocations. The report template provides a clear output format with prioritized issues (P0/P1/P2) and remediation steps. | 3 / 3 |
Progressive Disclosure | The skill references supporting files (checklist.md, report-template.md) and mentions a related skill (project-scaffold), but no bundle files are provided. The SKILL.md itself is monolithic—embedding extensive reference material (size guidelines, quality dimensions, remediation patterns, best practices, lean context principle) that should be in bundled files. The skill violates its own advice about keeping SKILL.md to 1-2K tokens. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- 0xrabbidfly/eric-cartman
- Commit
17bd06f
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.