CtrlK
BlogDocsLog inGet started
Tessl Logo

clarvia-aeo-check

Score any MCP server, API, or CLI for agent-readiness using Clarvia AEO (Agent Experience Optimization). Search 15,400+ indexed tools before adding them to your workflow.

53

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/clarvia-aeo-check/SKILL.md

The canonical home for this skill is clarvia-aeo-check in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body is well-structured and actionable with concrete config/snippet examples and clear sequenced steps plus error-recovery guidance. The main inefficiency is redundancy between the How-It-Works and Examples sections.

DimensionReasoningScore

Conciseness

The body is mostly lean and scannable, but the Examples section substantially duplicates the How-It-Works steps (Example 1 ≈ Step 1, Example 2 ≈ Step 2), which could be tightened.

3 / 5

Actionability

Provides copy-paste-ready MCP config JSON, a GitHub Action YAML block, and specific prompts naming the exact tool ('Use the clarvia aeo_score tool'); minor gaps in naming tool calls for every step.

4 / 5

Workflow Clarity

Steps 1–4 are clearly sequenced and the Common Pitfalls section supplies error-recovery feedback ('not found' → scan by URL; low score → get_score_breakdown); this is not a destructive/batch operation so no cap applies.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized with clear section headers and no nested references. It exceeds 50 lines and contains sections (score table, examples) that could be split, keeping it just short of a 5.

4 / 5

Total

15

/

20

Passed

Description

53%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.

The description clearly states what the skill does and targets a fairly distinct niche, but it lacks an explicit 'Use when...' trigger clause and leans on coined jargon ('AEO') over natural user phrasing. Specificity is adequate but not comprehensive.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when evaluating an MCP server, API, or CLI before adding it to an agent workflow, or when comparing candidate tools for a job.'

Replace or supplement the coined 'AEO (Agent Experience Optimization)' jargon with natural terms users would actually say (e.g., 'agent-readiness scoring', 'tool quality', 'best MCP server').

Enumerate the concrete capabilities more fully — mention the four AEO dimensions (API accessibility, data structuring, agent compatibility, trust signals) or the score/compare/leaderboard actions to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ('MCP server, API, or CLI') and two concrete actions ('Score... for agent-readiness', 'Search 15,400+ indexed tools'), but coverage is not comprehensive — the four AEO dimensions are not enumerated in the description.

3 / 5

Completeness

The 'what' is clear ('Score... for agent-readiness', 'Search... indexed tools'), but the 'when' is only weakly implied via 'before adding them to your workflow' with no explicit 'Use when...' clause, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

'MCP server', 'API', 'CLI', and 'agent workflow' are natural terms users say, but the coined jargon 'Clarvia AEO (Agent Experience Optimization)' and the absence of common synonyms/variants keep this from full coverage.

3 / 5

Distinctiveness Conflict Risk

The branded 'Clarvia AEO' agent-readiness-scoring niche is mostly distinct, but the broad triggers ('MCP server, API, CLI') create minor overlap with the related '@agent-evaluation' skill referenced in the body.

4 / 5

Total

13

/

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.

Validation15 / 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.