cli-e2e

Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

A minimal, well-disciplined body that follows the pointer pattern correctly and scores perfectly on progressive disclosure. The deductions come from small trimmable redundancy, fully delegated rather than inline actionable detail, and a verification step lacking an explicit feedback loop.

Suggestions

Drop or repurpose the sentence "Use this skill for CLI end-to-end tests." — it duplicates the frontmatter description and earns no new information.

Add a one-line inline example of the smallest useful action (e.g. the pnpm test:e2e:cli verification command) so the body is actionable even before the reference is opened.

In the verification guidance, add a short fix-and-retry loop (e.g. "If a suite fails, fix the suite or fixture and re-run with a focused Turbo filter") to make the checkpoint a true feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is three lines with zero padding, but "Use this skill for CLI end-to-end tests." merely restates the frontmatter description and could be trimmed. This is a minor instance of trimmable content rather than the every-token-earns-its-place ideal of the top anchor.	4 / 5
Actionability	"Read `references/docker-cli-e2e.md` before adding or changing suites under `ts/e2e-tests/cli/`" is concrete and executable, and the referenced bundle file (which exists) carries the templates and verification commands. Not 5 because the body itself offers no inline example covering a common case, so guidance is complete only via delegation.	4 / 5
Workflow Clarity	The body gives one unambiguous directive with a clear precondition, and the reference lays out architecture, a package template, and a verification command. Not 5 because the verification step ("pnpm test:e2e:cli") has no fix-and-retry feedback loop; not 3 because the sequence that exists is clear and the single directive is unambiguous.	4 / 5
Progressive Disclosure	The body is a lean overview pointing to a single one-level-deep reference (references/docker-cli-e2e.md, which exists at the stated path) that is clearly signaled and self-contained with no nested references. This matches the top anchor: content is appropriately split and navigation is trivial.	5 / 5
	Total	17 / 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 strong description: concrete multi-action capability list, explicit what and when clauses, and explicit boundary guidance against a sibling skill. The only minor weakness is that a few natural trigger-term variations are absent.

Dimension	Reasoning	Score
Specificity	"Write, modify, or debug... including binary invocation, fixture isolation, output assertions, and package manifests" lists multiple specific concrete actions that comprehensively cover the skill's scope, matching the top anchor without vague filler. Not 4 because coverage of the domain (authoring, editing, debugging, and the four named sub-areas) leaves no noticeable gap.	5 / 5
Completeness	It explicitly answers what ("Write, modify, or debug Docker-based Composio CLI end-to-end tests...") and when ("Use for CLI E2E test suites only") with concrete trigger phrases, matching the top anchor exactly. Not 4 because the when-clause is fully explicit, not merely present.	5 / 5
Trigger Term Quality	"Composio CLI", "end-to-end tests", "CLI E2E test suites", and the ts/e2e-tests/cli path are natural phrases a user would say, but a few common variations (e.g. "CLI tests", "composio tests") are missing. Not 3 because the existing keyword set is already relevant and well-matched rather than merely partial; not 5 because synonym/variation coverage is not comprehensive.	4 / 5
Distinctiveness Conflict Risk	"Use for CLI E2E test suites only; use cli-command for CLI source implementation" carves out a clear niche and explicitly disambiguates against the closest sibling skill, minimizing conflict risk. Not 4 because the boundary is stated outright rather than merely implied by specificity.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ComposioHQ/composio
Path: .agents/skills/cli-e2e/SKILL.md
Commit: 98b10d7

Reviewed: 3 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.