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).
87
81%
Does it follow best practices?
Impact
96%
1.09xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
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 with excellent completeness and distinctiveness. It clearly identifies the domain, includes an explicit 'Use when' clause with good trigger terms, and carves out a distinct niche around Typst specifically. The main weakness is that the specific capabilities could be more concrete—listing particular actions like creating tables, formatting math, or generating layouts rather than focusing on what to avoid.
Suggestions
Add more concrete action verbs describing specific Typst capabilities, e.g., 'create documents with tables, math equations, bibliographies, and custom layouts' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Typst code/document typesetting) and mentions some actions (creating, editing, answering questions), but the specific capabilities are more about avoiding pitfalls than listing concrete actions like 'create tables, format equations, generate bibliographies'. | 2 / 3 |
Completeness | Clearly answers both 'what' (write correct and idiomatic Typst code for document typesetting, focusing on common syntax issues) 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 files', 'Typst markup', 'Typst syntax', 'document typesetting'. These cover the main ways a user would refer to Typst-related tasks, including the file extension. | 3 / 3 |
Distinctiveness Conflict Risk | Typst is a very specific typesetting language with a clear niche. The description explicitly names Typst, .typ files, and Typst-specific concerns (arrays vs content blocks, state management), making it highly unlikely to conflict with LaTeX, Markdown, or other document skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%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, comprehensive Typst skill that excels in actionability with executable code examples, concrete CLI commands, and specific package recommendations. Its progressive disclosure is well-structured with clear references to supporting files. The main weaknesses are moderate verbosity (the extensive package list and some generic guidance could be tightened) and a workflow that lacks explicit validation/compilation checkpoints to verify correctness.
Suggestions
Integrate a compilation verification step into the workflow (e.g., 'After writing: compile with `typst compile doc.typ` and check for errors before proceeding').
Consider moving the extensive package list to a separate reference file (e.g., references/packages.md) and keeping only the top 5-6 most commonly needed packages inline to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity - e.g., the 'Core Principles' section is somewhat generic, and the extensive package list and template examples could be more tightly organized. Some sections like 'When to Consult Documentation' state obvious things. However, most content is genuinely useful and not padded with explanations of basic concepts. | 2 / 3 |
Actionability | The skill provides fully executable Typst code examples, concrete CLI commands for package searching and querying, specific import syntax, and copy-paste ready document templates. The common mistakes section with ❌ markers gives precise, actionable corrections. | 3 / 3 |
Workflow Clarity | The workflow section provides a reasonable 3-step process (before/while/after writing), but lacks explicit validation checkpoints. There's no feedback loop for catching errors - the troubleshooting section exists but isn't integrated into the workflow. For document manipulation tasks, missing validation steps (e.g., compile and check output) cap this at 2. | 2 / 3 |
Progressive Disclosure | The skill effectively uses one-level-deep references to external files (references/syntax.md, references/bibliography.md) and external documentation URLs. The main file serves as a well-organized overview with clear signposting to detailed resources, and content is appropriately split between quick reference and detailed examples. | 3 / 3 |
Total | 10 / 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
aed1afb
- 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.