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

85%Weight 40%Scale 1-5

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

Highly actionable body with concrete code, clear sequenced workflows, and validation feedback loops for destructive formatting changes. The main defect is that all docs/ references point to non-existent bundle files, undermining the progressive-disclosure structure.

Suggestions

Ship the referenced docs/ bundle (docs/reference/syntax.md, docs/tutorial/writing-in-typst.md, etc.) or remove/replace the dangling links so every referenced path resolves to a real file.

Consolidate 'Common mistakes to avoid' and 'Quick syntax reference' into the bundled docs to reduce inline length while keeping only the highest-value gotchas.

Verify the metadata/query probe example target paths (docs/reference/introspection/query.md, metadata.md) exist, since the probing workflow depends on them.

Dimension	Reasoning	Score
Conciseness	Mostly lean and actionable with domain-specific gotchas rather than generic Claude knowledge, but a few sections (e.g. 'Common mistakes to avoid' and 'Quick syntax reference') could be tightened and consolidated into the bundled docs.	4 / 5
Actionability	Provides copy-paste ready code (minimal document example, set/show rule snippets) and specific executable commands like 'typstyle --check <file>', 'typst query - "<probe>" --field value --one', and 'command -v typstyle' covering common cases.	5 / 5
Workflow Clarity	Detailed instructions are sequenced 1–7 with explicit validation checkpoints ('typst compile', 'typstyle --check') and a feedback loop (fail → 'typstyle --diff' → decide), plus a destructive-code guard ('Stop and ask the user when formatting would change untouched pre-existing code').	5 / 5
Progressive Disclosure	Sections are well-organized and references are signaled as one-level-deep links into docs/, but the referenced docs/ directory and files (e.g. docs/reference/syntax.md, docs/tutorial/writing-in-typst.md) do not exist in the bundle, so navigation is broken despite the intended structure.	3 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

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, concrete description that covers what the skill does and when to use it with explicit trigger terms and the .typ extension. Minor synonym coverage gaps keep trigger term quality just below the top anchor.

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' — with comprehensive coverage across generation, editing, troubleshooting, and Q&A.	5 / 5
Completeness	Explicitly answers both what ('Generate... edit and troubleshoot... answer... questions') and when ('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') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage including the '.typ' extension and natural task verbs ('creation, editing, debugging, compilation, formatting, template work, package usage'); a few natural synonyms a user might say (e.g. 'Typst templates' or 'render Typst') are absent.	4 / 5
Distinctiveness Conflict Risk	Typst-specific with the '.typ' extension and Typst-named triggers establish a clear niche with minimal conflict risk against other document/code skills.	5 / 5
	Total	19 / 20 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: 83d8783

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