CtrlK
BlogDocsLog inGet started
Tessl Logo

cli-a2a

Interact with the OmniRoute A2A server from the CLI. Send tasks, inspect skill execution history, and test the JSON-RPC 2.0 agent-to-agent protocol interactively.

60

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cli-a2a/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 a clean, well-structured CLI reference with executable commands and flags, and it appropriately assumes Claude's competence. It loses points for lacking demonstrated flag usage in examples, no workflow sequencing, and no validation guidance around the destructive cancel operation.

Suggestions

Show real flag usage in the examples for complex subcommands, e.g. 'omniroute a2a invoke my-skill --input '{"k":"v"}' --wait' instead of restating the bare command.

Add a brief validation/checkpoint note for the destructive 'a2a cancel' command (e.g. confirm task state with 'a2a get <id>' before cancelling).

Remove the redundant Overview line that duplicates the frontmatter description, or replace it with a short orientation to the command groups.

DimensionReasoningScore

Conciseness

A lean command reference that assumes Claude's competence (no explaining what A2A or JSON-RPC is); minor redundancy from the Overview duplicating the frontmatter description and example blocks restating the heading command, so not a 5.

4 / 5

Actionability

Provides concrete executable commands and lists flags per subcommand, but the example blocks merely restate the heading command (e.g. 'omniroute a2a invoke <skill>') without demonstrating flag usage like --input, leaving minor gaps; not a 5.

4 / 5

Workflow Clarity

The body is a command catalog with no multi-step sequencing, and the destructive 'a2a cancel <id>' operation has only a --yes flag with no validation/checkpoint guidance, capping workflow clarity at 3 per the destructive-operations rule.

3 / 5

Progressive Disclosure

Well-organized section hierarchy (Overview, Quick install, Subcommands with per-command subsections) with easy navigation and no bundle files needed; not a 5 because the body exceeds the simple-skill line count and the repeated example blocks could be tightened.

4 / 5

Total

15

/

20

Passed

Description

70%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 is specific and distinct, naming a clear niche and several concrete actions with good natural trigger terms. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when you need to drive the OmniRoute A2A server from the CLI, send or inspect A2A tasks, or test the agent-to-agent protocol.'

Consider listing a couple more concrete actions (e.g. 'watch task streams', 'fetch task logs') to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain (OmniRoute A2A server, CLI) and three concrete actions ('Send tasks, inspect skill execution history, and test the JSON-RPC 2.0 agent-to-agent protocol'), matching the 'several specific actions; minor gaps' anchor; not a 5 because the CLI exposes more subcommands than the three summarized.

4 / 5

Completeness

Has a clear 'what' (send tasks, inspect history, test the protocol) but no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric cap completeness stays at 3.

3 / 5

Trigger Term Quality

Includes natural domain terms a user would say ('A2A', 'OmniRoute', 'agent-to-agent', 'JSON-RPC 2.0', 'tasks', 'CLI') with the synonym pair A2A/agent-to-agent; not a 5 because common variations or file/flag-style triggers are not exhaustively covered.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche ('OmniRoute A2A server', 'JSON-RPC 2.0 agent-to-agent protocol') with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
diegosouzapw/OmniRoute
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.