CtrlK
BlogDocsLog inGet started
Tessl Logo

external-control-api

规划或实现面向外部 agent / Claw 的稳定控制 API,优先做底层分层、query/command 收口、runtime 串行化与契约文档,而不是零散补接口

62

Quality

72%

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 ./.cursor/skills/external-control-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-sequenced, with specific paths, commands, endpoints, and validation steps that leave little ambiguity. Its weakest point is progressive disclosure — a long single-file skill with mild internal redundancy and no split-out reference materials.

Suggestions

Extract the 'Claw 最小模板' polling sequence and the file-path inventory into a separate reference file referenced one level deep, keeping SKILL.md as an overview.

Consolidate the overlapping底盘/runtime/service ordering currently repeated across '目标', '推荐工作流 §3', and '代码改动建议' into a single canonical sequence.

Add an explicit validate→fix→retry feedback loop for the mutation/runtime test steps to make the verification path more concrete.

DimensionReasoningScore

Conciseness

The body is dense and avoids explaining concepts Claude already knows, but the '目标', '推荐工作流 §3', and '代码改动建议' sections repeat the底盘/runtime/service ordering, so it could be tightened.

2 / 3

Actionability

It gives concrete file paths (e.g. 'src/server/public_query_builders.py'), named commands ('set_long_term_objective', 'create_avatar'), exact endpoints, and runnable test commands — copy-paste ready guidance.

3 / 3

Workflow Clarity

Workflows are clearly sequenced (priority ordering 1–7, pre-flight '首先检查什么' checklist) and the Claw template includes a query→check→branch→re-query verification loop with test commands as validation.

3 / 3

Progressive Disclosure

Sections are well-organized, but at ~180 lines everything is inline with no bundle reference files; content like the Claw template or the file-path inventory could be split into separate reference files for clearer navigation.

2 / 3

Total

10

/

12

Passed

Description

67%

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 distinctive about planning an external control API for agents/Claw, with concrete priority actions. Its main weakness is the absence of an explicit 'when to use' trigger, which caps completeness and leaves trigger phrasing technical rather than natural.

Suggestions

Append an explicit trigger clause, e.g. 'Use when designing or refactoring an external control API for Claw/agents, or consolidating ad-hoc endpoints into a stable contract'.

Add natural-language keywords users would actually say (e.g. 'control API', 'agent API', 'query/command split') alongside the technical terms.

Keep the current concrete action list but lead with the what/when pair so both dimensions are unambiguous.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '底层分层、query/command 收口、runtime 串行化与契约文档' — rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It states clearly what the skill does but gives no explicit 'Use when...' trigger for when to invoke it; per the guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Relevant terms ('控制 API', 'Claw', 'agent') are present but phrasing is technical and lacks common natural variations a user would say, fitting the 'some relevant keywords but missing variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The niche — '面向外部 agent / Claw 的稳定控制 API' — is specific and distinct, unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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
4thfever/cultivation-world-simulator
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.