CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

content-calibrator

DNA 表现评估引擎——消费 published-track 的发布与互动数据,按量触发 DNA 评估,产出报告与优化建议,经用户确认后回写。用户开启、调整或停用定时取数复盘时,提供参考并派 IT engineer 管理原生 Automation。发布与指标记录由 published-track 管理,平台取数由各专家包 engagement 工具负责。

Quality

79%

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 ./crews/main/skills/content-calibrator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 a strong, highly executable skill document: complete command surface with defaults and semantics, a clearly sequenced evaluation loop with validation gates and error-recovery rules, and a clean one-level-deep reference split. The main cost is token efficiency — key safety rules and scheduled-review details are repeated verbatim across sections, and some reference-file content leaks back into the main file.

Suggestions

State the '评估只产出建议、DNA 更新须用户逐条确认' and '先排混杂再归因' rules once (in the 铁律 block) and reference them elsewhere by name instead of repeating them in 职责边界, 归因原则, and 定时取数与复盘.

Trim the '最终回复正文即完整报告' delivery rules and the ≥5 条/≥3 天 threshold definitions from the body — both already live in references/scheduled-review.md — keeping only the pointer.

Move the numbered main-agent Automation enable/adjust/disable steps (items 1-5) into the reference or a short checklist, since they are procedural detail rather than overview content.

DimensionReasoningScore

Conciseness

Mostly dense and efficient with no explanation of known concepts, but core rules are repeated nearly verbatim multiple times — '评估只产出建议 / DNA 更新须用户确认' appears in the 四条评估铁律, the 职责边界 section, and the 定时取数与复盘 section, and '先排混杂再归因' likewise. The 定时取数 governance section also restates content from the reference file. Fits the 'mostly efficient but could be tightened' anchor; not a 2 since there is no padding or over-explanation.

3 / 5

Actionability

Every operation has a copy-paste-ready command with placeholder arguments and defaults — 'content-calibrator eval --platform <platform> --check', '--dna-id <dna-id> --force', '--mark-evaluated --ids 3,4,5' — plus precise baseline semantics ('此前最多 N 篇均值,此前 <3 篇 → baseline_insufficient'), an enumerated 5-part report structure, and a concrete 4-step attribution procedure. Specific examples cover the common cases with no meaningful gaps.

5 / 5

Workflow Clarity

The 核心闭环 gives a clear sequence (取数 → 阈值检查 --check → 聚合+归因 → 报告 → 用户逐条确认 → style-dna 更新) with explicit validation checkpoints: the --check threshold gate, baseline_insufficient downgrade to absolute-only observation, and the mandatory post-report '--mark-evaluated' to prevent duplicate evaluation. Error-recovery feedback is specified ('技术故障记录后继续其他平台', '认证失效不自动登录'), and the batch DNA-update operation is guarded by mandatory per-item user confirmation — so the batch-operation cap does not apply.

5 / 5

Progressive Disclosure

One clearly signaled, real, one-level-deep reference ('参考文件:[定时取数与 DNA 复盘](references/scheduled-review.md)') verified to exist and to not nest further references, with a deliberate split: SKILL.md holds enable/adjust/disable governance while the reference holds per-run execution detail. Not a 5 because some reference content (the '最终回复正文即完整报告' delivery rules and threshold definitions) is duplicated inline in the body rather than left solely in the reference.

4 / 5

Total

17

/

20

Passed

Description

71%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 is specific, third-person, and does an excellent job of staking out a distinct niche with explicit boundary delineation against adjacent skills. Its main weaknesses are trigger-term quality — it speaks in internal system jargon rather than natural user phrases — and a 'when' clause that covers the scheduled-review lifecycle but omits the natural manual-review triggers.

Suggestions

Add natural user-facing trigger phrases to the description, e.g. 「复盘一下这个 DNA」「看看这个 DNA 表现怎么样」, so it fires on ad-hoc requests as well as scheduled ones.

Replace or gloss internal jargon ('专家包 engagement 工具', '原生 Automation') with plain terms users would actually say, such as '数据复盘' and '定时任务'.

State the volume-based trigger threshold (≥5 条成熟记录) explicitly in the description's 'when' clause so the automatic firing condition is discoverable.

DimensionReasoningScore

Specificity

Lists several concrete third-person actions — '消费 published-track 的发布与互动数据', '按量触发 DNA 评估', '产出报告与优化建议,经用户确认后回写', '派 IT engineer 管理原生 Automation' — with only minor coverage gaps (manual --force review path not mentioned). It exceeds the 1-2-action anchor and falls short of comprehensive coverage.

4 / 5

Completeness

Answers both 'what' (evaluates DNA performance from published-track data, produces reports and suggestions, writes back after user confirmation) and 'when' ('用户开启、调整或停用定时取数复盘时' plus volume-based triggering). Not a 5 because the 'when' clause lacks concrete natural trigger phrases — the manual '复盘一下这个 DNA' trigger is stated only in the body, not the description.

4 / 5

Trigger Term Quality

Contains relevant keywords like 'DNA 评估' and '定时取数复盘', but relies heavily on internal jargon ('published-track', '专家包 engagement 工具', 'IT engineer', '原生 Automation') rather than natural phrases a user would say (e.g., '复盘一下', '表现怎么样', '数据复盘'). Some relevant terms present, but common user-facing variations and synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (DNA performance evaluation for published content) and explicitly delineates boundaries against published-track ('发布与指标记录由 published-track 管理') and platform expert packages ('平台取数由各专家包 engagement 工具负责'), giving it minimal conflict risk with neighboring skills.

5 / 5

Total

16

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

TeamWiseFlow/xiaobei

Path

crews/main/skills/content-calibrator/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.