skills/slides-visuals/creating-svg-illustrations/SKILL.md
Create, revise, embed, or troubleshoot accessible SVG diagrams and illustrations for slide decks, documents, and other static artifacts, with portable sizing, layout, style, and validation guidance.
npx skillsauth add narumiruna/agent-skills creating-svg-illustrationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Start with references/core-rules.md; load only the extra detail the artifact needs.
| Need | Read or use |
| --- | --- |
| Canvas, style, text, accessibility, validation | references/core-rules.md |
| Reusable compositions | references/pattern-examples.md |
| Marp embedding | references/embedding.md |
| Rendering failures | references/troubleshooting.md |
| Known-good deck example | assets/examples/with-diagrams.md |
viewBox, explicit text styles, consistent geometry, and SVG title/description where the visual carries meaning. When embedding, also provide descriptive host-level alt text or an adjacent semantic equivalent as required by references/embedding.md; internal SVG metadata alone is not sufficient.svglint when available, then open or embed the SVG in the target artifact and inspect clipping, scaling, contrast, text, and relative paths.Use slide-authoring or color guidance only when the request also requires it. Do not claim visual inspection when only source validation ran, and do not commit or publish the artifact unless requested.
development
Score or compare one or more agent skills across trigger clarity, workflow actionability, safety boundaries, verification rigor, incremental knowledge value, and leanness. Use only when the user explicitly asks for ratings, numerical quality scores, rubric-based scorecards, or scored comparisons; use creating-agent-skills for unscored reviews or revisions.
development
Assess or improve an existing codebase's architecture when the user asks about module boundaries, coupling, scattered ownership, testability, change locality, deep modules, seams, or behavior-preserving structural refactoring. Use for cross-module design rather than ordinary diff review or a confirmed edge-case bug fix.
development
Perform read-only security audits, vulnerability assessments, or threat-focused reviews of diffs, pull requests, code paths, or explicitly scoped repositories when security is the primary objective or acceptance criterion. Use reviewing-code for ordinary review with baseline security coverage and hardening-code-paths for fixing confirmed findings.
development
Run iterative multi-reviewer panels over a code diff, verify their findings, apply explicitly authorized fixes, and re-review the updated change until it passes or reaches a stopping condition. Use when the user asks for a panel loop, multi-model code-review consensus, or a review-fix-re-review cycle.