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

82%

Does it follow best practices?

Impact

96%

1.09x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The body is highly actionable with multiple complete executable Typst examples and CLI commands, and it correctly signals two real reference files. It is weakened by verbosity (large inline package/template catalogs and a Quick Syntax Reference duplicating the syntax.md bundle) and by workflow steps that lack explicit validation checkpoints for compilation and package operations.

Suggestions

Move the inline 'Popular packages' and 'Popular templates' catalogs into a dedicated reference file (e.g. references/packages.md), keeping only a few top examples in SKILL.md with a clear link, to reduce token load and improve conciseness.

Remove or shrink the 'Quick Syntax Reference' section since it duplicates references/syntax.md; replace it with a one-line pointer to that file.

Add explicit validation checkpoints to the Workflow section — e.g. after writing or before importing a package, run `typst compile` to verify and only proceed on success — turning the reactive Troubleshooting notes into a sequenced validate→fix→retry loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable examples, but padded by a 20-item inline package catalog, an inline template catalog, and a Quick Syntax Reference that duplicates content already in references/syntax.md — these tokens compete with context unnecessarily.	2 / 3
Actionability	Provides complete, copy-paste-ready Typst code (function definitions, state management, template application, full document structure) plus concrete CLI commands (gh search, typst query, typst compile) — fully executable guidance.	3 / 3
Workflow Clarity	A Before/While/After workflow and Common Mistakes list exist, but there are no explicit validation checkpoints or validate→fix→retry feedback loops for the compilation/package operations; the Troubleshooting section is reactive rather than a sequenced checkpoint.	2 / 3
Progressive Disclosure	References two real, well-signaled, one-level-deep bundle files (references/syntax.md, references/bibliography.md), but substantial detail that belongs in references — the package catalog, template catalog, and full document-structure patterns — remains inline in SKILL.md.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 specific, complete, and distinct: it states concrete capabilities, provides an explicit 'Use when...' trigger clause with natural terms including the .typ extension, and occupies a clear niche unlikely to conflict with other skills. Voice is appropriately third person throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Write correct and idiomatic Typst code', 'creating or editing Typst (.typ) files', 'working with Typst markup', 'answering questions about Typst syntax' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Write correct and idiomatic Typst code for document typesetting') and when via a clear 'Use when...' clause with enumerated triggers.	3 / 3
Trigger Term Quality	Includes natural terms users would say — 'Typst (.typ) files', 'Typst markup', 'Typst syntax and features' — with the .typ extension as a strong concrete trigger.	3 / 3
Distinctiveness Conflict Risk	Typst is a clearly distinct niche with unique triggers (.typ files, Typst markup) unlikely to overlap with or trigger other skills.	3 / 3
	Total	12 / 12 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
Commit: ac633fa

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