CtrlK
BlogDocsLog inGet started
Tessl Logo

writing-fragments

Writing, explore:挖掘原始 fragments,暂不施加任何结构。

54

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/in-progress/writing-fragments/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-crafted instruction-only skill: it defines a non-obvious concept (fragments) with a vivid example taxonomy, gives a concrete file format, and specifies precise behavioral rules (append-only, re-read before write, one-time path question) that make it directly executable. The main gaps are the undefined 'grilling session' protocol and a small amount of philosophical padding.

DimensionReasoningScore

Conciseness

The body is lean and teaches genuinely non-obvious domain concepts (the fragment taxonomy, leading words) that Claude would not already know, with a compact copy-paste format example. It stays at 4 rather than 5 because a few flavor lines ('Novelist's diary 是模型...') and some framing about the exploit phase could be trimmed without loss.

4 / 5

Actionability

Guidance is highly concrete and executable for an instruction-only skill: '只询问一次文档保存到哪里', '在顶部放一个带 working title 的单一 H1...不要 metadata、TOC 或 date', '每次写入前:从磁盘重新读取文件...永远不要 overwrite;只 append', plus a complete file-format example. It falls short of 5 because '运行一个产出 fragments 的 grilling session' references an interview protocol that is never defined in the skill.

4 / 5

Workflow Clarity

The sequence is clear (ask the path once → capture from the user's first message → first write with H1 only → re-read from disk before every write → append only, with in-place edits on request) and the re-read-before-write rule acts as a checkpoint that preserves user edits between turns. It is not 5 because the steps are dispersed across prose rather than sequenced, and the grilling-session protocol itself is left implicit.

4 / 5

Progressive Disclosure

There are no bundle files, and at ~73 lines with well-separated <what-to-do>/<supporting-info> sections and clear H2 headings, keeping everything inline is the right call — no broken or buried references exist. It is not 5 because the supporting-info section carries background material (e.g., the novelist's-diary model) that sits at the edge of what the overview needs.

4 / 5

Total

16

/

20

Passed

Description

45%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 communicates an appealing concept (unstructured fragment mining for writing) but is too terse to function well as a skill description: it lists almost no concrete capabilities, includes no 'use when' trigger guidance, and relies on terms ('fragments', 'explore') whose meaning is only established in the body. It reads more like a tagline than a description.

Suggestions

Add a 'Use when...' clause stating when this skill applies (e.g., 'Use when the user wants to brainstorm, freewrite, or collect raw material for an essay before outlining').

List 2-3 concrete capabilities in the description (e.g., 'run an interview-style session, capture fragments verbatim into a single markdown file, separate fragments with horizontal rules') instead of the single vague phrase '挖掘原始 fragments'.

Include natural trigger terms and synonyms users would actually say — 'writing', 'drafting', 'brainstorm', 'freewriting', 'essay', 'raw notes' — to improve both trigger quality and distinctiveness from general writing skills.

DimensionReasoningScore

Specificity

The description names the domain ('Writing, explore') but offers only one vague action ('挖掘原始 fragments') plus a constraint ('暂不施加任何结构'), matching the anchor 'names the domain but actions are minimal or generic'. It does not reach 3 because no concrete, specific actions (comparable to 'extracts text and tables') are listed.

2 / 5

Completeness

The 'what' is reasonably clear (mine raw fragments without imposing structure) but there is no 'Use when...' clause or any equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. It is not 2 because the 'what' is more than vague, and not 4 because the 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

'Writing' and 'fragments' are keywords a user might naturally say, but common variations and synonyms ('draft', 'brainstorm', 'free writing', 'outline') are missing. This matches anchor 3 ('some relevant keywords but missing common variations or synonyms') rather than 4, which requires good coverage.

3 / 5

Distinctiveness Conflict Risk

'Writing' is broad and overlaps with many writing-related skills, but the fragment/no-structure framing carves out a distinct explore-phase niche, matching anchor 3 ('somewhat specific but could still overlap with similar skills'). It is not 4 because the trigger surface is too thin to reliably distinguish it from generic writing help.

3 / 5

Total

11

/

20

Passed

Validation

100%

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