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).
84
77%
Does it follow best practices?
Impact
96%
1.09xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./typst-writer/SKILL.mdQuality
Discovery
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 domain, and strong distinctiveness. The main weakness is that the capability description could be more specific about concrete actions (e.g., creating tables, styling pages, managing bibliographies) rather than the somewhat general 'write correct and idiomatic Typst code'.
Suggestions
Add more specific concrete actions to boost specificity, e.g., 'Write correct and idiomatic Typst code for document typesetting, including page layout, tables, mathematical notation, bibliographies, and custom styling.'
| 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 doesn't list multiple concrete discrete actions like 'extract tables, fill forms, merge documents'. | 2 / 3 |
Completeness | Clearly answers both 'what' (write correct and idiomatic Typst code for document typesetting) and 'when' (explicit 'Use when' clause covering creating/editing .typ files, working with Typst markup, or answering questions about Typst syntax and features). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'Typst', '.typ', 'Typst markup', 'Typst syntax', 'document typesetting', plus specific technical terms users would mention like 'arrays', 'content blocks', 'function definitions', 'state management'. Good coverage of what users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Typst is a specific typesetting language with a clear niche. The description includes distinct triggers like '.typ files', 'Typst markup', 'Typst syntax' that are unlikely to conflict with LaTeX, Markdown, or other document skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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 solid, actionable skill with excellent concrete examples and executable code covering Typst syntax, packages, templates, and document structure. Its main weaknesses are verbosity (too much inline content that could be offloaded to reference files) and a workflow that lacks explicit validation/compilation checkpoints. The package list and template examples are genuinely useful but contribute to a lengthy document that could benefit from better progressive disclosure.
Suggestions
Move the extensive package list and complete document structure patterns into separate reference files (e.g., references/packages.md, references/templates.md) and link to them from the main skill.
Integrate a compile-and-validate step into the workflow (e.g., 'After writing: compile with `typst compile doc.typ` and review warnings/errors before delivering').
Trim generic advice like 'Verify uncertain syntax' and 'Use idiomatic patterns' — 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 | The workflow section provides a basic 3-step process (before/while/after writing) but lacks explicit validation checkpoints. There's no feedback loop for catching errors during compilation, and the troubleshooting section is separate from the workflow rather than integrated as validation steps. For document generation tasks, a compile-and-verify step would strengthen this. | 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 detail is skewed toward too much inline content. | 2 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- YPares/agent-skills
- Commit
84b1da5
- 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.