CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cheat-bump

提议并执行 rubric 或 bucket 升级。两种模式:**完整 rubric bump**(最高风险动作,5 步强制 + 跨模型审核)和 **--bucket-only 轻量重校**(只换 bucket 边界,不动 rubric 公式)。**Phase 2 强制走 cheat-score-blind sub-agent 给校准池重打分**——不接受 self-scored fallback。触发词:"升级 rubric"/"bump rubric"/"更新公式"/"我想加一个维度"/"调整权重"/"重校桶"/"recalibrate bucket"。

Quality

85%

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.

The body is an exemplary operational protocol: phased routing, executable prompts and commands, hard validation gates with rollback, and explicit refusal handling for every shortcut a user might request. Its weaknesses are token efficiency — rules are restated across Constants, Key Rules, Refusals, and phase text — and progressive disclosure, since everything lives inline in one long file while all referenced documents sit outside the bundle where their existence cannot be confirmed.

Suggestions

Consolidate the rule statements that currently appear in Constants, Key Rules, Refusals, and the phase bodies (e.g., THRESHOLD immutability and blind-sub-agent enforcement each stated three times) into a single authoritative 'Key Rules' section referenced from the phases.

Move the worked examples with real data — the Phase 3 sample ranking table, Phase 8 console report, and B3 boundary report — into a reference file (e.g., examples.md) and keep only the output format skeleton inline, cutting a substantial fraction of the ~470 lines.

Verify or inline the externally-referenced material (bump-validation-protocol.md, observation-lifecycle.md, rubric-memo.template.md, cheat-score-blind SKILL.md): these paths resolve outside the skill bundle, so a consumer cannot confirm they exist; either bring the needed protocol steps into the bundle's references/ or restructure so the skill is self-contained.

DimensionReasoningScore

Conciseness

The body is ~470 lines where the same rules appear three times: THRESHOLD=0.8 is stated in Constants ("这条写死"), Phase 3 ("不允许临时调低"), and Key Rules #2; blind-sub-agent enforcement appears in Phase 2, Refusals, and Key Rules; Phase B rules are restated in "Phase B 不做的事". Not 2: nothing explains concepts Claude already knows — all material is domain-specific protocol, not padding; not 4: the duplication between Constants / Key Rules / Refusals and the long sample console outputs (Phase 8, B3) could be consolidated without losing meaning.

3 / 5

Actionability

Quotes: the verbatim sub-agent spawn prompt ("script_path: <prediction header 的 Script Path>…不要询问用户 —— 你没有用户"), the exact leak-guard command "grep -E '\d+\s*[wWmMkK万]|播放|实绩|实际'", exact bucket formulas ("buckets = { '退步': (-inf, baseline * 0.3), … }"), concrete state-file JSON, and the full external-LLM audit prompt — all copy-paste executable. Not 4: even edge handling (refusals, retries "重发 Task 最多 3 次", abort conditions) is specified with concrete actions.

5 / 5

Workflow Clarity

Quotes: a routing diagram (Phase A0) dispatching to Phase B vs Phases 0-8, hard validation gates ("排序一致性 < THRESHOLD(默认 0.8) → 本地拒绝"), a mandatory independent audit (Phase 4) with conflict handling ("本地 PASS + 外部 REJECT → 视为 REJECT"), a post-write self-check with rollback (Phase 5d leak guard → "abort bump + 回滚"), and a failure-mode table with retry/exclusion logic. Despite being a destructive batch operation (rewrites rubric_notes.md and all prediction files), every step has an explicit checkpoint or abort path, which clears the destructive-batch cap.

5 / 5

Progressive Disclosure

All links point outside the bundle ("[shared-references/bump-validation-protocol.md](../../shared-references/bump-validation-protocol.md)", "[cheat-score-blind](../cheat-score-blind/SKILL.md)", "[templates/rubric-memo.template.md](../../templates/rubric-memo.template.md)") and no references/, scripts/, or assets/ directories exist in the skill — so the referenced material is unverifiable from the bundle. Meanwhile content that belongs in separate files is inlined: full protocol detail, sample re-scoring tables with real data, complete console-report examples, and three bucket-derivation formula blocks. Not 2: headers, a flow diagram, and tables make it navigable, not a header-less wall; not 4: the 470-line monolith plus external-only references leave real organization gaps.

3 / 5

Total

16

/

20

Passed

Description

91%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 strong: it clearly states what the skill does, splits the two operating modes with their differing rigor, and provides an explicit bilingual trigger-word list that satisfies the 'when' requirement. Its only weakness is spending specificity budget on internal mechanics (blind sub-agent rescoring) rather than user-visible outcomes, and a couple of overly generic trigger phrases.

DimensionReasoningScore

Specificity

Quotes: "两种模式:完整 rubric bump(最高风险动作,5 步强制 + 跨模型审核)和 --bucket-only 轻量重校(只换 bucket 边界,不动 rubric 公式)" — several distinct concrete actions (propose/execute upgrade, 5-step full bump, boundary-only recalibration) with the two modes clearly delineated. Not 5: it spends budget on internal process detail ("Phase 2 强制走 cheat-score-blind sub-agent…不接受 self-scored fallback") instead of user-facing outcomes (e.g., updates rubric_notes.md, validates rank consistency); not 3, since multiple specific actions are named, not just 1-2.

4 / 5

Completeness

Quotes: "提议并执行 rubric 或 bucket 升级" answers "what" concretely, and the explicit 触发词 list plus mode markers (--bucket-only / --propose) answer "when" with concrete trigger phrases. Not 4: the when-clause is explicit and phrase-based rather than merely present-but-vague.

5 / 5

Trigger Term Quality

Quotes: "触发词:'升级 rubric'/'bump rubric'/'更新公式'/'我想加一个维度'/'调整权重'/'重校桶'/'recalibrate bucket'" — seven natural phrasings users would actually say, covering synonyms in both Chinese and English. Not 4: coverage is comprehensive rather than merely good; only trivial variations (e.g., "改权重", "bucket 不准") are absent.

5 / 5

Distinctiveness Conflict Risk

Quotes: "提议并执行 rubric 或 bucket 升级" — a clear niche (rubric version upgrade with a validation protocol) with dedicated bump-specific triggers. Not 5: generic phrases like "我想加一个维度" and "调整权重" could plausibly fire in unrelated contexts (charts, tables, weighting schemes); not 3, since the niche and most triggers are unmistakably about rubric bumping.

4 / 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: 1 missing, 6 suspicious

Warning

Total

13

/

16

Passed

Repository

XBuilderLAB/cheat-on-content

Path

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