CtrlK
BlogDocsLog inGet started
Tessl Logo

claude-automation-recommender

Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable recommender skill with a clear three-phase workflow and excellent progressive disclosure via real reference files. The main weakness is conciseness: redundant overview and decision-framework sections restate knowledge Claude already has.

Suggestions

Remove or merge the "Automation Types Overview" table into the Phase 2 sections, since Claude already knows what hooks, subagents, skills, plugins, and MCP servers are.

Collapse the "Decision Framework: When to Recommend X" subsections into the Phase 2 recommendation tables to eliminate redundancy between the overview, Phase 2, and decision sections.

Add install/creation commands for the MCP servers and skills named only by name in the Phase 2 tables so every recommendation is fully copy-paste actionable.

DimensionReasoningScore

Conciseness

The body is dense with useful signal-to-recommendation tables, but the "Automation Types Overview" and the "Decision Framework: When to Recommend X" sections restate concepts Claude already knows (what hooks/subagents/MCP servers are and when to use them), and there is redundancy across the overview, Phase 2, and Decision Framework sections that could be tightened.

3 / 5

Actionability

Phase 1 provides executable bash detection commands, recommendations map signals to specific named tools with install commands like `claude mcp add context7`, and the output template gives concrete file paths and YAML frontmatter; minor gaps remain where some MCP/skill entries name a tool without its exact install or creation command.

4 / 5

Workflow Clarity

Three phases (Codebase Analysis, Generate Recommendations, Output Report) are clearly sequenced with a concrete output template, and the skill is explicitly read-only so no destructive-validation cap applies; checkpoints for analysis completeness are implicit rather than explicit, keeping it just below a 5.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled one-level-deep references (e.g. "See [references/mcp-servers.md](references/mcp-servers.md) for detailed patterns"), and all five referenced files exist in the references/ bundle, giving easy navigation with no nesting.

5 / 5

Total

16

/

20

Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly covers both what it does and when to use it with comprehensive, natural trigger phrases and third-person voice. The only weakness is mild overlap risk from broad setup/workflow phrasing and a slightly limited action verb set.

DimensionReasoningScore

Specificity

"Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers)" names the domain and enumerates five concrete automation categories, giving several specific actions with only minor gaps; it stops short of the 5 anchor because the verbs are limited to analyze/recommend rather than a fuller action set.

4 / 5

Completeness

It clearly states what the skill does (analyze codebase and recommend automations across five types) and explicitly answers when with concrete "Use when..." trigger phrases, matching the anchor for both what and when.

5 / 5

Trigger Term Quality

"asks for automation recommendations", "optimize their Claude Code setup", "improving Claude Code workflows", "set up Claude Code for a project", "what Claude Code features they should use" comprehensively covers natural phrases and synonyms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

The Claude Code automation-recommender niche is mostly distinct with specific triggers, but phrases like "optimize their Claude Code setup" and "improving Claude Code workflows" carry minor overlap risk with general Claude Code configuration skills.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
anthropics/claude-plugins-official
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.