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 solid skill description that clearly identifies its niche (Typst typesetting), provides explicit trigger guidance via a 'Use when' clause, and includes domain-specific terms that minimize conflict risk. The main weakness is that the capability description could be more specific about the concrete actions it supports (e.g., creating tables, formatting math, building templates) rather than the general 'write correct and idiomatic Typst code'.
Suggestions
Expand the capability list with more concrete actions, e.g., 'create documents, format tables, write mathematical expressions, define custom functions, manage page layouts' to improve specificity.
| 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. A user asking about Typst would naturally use these terms. | 3 / 3 |
Distinctiveness Conflict Risk | Typst is a specific typesetting language with a clear niche. The description includes distinctive triggers like 'Typst', '.typ files', and 'Typst markup' that are unlikely to conflict with LaTeX, Markdown, or other document-related 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, highly actionable Typst skill with excellent concrete examples and good coverage of the ecosystem (packages, templates, CLI usage). Its main weaknesses are moderate verbosity—particularly the extensive inline package catalog and full document templates that could be offloaded to reference files—and a workflow that lacks explicit compile-and-validate checkpoints. The troubleshooting section is useful but would be more effective integrated into a validation workflow.
Suggestions
Move the package catalog and complete document structure patterns into separate reference files (e.g., references/packages.md, references/templates.md) to reduce SKILL.md length and improve progressive disclosure.
Add an explicit compile-and-validate step to the workflow, e.g., 'After writing: compile with `typst compile doc.typ output.pdf`, check for errors, fix and recompile if needed' to create a proper feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity—e.g., the 'Core Principles' section is somewhat generic, the 'When to Consult Documentation' section states obvious things, and some explanatory text could be trimmed. However, most content is substantive and adds value Claude wouldn't inherently know (Typst-specific syntax, package lists, template patterns). | 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. For a skill involving document compilation, there's no clear 'compile and verify' step or feedback loop for fixing compilation errors. The troubleshooting section helps but is separate from the workflow rather than integrated as validation steps. | 2 / 3 |
Progressive Disclosure | The skill references external files (references/syntax.md, references/bibliography.md) which is good progressive disclosure, but the main SKILL.md itself is quite long (~200+ lines) with substantial inline content (complete document patterns, extensive package lists, template examples) that could be split into reference files. The package catalog especially could be a separate reference. | 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
d2b7dff
- 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.