CtrlK
BlogDocsLog inGet started
Tessl Logo

antinet-four-color-cards

财务和投资分析师、律师助理与法律助手在撰写金融研报或分析法律文档时,必用此技能!基于解析文档一键生成事实蓝卡、解释绿卡、风险黄卡与行动红卡。自动完成深度剖析与风险排查,产出100%可溯源的结构化四色报告,让复杂分析高效且严谨。

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/antinet-four-color-cards/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 compact, well-structured, actionable skill body with concrete commands, a clear three-stage workflow, and validation checkpoints; its main weaknesses are a promotional 复用价值 section, slight redundancy, and a runtime dependency outside the bundle.

Suggestions

Remove or tighten the 复用价值 section, which is non-instructional padding that does not advance execution.

State the external core.runtime.AgentSession dependency explicitly (e.g. in 依赖) so the runnable path is self-documenting.

De-duplicate the worker→stage→card mapping so it appears once rather than across 使用方式 and 复赛代码包执行.

DimensionReasoningScore

Conciseness

The body is mostly lean and section-organized, but the 复用价值 section ('方法论通用', '天然契合 Agent Infra 的可观测/审计评审维度') is promotional padding and the worker→stage mapping is restated across sections.

4 / 5

Actionability

Concrete runnable commands are given (scripts/run_four_color_cards.py --stage {extract|review|propose}) with example invocations and output paths, but execution depends on an external core.runtime.AgentSession not bundled with the skill.

4 / 5

Workflow Clarity

The extract→review→propose sequence is clear with failure-handling and a traceability checkpoint (无来源不得入库, pending_review, 低置信度触发人工复核); only minor validation gaps remain.

4 / 5

Progressive Disclosure

Well-organized sections with a one-level-deep reference to the bundled scripts/run_four_color_cards.py (verified to exist); minor organization gaps from the duplicated worker mapping keep it just below 5.

4 / 5

Total

16

/

20

Passed

Description

67%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 conveys a clear, fairly specific purpose with both what and when, but leans on skill-internal card jargon and role-based framing rather than natural user trigger phrases, capping trigger quality at 3.

Suggestions

Rewrite the trigger clause in user-spoken terms (e.g. '分析财报/金融研报、梳理法律文档、做风险排查时使用') instead of leading with role assignments and 蓝卡/绿卡 jargon.

Add common synonyms and file-type cues (e.g. 财报、研报、招股书、合同、判决书) to broaden natural trigger coverage.

Trim promotional padding ('100%可溯源', '高效且严谨', '必用此技能!') that does not aid triggering.

DimensionReasoningScore

Specificity

Lists several concrete actions — 生成事实蓝卡/解释绿卡/风险黄卡/行动红卡, 深度剖析与风险排查, 产出可溯源结构化报告 — though 深度剖析 is mildly abstract, keeping it just below comprehensive (5).

4 / 5

Completeness

It states both what (生成四色卡片、深度剖析与风险排查、产出结构化报告) and when (撰写金融研报或分析法律文档时), so it clears the 'Use when' floor of 3, but the when is role-framed and could be more explicit.

4 / 5

Trigger Term Quality

Domain terms 金融研报 and 法律文档 are natural, but the card jargon (蓝卡/绿卡/四色卡片) is skill-internal rather than user-spoken, and common synonyms/variations are missing.

3 / 5

Distinctiveness Conflict Risk

The four-color card + auditable-traceability niche for financial/legal analysis is mostly distinct, with only minor overlap risk against general analysis skills.

4 / 5

Total

15

/

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.

Validation — 15 / 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.