typst-writer

Write correct and idiomatic Typst code for document typesetting. Use when creating or editing Typst (.typ) files, working with Typst markup, or answering questions about Typst syntax and features. Focuses on avoiding common syntax confusion (arrays vs content blocks, proper function definitions, state management).

1.09x

Quality

76%

Does it follow best practices?

Impact

96%

1.09x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./typst-writer/SKILL.md

Quality

Content

65%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 highly actionable with concrete, executable Typst examples, but it is padded and inlines material (package catalog, full templates, troubleshooting) that would be better split into reference files. The workflow lacks an explicit compile/validate feedback loop.

Suggestions

Add an explicit validation step to the Workflow's 'After writing' phase (e.g. run `typst compile doc.typ` and fix any errors before considering the task done) to create a validate-fix-retry loop.

Move the 'Popular packages' catalog and the full template/document-structure examples into a reference file (e.g. references/packages.md) and summarize a few key entries inline with a link, reducing SKILL.md length.

Trim explanatory prose like the font-warning aside and the SearXNG/GitHub search tutorial to the minimum needed, since Claude can derive general background; keep only Typst-specific gotchas.

Dimension	Reasoning	Score
Conciseness	The body is efficient in core sections but noticeably padded: a ~20-entry 'Popular packages' catalog, full template examples, and prose like 'Font warnings don't prevent compilation; the document will use fallback fonts' explain or catalog content Claude could derive or that belongs in a reference file, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Provides copy-paste-ready executable guidance across common cases: a full function/state example, real `gh search` commands, a `typst query` one-liner, package import syntax, and complete template usage blocks (charged-ieee, bubble), matching the 'fully executable; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The Workflow section sequences before/while/after writing and 'Common Mistakes to Avoid' acts as a review checklist, but the 'after writing' step only says to 'review for syntax leaking in' without an explicit compile/validate checkpoint (e.g. `typst compile`) or fix-retry loop, matching the 'steps listed but validation gaps' anchor.	3 / 5
Progressive Disclosure	Two real reference files (syntax.md, bibliography.md) are linked with clear signals ('For detailed syntax rules... see'), but large blocks that belong in separate files—the package catalog, full template examples, complete document-structure patterns, and troubleshooting—are inlined in SKILL.md, matching 'some structure... content that should be separate is inline'.	3 / 5
	Total	14 / 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.

The description is strong: it concisely states what the skill does and gives explicit, concrete 'Use when...' triggers tied to the Typst niche. Minor room to add a few more user-natural synonyms, but conflict risk and completeness are excellent.

Dimension	Reasoning	Score
Specificity	Names the Typst domain plus several concrete actions ('creating or editing Typst (.typ) files, working with Typst markup, or answering questions about Typst syntax and features') and specific pitfalls ('arrays vs content blocks, proper function definitions, state management'), with only minor coverage gaps, matching the 'several specific actions' anchor.	4 / 5
Completeness	Explicitly answers both 'what' ('Write correct and idiomatic Typst code for document typesetting... Focuses on avoiding common syntax confusion') and 'when' ('Use when creating or editing Typst (.typ) files, working with Typst markup, or answering questions about Typst syntax and features') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('Typst', 'Typst (.typ) files', 'Typst markup', 'Typst syntax and features') plus the .typ extension, giving good coverage; a few synonyms (e.g. 'typesetting' as a trigger) are underused, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Typst is a clear niche with distinct triggers (.typ extension, Typst markup/syntax) and minimal overlap with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: YPares/agent-skills
Path: typst-writer/SKILL.md
Commit: e9d2149

Reviewed: 3 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.