CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cheat-persona

从复盘评论数据派生 / 刷新账号的受众画像,写入 audience.md。这是和 rubric 平行的第二个派生物——rubric 答"怎么打分",persona 答"谁在看"。cheat-seed 选题 / 写稿时读它。**audience.md 含实绩信号,cheat-score-blind 硬禁读**。触发词:"构造受众画像"/"更新 persona"/"我的观众是谁"/"build persona"/"刷新受众画像"/"看看我的受众画像"。

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A strongly structured, highly actionable instruction skill with a genuinely sequenced workflow and honest limits (Refusals, Known limitations). The main quality cost is redundancy: the pollution-isolation principle is restated so many times that it inflates token cost without adding guidance, and the analysis steps themselves rely on judgment more than the surrounding scaffolding.

Suggestions

Consolidate the persona/rubric isolation rationale into one section (e.g. keep '⚠️ 污染隔离' and reduce the rest to one-line pointers in Key Rules / Integration) — the same leak argument is currently made five times.

Add a brief post-write verification step in Phase 4/5 (check audience.md contains header fields, verified/hypothesized/anti-persona sections per the template) to close the workflow's validation gap.

Tighten Phase 2 with concrete operational hints (e.g. how to bucket a comment into 自我认同/情绪寄存/反驳点/语言, or what counts as one evidence comment) so the analytical core matches the specificity of the surrounding phases.

DimensionReasoningScore

Conciseness

The body is dense and operational (no teaching of known concepts), but the persona/rubric isolation rationale is explained at length in at least three dedicated places ('核信定位 — 绝不混', '⚠️ 污染隔离', Key Rule 4) plus two Refusals and the Integration section — noticeably more than the 'minor instances' of anchor 4. Fits anchor 3: could be tightened.

3 / 5

Actionability

Concrete and executable for an instruction skill: named constants (MIN_RETROS_FOR_DATA_GROUNDED=3, MIN_COMMENTS_PER_TRAIT=3, SEED_FROM_BENCHMARK=auto), explicit file paths, a Phase 1 decision table, evidence rules requiring 出处 and counts, a template link, and a full example output report. Falls short of anchor 5 because the core analysis mechanics (how to cluster comments, '统计占比') are left entirely to judgment.

4 / 5

Workflow Clarity

Six phases are clearly sequenced with an overview diagram and explicit checkpoints (Phase 1 data-sufficiency gate with exit, Phase 2 evidence-count gate, Phase 3 cross-check flag, Phase 5 diff vs previous version). The destructive-op cap does not apply — the overwrite rebuild preserves version history and is explicitly documented as re-runnable. Minor gap versus anchor 5: no post-write verification that audience.md matches the template structure.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent), so the skill is a single well-sectioned file with one-level-deep references (templates/audience.template.md, ../cheat-score-blind/SKILL.md). Good structure and navigation throughout; falls short of anchor 5 because the referenced template and sibling-skill paths live outside the skill bundle and their content is not summarized inline as a fallback.

4 / 5

Total

15

/

20

Passed

Description

90%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.

A well-crafted description with excellent trigger coverage, explicit what/when, and clear separation from sibling skills. Its main weakness is that capability coverage is thin relative to the internal-architecture context it carries.

Suggestions

Trade some of the cross-skill architecture detail (rubric/cheat-seed/cheat-score-blind relationships) for capability breadth — e.g. mention comment clustering into identity/emotion/rebuttal/language dimensions and confidence tiering so the 'what' is comprehensive.

The audience.md isolation note ('cheat-score-blind 硬禁读') is important but could be compressed to one short clause; it is a body-level concern and costs description budget.

Consider naming the output's consumers in one compact phrase ('写入 audience.md,供 cheat-seed 选题/写稿参考') instead of multi-sentence derivation-relationship prose.

DimensionReasoningScore

Specificity

The description names the domain and 2 concrete actions ('从复盘评论数据派生 / 刷新账号的受众画像,写入 audience.md') but is not comprehensive — it spends most of its budget on cross-skill architecture ('这是和 rubric 平行的第二个派生物… cheat-seed 选题 / 写稿时读它… cheat-score-blind 硬禁读') rather than what the skill actually does (comment clustering, confidence tiering, rubric cross-check, rebuild). Fits anchor 3; not anchor 4 because the capability gaps are more than minor.

3 / 5

Completeness

Both 'what' (derive/refresh audience persona from retrospective comment data, write audience.md) and 'when' are explicitly answered — the 触发词 list is equivalent explicit trigger guidance, so the missing-'Use when' cap does not apply.

5 / 5

Trigger Term Quality

Six explicit, natural trigger phrases in both Chinese and English ('构造受众画像'/'更新 persona'/'我的观众是谁'/'build persona'/'刷新受众画像'/'看看我的受众画像') with synonym variations — comprehensive coverage of what a user would actually say.

5 / 5

Distinctiveness Conflict Risk

The description explicitly distinguishes persona derivation from rubric derivation ('rubric 答"怎么打分",persona 答"谁在看"') and its triggers are persona-specific nouns with no overlap risk against sibling skills. Anti-drift check against anchor 4 (minor overlap) — the unique trigger surface keeps it at 5.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository

XBuilderLAB/cheat-on-content

Path

skills/cheat-persona/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.