CtrlK
BlogDocsLog inGet started
Tessl Logo

cheat-init

cheat-on-content 的首次 onboarding 与脚手架创建器。统一流程——所有用户都走相同 5 阶段闭环,唯一区别是"发过视频的人"会在 init 时多一步:抓取已有视频建立历史 context(用于后续 cheat-seed 给更贴合的选题、更准的 baseline)。触发词:"初始化"/"init"/"首次使用"/"我是新用户"/"setup cheat-on-content"。**必须在用户第一次会话执行;其他子 skill 在 .cheat-state.json 不存在时自动路由到此。**

68

Quality

86%

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

77%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 highly actionable, well-sequenced onboarding workflow with strong validation and error-handling, but it is verbose and monolithic — rationale prose and large structural artifacts (state schema, enum tables, verbatim scripts) are inlined rather than offloaded to reference files.

Suggestions

Move the verbatim user-facing dialogue blocks and the full .cheat-state.json schema into reference files under references/, keeping SKILL.md as an overview that points to them — this would improve both conciseness and progressive_disclosure.

Trim or relocate the design-rationale asides ('为什么叫 v0', '为什么单独一个文件', etc.) into a single design-notes reference; the agent needs the rule, not the history of the decision, in the main flow.

Extract the per-question enum mapping tables (Q1/Q3/Q4/Q5) into a references/mappings.md file and reference it once, reducing repeated inline tables.

DimensionReasoningScore

Conciseness

Mostly efficient given the complexity of a multi-phase onboarding flow, but retains numerous rationale asides ('为什么叫 v0', '为什么单独一个文件') and long verbatim dialogue blocks that could be tightened without losing clarity.

3 / 5

Actionability

Provides fully executable guidance: a concrete .cheat-state.json template, explicit enum mapping tables (Q1→content_form, Q3→data_collection), exact commands (chmod +x, git rm -r --cached ...), and precise file paths.

5 / 5

Workflow Clarity

Phases 0–5 are clearly sequenced with explicit validation checkpoints (Phase 4 hook test, adapter verification), feedback loops (import failure → graceful degradation, hook failure → explicit user notice), and a State 字段写入清单 checklist.

5 / 5

Progressive Disclosure

Section structure is reasonable and external template references are clearly signaled, but no bundle reference files exist and large inlined content (the full JSON state schema, mapping tables, verbatim dialogue) that could live in separate files makes the SKILL.md monolithic.

3 / 5

Total

16

/

20

Passed

Description

95%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 strong, specific description that clearly states what the skill does, when to use it via natural trigger phrases, and how it is distinct from sibling skills. Minor additional specificity on the scaffolding outputs could push it further, but it already covers the essentials well.

DimensionReasoningScore

Specificity

Lists several concrete actions ('首次 onboarding 与脚手架创建器', '抓取已有视频建立历史 context') rather than vague language, but coverage is not exhaustive enough for a 5.

4 / 5

Completeness

Explicitly answers both 'what' (onboarding + scaffolding creator) and 'when' (concrete trigger words plus the rule '必须在用户第一次会话执行;其他子 skill 在 .cheat-state.json 不存在时自动路由到此').

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrases with synonyms in both Chinese and English ('初始化'/'init'/'首次使用'/'我是新用户'/'setup cheat-on-content') that users would naturally say.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (cheat-on-content first-time onboarding) with distinct triggers and unique auto-routing logic, giving minimal conflict risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

75%

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

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (537 lines); consider splitting into references/ and linking

Warning

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: 1 suspicious

Warning

Total

12

/

16

Passed

Repository
XBuilderLAB/cheat-on-content
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.