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

77%

Does it follow best practices?

Impact

96%

1.09x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

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

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive and highly actionable Typst skill with excellent concrete examples, executable code, and useful package/template guidance. Its main weaknesses are verbosity (the file tries to be both a quick reference and a comprehensive guide) and lack of explicit validation steps in the workflow. Splitting the package catalog, template examples, and document structure patterns into referenced files would improve both conciseness and progressive disclosure.

Suggestions

Move the extensive package list, template usage section, and complete document structure patterns into separate referenced files (e.g., references/packages.md, references/templates.md) to reduce main file length and improve progressive disclosure.

Add an explicit compilation/validation step to the workflow, e.g., 'After writing: compile with `typst compile doc.typ` and verify no errors before delivering.'

Remove generic advice like 'Verify uncertain syntax' and 'Use idiomatic patterns' from Core Principles—these are obvious to Claude and waste tokens.

Dimension	Reasoning	Score
Conciseness	The skill is fairly long (~250 lines) and includes some content Claude likely already knows (e.g., general advice like 'verify uncertain syntax', 'use idiomatic patterns'). The package list and template examples are useful but could be more compact. Some sections like 'When to Consult Documentation' state the obvious.	2 / 3
Actionability	The skill provides fully executable Typst code examples, concrete CLI commands for package searching and querying, specific package import syntax, and complete document structure patterns. The examples are copy-paste ready and cover multiple real scenarios.	3 / 3
Workflow Clarity	There is a basic 3-step workflow (before/while/after writing) but it lacks explicit validation checkpoints. The troubleshooting section helps with error recovery, but there's no feedback loop for verifying compilation success before proceeding. For document manipulation tasks, missing a 'compile and verify' step between writing and delivering is a gap.	2 / 3
Progressive Disclosure	The skill references two external files (references/syntax.md and references/bibliography.md) which is good progressive disclosure, but the main file itself is quite long with inline content that could be split out (e.g., the extensive package list, complete document structure patterns, template usage details). The balance between overview and inline detail is off—too much is kept in the main file.	2 / 3
	Total	9 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-structured skill description with a clear 'Use when' clause, good trigger term coverage for the Typst ecosystem, and strong distinctiveness. The main weakness is that the capability description could be more specific about concrete actions (e.g., creating tables, formatting math, building templates) rather than the somewhat general 'write correct and idiomatic Typst code'. The focus areas at the end add useful specificity but are more about pitfalls than capabilities.

Suggestions

Add more specific concrete actions beyond 'write correct and idiomatic Typst code', such as 'create layouts, format mathematical expressions, build document templates, style text and headings'.

Dimension	Reasoning	Score
Specificity	It names the domain (Typst code/document typesetting) and mentions some actions ('creating or editing', 'answering questions'), plus notes specific focus areas (arrays vs content blocks, function definitions, state management), but the core capability statement 'Write correct and idiomatic Typst code' is somewhat general rather than listing multiple distinct concrete actions like 'create tables, format equations, build templates'.	2 / 3
Completeness	Clearly answers both 'what' (write correct and idiomatic Typst code for document typesetting, focusing on common syntax pitfalls) and 'when' (explicit 'Use when' clause covering creating/editing .typ files, working with Typst markup, or answering Typst syntax questions).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms: 'Typst', '.typ', 'Typst markup', 'Typst syntax', 'document typesetting'. These cover the main ways a user would refer to Typst-related tasks, including the file extension. Good coverage of natural variations.	3 / 3
Distinctiveness Conflict Risk	Typst is a specific typesetting language with a clear niche. The description is unlikely to conflict with LaTeX, Markdown, or general code-writing skills due to the explicit mention of Typst, .typ files, and Typst-specific concepts like arrays vs content blocks.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: YPares/agent-skills
Commit: bc4c2ce

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