Name: clarvia-aeo-check
Rating: 58.4 (1 reviews)
Author: administrakt0r

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.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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

Quality

Content

75%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 content is well-structured, actionable, and respectably concise for an MCP-tool-driving instruction skill. It lands at 4 across all dimensions, held back from 5s by minor redundancy, prompt-only tool-call examples, and the slightly misleading 'Steps 1-4' framing.

Suggestions

Dedupe the '15,400+' figure and trim the Examples section so it does not restate the How-It-Works steps.

Show the actual MCP tool-call invocation (e.g. a sample `aeo_score` call with arguments) instead of only natural-language prompts to push actionability toward fully executable.

Relabel 'Step 1-4' as distinct use-cases or capabilities (Score / Search / Compare / Leaderboard) to avoid implying a required sequence.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's knowledge of MCP/API/CLI concepts and stays mostly lean; minor redundancy ('15,400+' repeated three times, the Examples section restating the How-It-Works steps) keeps it just short of the fully lean anchor 5.	4 / 5
Actionability	Copy-paste-ready MCP config JSON and CI Action YAML plus concrete example prompts and named tools ('aeo_score', 'get_score_breakdown') provide mostly executable guidance; the actual tool-call structure is shown only as natural-language prompts, a minor gap versus the copy-paste-everything anchor 5.	4 / 5
Workflow Clarity	Each use-case is clearly explained and the single action (use Clarvia to score/search/compare) is unambiguous; the four 'Steps' are really independent alternatives rather than a sequence, a minor clarity gap, and no validation checkpoints are needed for this non-destructive skill.	4 / 5
Progressive Disclosure	No bundle files exist, so scoring is against the inline structure: ~120 lines organized into clear, well-labeled sections that are appropriately self-contained for a skill this size, with only minor organization gaps versus the ideal split-and-reference anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

61%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 states a clear purpose and distinct niche but lacks an explicit 'Use when...' trigger clause, capping its completeness. It is solid and specific, just short of the best examples on coverage and trigger guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when evaluating, comparing, or selecting MCP servers, APIs, or CLIs for agent workflows.'

List one or two more concrete actions (e.g. 'compare tools head-to-head', 'browse category leaderboards') to lift specificity from 1-2 actions toward 'several'.

Include natural trigger synonyms users might say ('agent-ready', 'tool quality', 'which MCP server should I use') to round out trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (MCP servers, APIs, CLIs) and two concrete actions ('Score any MCP server, API, or CLI for agent-readiness', 'Search 15,400+ indexed tools'), matching the anchor for 1-2 concrete actions rather than the 'several' required for a 4.	3 / 5
Completeness	A clear 'what' is present ('Score any MCP server, API, or CLI for agent-readiness using Clarvia AEO') but the 'when' is only the weak conditional 'before adding them to your workflow' with no explicit 'Use when...' trigger, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms a user would say ('MCP server', 'API', 'CLI', 'agent-readiness', 'tools') give good coverage; a few synonyms or phrasings are missing, fitting the anchor 4.	4 / 5
Distinctiveness Conflict Risk	The AEO/agent-readiness framing and the named Clarvia tool carve a clear niche, but 'MCP server, API, or CLI' is broad with minor overlap against general tool-evaluation skills, fitting anchor 4 rather than the minimal-conflict anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/clarvia-aeo-check/SKILL.md
Commit: 57c135b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.