svg

Author and edit `.svg` files in a Grida editor session — live-canvas binding, SVG output style, and parse-error recovery. Use when creating or modifying an SVG document.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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.

A lean, actionable, well-structured instruction skill that assumes Claude's competence and includes a parse-error feedback loop. Slight redundancy in the presentation guidance and prose-instead-of-numbered-checklist workflow keep it just under the ceiling on three dimensions.

Suggestions

Consolidate the repeated surface_open "do not reopen / do not retry / not required before" bullets into a single concise rule to remove redundancy.

Present the presentation workflow as a short numbered sequence with an explicit validation checkpoint (e.g. parse-error check) between phases to lift workflow clarity.

Show one complete `surface_open` call with its path argument so the primary command is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is dense and directive with no concept re-explanation (e.g. it never explains what SVG/Grida are), but the "Show the result" section repeats the surface_open guidance across several bullets, which could be tightened; hence below the lean 5 anchor.	4 / 5
Actionability	Concrete tool names (`surface_open`, `surface_list_open`, `edit_file` reason="parse_error") and a specific path example (`/poster.svg`) make the guidance executable, but calls are named rather than shown in full copy-paste form, leaving minor gaps.	4 / 5
Workflow Clarity	A clear sequence is given (write a valid first frame → `surface_open` → refine) with an explicit parse-error feedback loop ("Re-read and fix"), but the workflow is bulleted prose rather than a numbered checklist with explicit validation checkpoints between phases.	4 / 5
Progressive Disclosure	This is a sub-50-line single-purpose skill with no bundle files and no need for external references; its well-organized sections (intro, "Show the result", "SVG style") satisfy the simple-skill exception for a top score.	5 / 5
	Total	17 / 20 Passed

Description

87%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, third-person description that concretely names both capabilities and a clear use-trigger within a well-scoped niche. Minor keyword-synonym gaps keep trigger term quality and specificity just below the ceiling.

Dimension	Reasoning	Score
Specificity	"Author and edit `.svg` files" plus "live-canvas binding, SVG output style, and parse-error recovery" lists several concrete capabilities; not a 5 because only two verbs (author/edit) anchor the actions.	4 / 5
Completeness	It explicitly states what ("Author and edit `.svg` files in a Grida editor session — live-canvas binding, SVG output style, and parse-error recovery") and when ("Use when creating or modifying an SVG document") with concrete trigger phrasing.	5 / 5
Trigger Term Quality	"`.svg` files", "SVG document", and "SVG output" give good keyword coverage including the file extension, but synonyms like "vector graphics" are absent so it is not comprehensive.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply defined — SVG authoring/editing within a Grida editor session — so it is clearly distinguishable and unlikely to trigger for unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: gridaco/grida
Path: skills/svg/SKILL.md
Commit: 8ef5e53

Reviewed: about 11 hours 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.