writing-beats

Writing, exploit——把原始素材组装成一段节拍旅程，在某个 beat 依赖一个术语之前先把它 grounded。

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/in-progress/writing-beats/SKILL.md

Quality

Content

78%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 content is a well-structured, actionable CYOA writing workflow with clear sequencing and genuine validation/feedback checkpoints. It is lean and appropriately self-contained for a simple instruction skill.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence, explaining only the skill-specific 'grounding' mechanic without padding basic writing concepts; a few sentences in the Grounding section could be tightened.	4 / 5
Actionability	Concrete numbered steps (read the article file from disk, write exactly one beat, present 2–3 candidate next beats) give executable guidance with only minor gaps in how to format candidate previews.	4 / 5
Workflow Clarity	A clear 5-step sequence with an explicit re-read-from-disk checkpoint and feedback loops for user edits and rewrite requests; lacks a formal error-recovery path but is not a destructive/batch operation.	4 / 5
Progressive Disclosure	A self-contained, well-organized skill under ~60 lines with clearly signaled sections (<what-to-do>, <supporting-info>, subheadings) and a one-level internal anchor; no external references are needed.	5 / 5
	Total	17 / 20 Passed

Description

42%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 states a concrete what but omits any explicit when-to-use trigger, and its keywords are mostly skill jargon rather than natural user phrases. It is moderately specific but generic at the lead.

Suggestions

Append an explicit 'Use when…' trigger clause naming natural user phrases (e.g. 'when the user wants to draft an article or essay from rough notes').

Replace or augment the generic lead 'Writing' with a more distinctive trigger term a user would actually say.

Add 1–2 more concrete actions (e.g. 'offers branching next-beat options', 'preserves user edits') to broaden specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('把原始素材组装成一段节拍旅程') and one concrete action ('在某个 beat 依赖一个术语之前先把它 grounded'), but coverage is limited to that single action.	3 / 5
Completeness	The 'what' is clear (assemble raw material into a beat journey, ground terms before use) but there is no 'Use when…' or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Only the generic keyword 'Writing' resembles a natural user phrase; 'exploit', '节拍旅程', 'beat', and 'grounded' are skill-internal jargon that users would not naturally say.	2 / 5
Distinctiveness Conflict Risk	The beat/grounding framing is a distinct niche, but the leading word 'Writing' is broad and risks overlap with general writing skills.	3 / 5
	Total	11 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: vinvcn/mattpocock-skills-zh-CN
Path: skills/in-progress/writing-beats/SKILL.md
Commit: 9fb0161

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.