CtrlK
BlogDocsLog inGet started
Tessl Logo

four-color-cards

基于解析后的文档与用户意图,生成四色卡片——事实蓝卡、解释绿卡、风险黄卡、行动红卡,是八官署方法论的核心分析输出。

59

Quality

68%

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 ./antinet-agentteams/skills/four-color-cards/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a well-structured, highly actionable skill body with concrete runnable commands, clear stage mapping, explicit failure-handling feedback loops, and a clean one-level reference to a real bundle script. Its only mild weakness is a few trimmable explanatory phrases.

DimensionReasoningScore

Conciseness

The body is efficiently organized into focused sections and largely assumes Claude's competence; only minor phrases (e.g. the 复用价值 framing) could be trimmed without losing clarity.

4 / 5

Actionability

It gives copy-paste-ready executable commands for all three stages (`python skills/four-color-cards/scripts/run_four_color_cards.py --stage {extract|review|propose}`), a real entry point, and concrete output paths — fully executable and covering the common cases.

5 / 5

Workflow Clarity

The extract→review→propose sequence is clear and the 失败处理 section provides explicit fallbacks (LLM 不可用→规则引擎, 超时→pending_review, 来源缺失→标注) plus the 溯源铁律 enforcement; only minor explicit validation checkpoints are missing.

4 / 5

Progressive Disclosure

The SKILL.md is a well-organized overview with a single clearly-signaled one-level-deep reference to the real script `scripts/run_four_color_cards.py`; navigation is easy and content is appropriately split.

5 / 5

Total

18

/

20

Passed

Description

51%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 concretely names what the skill produces but relies on internal-methodology jargon rather than natural user trigger terms, and it omits an explicit 'Use when' clause in the description field itself. Trigger-term quality and completeness are the main weaknesses.

Suggestions

Add an explicit 'Use when...' clause to the description field naming natural user phrases (e.g. structured document analysis, fact/risk/action card generation) rather than leaving the trigger only in assign_when.

Soften the 八官署/四色卡片 jargon with everyday synonyms so users who don't know the internal methodology can still match the skill.

Briefly state the concrete actions per card type (extract facts, explain mechanisms, flag over-claims, propose actions) to lift specificity toward 5.

DimensionReasoningScore

Specificity

Lists several concrete actions — generating four distinct card types (事实蓝卡/解释绿卡/风险黄卡/行动红卡) from parsed documents and user intent — with only minor gaps in describing what each generation step entails.

4 / 5

Completeness

It clearly states what the skill does (generate four-color cards) but the description field itself lacks any 'Use when...' trigger; the when-guidance lives only in the separate assign_when field, which caps completeness at 3.

3 / 5

Trigger Term Quality

The keywords (四色卡片, 事实/解释/风险/行动, 八官署方法论) are domain-specific jargon tied to an internal methodology rather than natural phrases a user would spontaneously say when needing this skill.

2 / 5

Distinctiveness Conflict Risk

The four-color-card / 八官署 niche is fairly specific and distinguishable from generic document skills, with only minor overlap risk against other analysis-oriented skills.

4 / 5

Total

13

/

20

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
anbeime/skill
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.