CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

92%

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

92%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 exemplary dispatcher-style SKILL.md body: concise, well-structured, and cleanly delegating detail to five purpose-labeled reference files that all exist. The only improvement would be removing the one sentence that duplicates the frontmatter description. All four dimensions land at or near the top anchors.

DimensionReasoningScore

Conciseness

The body is a lean routing table where every reference line earns its place, but "Use this skill for CLI command design and implementation." restates the frontmatter description and could be trimmed. This is a minor instance of over-explanation, matching anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Each line is a fully executable directive mapping a concrete condition to a named file (e.g., "references/client-cache-sync.md when touching toolkit client services"). Per the instruction-skill note, absence of code is not penalized because the guidance is specific and directly actionable, covering the common cases.

5 / 5

Workflow Clarity

The body's single action — select and read the matching reference — is unambiguous because every reference is annotated with when to use it. As a simple dispatcher skill with no destructive or batch operations in the body, it meets the simple-skill exception for a top workflow-clarity score.

5 / 5

Progressive Disclosure

The body is a clear overview that splits content across five one-level-deep references (references/design.md, references/implementation.md, references/client-cache-sync.md, references/command-example.md, references/data-and-lifecycle.md), all of which exist in the bundle and are clearly signaled with their scope. Navigation is easy with no nesting or buried references.

5 / 5

Total

19

/

20

Passed

Description

87%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 pairs a concrete capability statement with explicit positive and negative triggers. Third-person voice is used throughout, and the scope is tightly bounded to a specific repo path and sibling-skill boundary. The only gap is that the capability list leans on technology names rather than a fuller set of concrete actions.

DimensionReasoningScore

Specificity

"Design, implement, or review Composio CLI commands under ts/packages/cli" names concrete verbs and a precise tech surface ("Effect, effect/cli, services, output conventions, configuration and environment variables"), but the middle list enumerates technologies rather than actions, leaving minor gaps in action coverage. Not 5 because it does not comprehensively enumerate concrete actions; not 3 because several specific actions and capabilities are explicitly stated.

4 / 5

Completeness

The description explicitly answers what ("Design, implement, or review Composio CLI commands ... using Effect, effect/cli, services, output conventions ...") and when ("Use for CLI command UX, command wiring, service changes, or CLI source edits"), with concrete trigger phrases. It even adds an explicit negative trigger ("Do not use for CLI E2E-only work; use cli-e2e there"), matching the top anchor.

5 / 5

Trigger Term Quality

"Use for CLI command UX, command wiring, service changes, or CLI source edits" supplies natural developer phrases that map directly to how users would phrase requests. A few natural variations (e.g., "add a command", "flag", "argument") are missing, keeping it below the comprehensive-synonym anchor of 5.

4 / 5

Distinctiveness Conflict Risk

The product ("Composio CLI"), the repo path ("ts/packages/cli"), and the explicit handoff to a sibling skill ("Do not use for CLI E2E-only work; use cli-e2e there") carve out a clear niche with minimal conflict risk. This is stronger than the 4 anchor because overlap with related skills is actively disambiguated.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ComposioHQ/composio

Path

.agents/skills/cli-command/SKILL.md

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.