CtrlK
BlogDocsLog inGet started
Tessl Logo

coding-cli

将编码工作委托给 Manager 持有的 AI CLI 工具(Claude Code / Gemini CLI / qodercli)执行

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./manager/agent/skills-alpha/worker-skills/coding-cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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 clearly sequenced with concrete commands, templates, a validation checkpoint, and feedback loops. Its main weakness is mild redundancy between the prompt-generation guidance and the later Tips section, which could be consolidated for token efficiency.

Suggestions

Merge 'Tips for Better Prompts' into the 'Generate a High-Quality Prompt' section to remove the partial overlap (surgical/specific changes, limit scope/constraints, verify command/acceptance criteria) and tighten the body.

Make the post-delegation verification step more explicit as a validate-then-proceed checkpoint (e.g., 'Only report completed: after tests pass / git diff is reviewed') to strengthen the feedback loop.

Consider extracting the long worked prompt example into a short reference snippet or trimming it, since it is the single largest token block.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining concepts Claude already knows, but the 'Tips for Better Prompts' section partially restates the 'Generate a High-Quality Prompt' section (surgical≈specific changes, limit scope≈constraints, verify command≈acceptance criteria) and could be tightened.

2 / 3

Actionability

It provides fully executable bash commands (mkdir, git clone, mc mirror), copy-paste message templates, and a concrete worked prompt example with exact file paths and line numbers, leaving no ambiguity about what to do.

3 / 3

Workflow Clarity

Steps are clearly sequenced (1 through 6) with an explicit checkpoint (the .processing marker check in 2b) and feedback loops (6b failure fallback to manual implementation, and the Multiple Rounds retry after re-syncing).

3 / 3

Progressive Disclosure

No bundle files exist and the skill needs no external references; the single SKILL.md is well-organized into clearly headed sections (When to Use, Step-by-Step Workflow, Multiple Rounds, Tips), which suffices for progressive disclosure per the rubric's no-external-references guidance.

3 / 3

Total

11

/

12

Passed

Description

57%Weight 40%Scale 1-3

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 states a concrete, distinct purpose but is missing an explicit 'when to use' trigger clause and leans on internal jargon rather than natural user-facing keywords. Adding a 'Use when...' clause with common trigger phrasing would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' / 'assign_when'-style trigger clause directly in the description field (e.g., 'Use when the Worker must perform code changes and spec.md contains a Coding CLI Mode section').

Replace internal jargon ('Manager 持有的 AI CLI 工具') with more natural trigger terms a user would say, such as '写代码', '修改代码', '重构', '修 bug', 'delegate coding tasks'.

Expand the stated actions beyond the single 'delegate' verb to a fuller set (e.g., prepare workspace, generate coding prompt, review CLI-produced changes) to improve specificity.

DimensionReasoningScore

Specificity

It names the domain (coding work) and a concrete action ('委托...执行' / delegate to a CLI tool) plus the specific tools (Claude Code / Gemini CLI / qodercli), but describes only the single action of delegation rather than a comprehensive set of actions.

2 / 3

Completeness

It clearly states what the skill does (delegate coding to the CLI tool) but provides no 'Use when...' clause or explicit trigger guidance in the description field, capping completeness at 2 per the guideline.

2 / 3

Trigger Term Quality

It includes some relevant terms ('编码', 'CLI', 'Claude Code'), but the phrasing relies on internal/system jargon ('Manager 持有的 AI CLI 工具') that a user would not naturally say, and it omits common variations.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and operationally specific (delegating coding work to the Manager's AI CLI tool within the agent-team workflow), making it unlikely to trigger for or conflict with other skills.

3 / 3

Total

9

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
agentscope-ai/AgentTeams
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.