typst-author

Generate idiomatic Typst (.typ) code, edit and troubleshoot Typst documents and projects, and answer Typst syntax/reference questions. Use when working with .typ files or when the user explicitly asks for Typst document creation, editing, debugging, compilation, formatting, template work, or package usage.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

77%Weight 40%Scale 1-3

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 executable Typst commands, concrete code, and well-sequenced validation workflows including feedback loops. Its main weaknesses are mild redundancy between the Workflows and Detailed-instructions sections and references to a docs/ bundle that is not present to verify.

Suggestions

Consolidate the overlapping guidance between 'Workflows' and 'Detailed instructions' (post-edit formatting and doc-verification steps appear in both) into a single source of truth to tighten conciseness.

Ship or verify the referenced docs/ bundle (docs/reference/*.md, docs/guides/*.md, docs/tutorial/writing-in-typst.md) so the well-signaled one-level-deep links actually resolve, lifting progressive_disclosure.

For the probing section, note the expected typst version requirement for the metadata/query stdin pattern, since introspection behavior can vary across releases.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of generic concept explanations, but the 'Workflows' and 'Detailed instructions' sections overlap (e.g., post-edit formatting and doc-verification guidance appear in both), so it could be tightened — not quite the lean level-3 where every token is irreducible.	2 / 3
Actionability	Provides copy-paste-ready, executable commands and code — 'typstyle --check <file>', 'typst compile', and the stdin probe 'printf '#metadata(1 + 2) <probe>\n' \| typst query - "<probe>" --field value --one' — matching the fully-executable level-3 anchor.	3 / 3
Workflow Clarity	The 'Post-edit formatting checks' and 'Detailed instructions' are explicitly sequenced with validation checkpoints (typstyle --check, typst compile), a diff-inspection feedback loop, and a stop-and-ask gate for untouched code, matching the level-3 anchor with error-recovery feedback loops.	3 / 3
Progressive Disclosure	References are well-signaled and one-level-deep in the text (docs/reference/syntax.md, docs/guides/tables.md, etc.), but the referenced docs/ bundle files are not present in the skill directory to verify, so actual navigation cannot be completed — falling short of the fully-resolvable level-3 anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

A strong, third-person description that concisely states concrete capabilities and pairs them with explicit, natural-language triggers tied to the .typ extension and common Typst tasks. It cleanly satisfies the what/when requirement and is unlikely to fire for unrelated skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Generate idiomatic Typst (.typ) code, edit and troubleshoot Typst documents and projects, and answer Typst syntax/reference questions' — matching the level-3 anchor rather than the single-action level-2 example.	3 / 3
Completeness	Explicitly states both what it does and when to use it via the 'Use when working with .typ files or when the user explicitly asks for...' clause, matching the level-3 anchor; not the level-2 case where 'when' is only implied.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — '.typ files', 'document creation, editing, debugging, compilation, formatting, template work, or package usage' — with good variation rather than the sparse level-2 'Works with PDF files' style.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Typst/.typ) with file-extension and task-specific triggers, making conflicts with other skills unlikely; far more distinct than the generic level-1/2 examples.	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: 16 missing, 15 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: jihe520/MathModelAgent
Path: skills/typst-author/SKILL.md
Commit: 11f3862

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.