CtrlK
BlogDocsLog inGet started
Tessl Logo

author-zine

Use when writing or updating a zine — Skylark's spec format. Covers the required sections (tl;dr, Components, Structure, Decisions, Changelog) and the principles for what belongs in a zine versus a skill or elsewhere.

71

Quality

86%

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

86%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 concise, well-structured instruction skill that defines a distinctive spec format and gives concrete, opinionated authoring rules. It is lean and appropriately scoped for a single-file skill with no bundle.

DimensionReasoningScore

Conciseness

Lean ~45-line body that defines only the project-specific term ('zine'), states each principle flatly, and avoids explaining anything Claude already knows; every line earns its place.

5 / 5

Actionability

Provides concrete authoring guidance — the five sections in order with what each contains, the forward-guards-only decision rule, and the downward-linking rule — but is format/content guidance rather than executable steps, leaving minor gaps.

4 / 5

Workflow Clarity

The 'five sections, in order' gives a clear construction sequence and the simple-skill exception applies (no destructive/batch ops needing validation), though there are no explicit checkpoints or feedback loops.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files present and no need for external references; the body is well-organized into clear section headers (Where zines live, The five sections, Principles), satisfying the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

87%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, third-person description with an explicit Use-when trigger, concrete enumeration of the five sections it covers, and a highly distinctive keyword ('zine'). Minor room to expand the action verbs beyond write/update.

DimensionReasoningScore

Specificity

Names the domain ('writing or updating a zine') and concretely enumerates the five required sections (tl;dr, Components, Structure, Decisions, Changelog) plus the principles for scoping; the only gap is that the verbs are limited to write/update.

4 / 5

Completeness

Explicitly answers both 'what' ('Covers the required sections... and the principles for what belongs in a zine versus a skill or elsewhere') and 'when' via a concrete 'Use when writing or updating a zine' trigger clause.

5 / 5

Trigger Term Quality

Includes the natural terms a user would say ('writing or updating a zine', 'zine', 'Skylark's spec format'); coverage is good though a few related phrasings (e.g. 'spec', 'document a component') are absent.

4 / 5

Distinctiveness Conflict Risk

The term 'zine' and 'Skylark's spec format' carve out a clear, distinctive niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

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
drufball/skylark
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.