CtrlK
BlogDocsLog inGet started
Tessl Logo

cli-command

Design, implement, or review Composio CLI commands under ts/packages/cli using Effect, @effect/cli, services, output conventions, configuration and environment variables, and local vendor references. Use for CLI command UX, command wiring, service changes, or CLI source edits. Do not use for CLI E2E-only work; use cli-e2e there.

72

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An efficient, well-structured overview that routes Claude to the right one-level-deep reference with clear scope annotations. It is concise and well-disclosed; the only weak spot is that all executable detail lives in the reference files rather than inline.

DimensionReasoningScore

Conciseness

Seven lean lines with no over-explanation of concepts Claude already knows; every line earns its place and assumes Claude's competence. It is not 4 because there are no instances of over-explanation to trim.

5 / 5

Actionability

Gives concrete, specific routing guidance mapping each real reference file to its exact scope (e.g. 'references/implementation.md for Effect command wiring and service patterns'). It is not 5 because the body delegates all executable detail to the reference files rather than including any inline concrete steps, and not 3 because the file-to-scope mapping is precise and actionable.

4 / 5

Workflow Clarity

The single action (read the matching reference, then act) is unambiguous and each bullet specifies when it applies. It is not 5 because the body does not spell out an explicit decision procedure or sequencing beyond 'Read the relevant reference', and not 3 because the routing logic is clear and this is not a destructive/batch operation requiring validation checkpoints.

4 / 5

Progressive Disclosure

A clear overview pointing to three well-signaled, one-level-deep references (design.md, implementation.md, client-cache-sync.md — all verified to exist), each annotated with its scope and content appropriately split out of SKILL.md. It is not 4 because navigation is clean with no organization gaps or buried references.

5 / 5

Total

18

/

20

Passed

Description

92%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 tight, well-scoped description that clearly states what the skill does, when to use it, and when not to use it. Strong trigger terms and explicit sibling-skill disambiguation make it highly distinctive.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Design, implement, or review', 'command wiring, service changes, or CLI source edits') and names the tech stack (Effect, @effect/cli) and location (ts/packages/cli), giving comprehensive coverage of the CLI command domain. It is not the 4-anchor because coverage is comprehensive rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both 'what' (design/implement/review Composio CLI commands) and 'when' ('Use for CLI command UX, command wiring, service changes, or CLI source edits') with concrete trigger phrases, plus a negative boundary ('Do not use for CLI E2E-only work; use cli-e2e there').

5 / 5

Trigger Term Quality

Includes natural trigger phrases a developer would say ('CLI command UX', 'command wiring', 'service changes', 'CLI source edits', 'CLI E2E') with good coverage. It is not 5 because it leans on specialized jargon (Effect, @effect/cli) and lacks the synonym/file-extension breadth of the 5-anchor examples.

4 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (Composio CLI under ts/packages/cli) with an explicit disambiguation against the sibling cli-e2e skill, giving minimal conflict risk. It is not 4 because the negative-trigger guidance makes the boundary explicit rather than merely 'mostly distinct'.

5 / 5

Total

19

/

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
ComposioHQ/composio
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.