CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

acpx

Use acpx as a headless ACP CLI for agent-to-agent communication, including installed-agent inspection, prompt/exec/sessions workflows, session scoping, queueing, permissions, output formats, system-prompt overrides, and multi-agent flows authored with defineFlow/decision/decisionEdge.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/acpx/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 exceptionally actionable, with executable commands and examples for every feature, and destructive operations are properly guarded with dry-run previews. Its main weaknesses are token efficiency — a large amount of per-agent and embedded-runtime implementation detail is inlined — and the absence of any progressive-disclosure bundle structure to move that detail into reference files.

Suggestions

Move the per-agent registry details (~90 lines of agent-specific quirks and external guide links) and the embedded-hosts API semantics into reference files, keeping only the default-agent rule and a few common agents in SKILL.md.

Trim or remove the 30+-bullet "Core capabilities" list at the top, since nearly every bullet duplicates a dedicated section later in the file.

Convert release-note-style behavioral prose (e.g., the -32603 session-recovery rules and adapter-range migration notes) into a short "Behavior notes" or "Migration/deprecated" reference file, keeping only operator-relevant rules inline.

DimensionReasoningScore

Conciseness

The ~720-line body inlines deep implementation internals (e.g., "may be replaced after an ACP internal load/resume error (`-32603`)"), release-note-style migration rules, and a 30+-bullet capabilities list that duplicates later sections, making it noticeably verbose for a SKILL.md even though the content is accurate and free of known-concept padding.

2 / 5

Actionability

Commands are fully executable and copy-paste ready throughout: install ("npm i -g acpx"), per-subcommand examples, a jq NDJSON automation pipeline, prune recipes, and a complete runnable defineFlow TypeScript example covering the common cases.

5 / 5

Workflow Clarity

Key multi-step workflows are clearly sequenced with validation checkpoints where it matters — destructive prune is demonstrated with "--dry-run" preview first, and the system-prompt override flow gives an explicit create-then-select sequence — though most other sections describe behavior rather than prescriptive validated sequences.

4 / 5

Progressive Disclosure

Section headers are well-organized and external references are clearly signaled (e.g., "see the [OpenClaw guide](...)", "See `docs/flows.md`"), but no bundle files exist and content that clearly belongs in separate files — per-agent registry quirks for ~25 agents and embedded-host API semantics — is inlined in a single monolithic file.

3 / 5

Total

14

/

20

Passed

Description

58%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 gives a strong, specific account of what the tool does, but it entirely lacks "when to use" trigger guidance and over-indexes on internal API names at the expense of natural user phrases. Adding an explicit "Use when..." clause with natural trigger terms (agent names, automation, orchestration) would lift both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when you need to run coding agents (codex, claude, gemini) headlessly from scripts, orchestrate multi-agent workflows, or manage persistent ACP sessions."

Replace or supplement internal API names like "defineFlow/decision/decisionEdge" with user-facing phrases such as "authoring multi-agent workflow graphs".

Include natural synonyms users would actually say — "agent automation", "CLI agent orchestration", "ACP" — to improve trigger coverage.

DimensionReasoningScore

Specificity

The description enumerates several specific capability areas ("installed-agent inspection, prompt/exec/sessions workflows, session scoping, queueing, permissions, output formats, system-prompt overrides"), but several entries are single-word category labels rather than concrete verb phrases, leaving minor gaps versus the comprehensive anchor-5 example.

4 / 5

Completeness

The "what" is clearly and concretely stated, but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"agent-to-agent communication", "headless ACP CLI", and "multi-agent flows" are relevant phrases, but the description leans on tool-internal API names ("defineFlow/decision/decisionEdge") and omits common natural variations users would say, such as agent names (codex, claude, gemini) or terms like automation/orchestration.

3 / 5

Distinctiveness Conflict Risk

"acpx" and "headless ACP CLI for agent-to-agent communication" define a clear niche that is unlikely to trigger for unrelated skills, with only minor overlap risk against other agent-running or orchestration skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (723 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

14

/

16

Passed

Repository

openclaw/acpx

Path

skills/acpx/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.