CtrlK
BlogDocsLog inGet started
Tessl Logo

story-review

多视角对抗式审查。full/lean 模式在已部署 reviewer agents 时并行 spawn;缺失/异常 agents 或 spawn 失败时自动降级 solo,参考文件不可读时使用内置 rubric fallback。触发方式:/story-review、/审查、「审查一下」「帮我审一下」。

68

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 highly actionable with clear, validated workflows and well-organized references, but it is noticeably verbose with repeated fallback enumerations and a bulky inline fallback rubric. Tightening redundancy would improve token efficiency without losing clarity.

Suggestions

Consolidate the fallback-reason enumerations into a single shared list (Phase 0) and have the metadata table and report templates reference it by name instead of repeating the full set of strings three times.

Move the embedded fallback rubric (核心卖点/冲突推进/... and AI味/平台 fallback summaries) into a reference file and keep only a short pointer plus the one mandatory sentence-length rule inline, reducing duplication with references/quality-rubric.md and the rubric/ files.

Compress the multi-platform agent-format deployment details (Claude/OpenCode/Codex/Antigravity frontmatter rules) into a compact table or a single reference, since the per-platform prose repeats the same malformed-agent logic.

DimensionReasoningScore

Conciseness

The body is noticeably verbose — ~470 lines with repeated enumerations of fallback strings across the Phase 0 list, the metadata field table, and both report templates, plus a long version-notice paragraph. While much is genuine novel procedure rather than concepts Claude already knows, the redundancy and padding pull it below the 'mostly efficient' score-3 anchor and toward score 2. It is not score 1 because it does not extensively explain concepts Claude already knows.

2 / 5

Actionability

Provides fully executable, copy-paste-ready guidance: exact script invocations (`node scripts/normalize-punctuation.js --check ...`), complete per-agent prompt templates, a concrete YAML Findings Schema, and exact report templates covering the common full/lean/solo cases.

5 / 5

Workflow Clarity

Clear Phase 0→1→2→3→4 sequence with explicit validation and degradation checkpoints (spawn-failed → solo), feedback loops for the destructive tracking_commit path (check → fix → recheck), and a precise cross-batch state.md contract, matching the top anchor.

5 / 5

Progressive Disclosure

Good one-level-deep structure: a canonical-path reference table points to verified real files in references/ and scripts/, and SKILL.md serves as overview plus inline fallback rubric. It is not score 5 because the embedded fallback rubric section duplicates material that also lives in reference files, a minor organization overlap.

4 / 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.

The description is specific, trigger-rich, and complete, naming both the operational mechanism (parallel spawn with solo/fallback degradation) and concrete user-facing triggers. It is a strong, well-distinguished description whose only minor gap is not explicitly naming the review-output artifact.

DimensionReasoningScore

Specificity

Lists several concrete operational actions (parallel spawn of reviewer agents, auto-downgrade to solo, embedded rubric fallback) rather than a single vague verb, though it stops short of naming the review outputs themselves. It sits above score 3 (domain + 1-2 actions) but below 5 (full coverage of concrete outputs) because it omits what the review actually produces.

4 / 5

Completeness

Explicitly answers both 'what' (multi-perspective adversarial review via parallel spawn with solo/fallback degradation) and 'when' (concrete trigger phrases and slash commands), matching the top anchor with concrete trigger guidance.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger terms users would actually say: the slash command '/story-review', '/审查', and the phrases '审查一下' and '帮我审一下'. Covers synonyms and the natural Chinese phrasing a user would use, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

The '多视角对抗式审查' niche plus story-review/审查 triggers carve a clear, distinct purpose with minimal overlap risk against other skills, matching the top anchor.

5 / 5

Total

19

/

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.

Validation13 / 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

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
worldwonderer/oh-story-claudecode
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.