Skip to content
Back to skills

Svg Cleaner

ASecurity

Clean SVG files for UI usage. Use when asked to remove SVG comments, simplify SVG markup, or make icon color follow CSS via currentColor.

  • 2 stars
  • 0 votes
  • 0 copies
  • 7 views
  • Added September 9, 2026
toolsgoexpress

Works with

  • cli

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add skitsanos/ironcrew --skill svg-cleaner --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Svg Cleaner?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Svg Cleaner
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/skitsanos-svg-cleaner/badge)](https://www.skillsdirectory.com/skills/skitsanos-svg-cleaner)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: svg-cleaner
description: Clean SVG files for UI usage. Use when asked to remove SVG comments, simplify SVG markup, or make icon color follow CSS via currentColor.
disable-model-invocation: true
allowed-tools: Read Edit MultiEdit Write Grep
model: sonnet
---

# SVG Cleaner

Use this skill when the user wants an SVG cleaned up for application use, especially for icons that should inherit color from CSS.

Arguments:

- `$ARGUMENTS` may contain one or more SVG file paths, or a short instruction about the target SVGs.
- If no arguments are provided, inspect the current task context and ask for the SVG path only if it cannot be inferred safely.

Goals:

1. Remove SVG comments such as `<!-- ... -->`.
2. Make icon color follow CSS with `currentColor` where it is safe to do so.
3. Preserve rendering unless the user explicitly asks for a more aggressive cleanup.

Workflow:

1. Read the SVG file or files first.
2. Remove comments and obvious editor noise only when it is safe.
3. Inspect how color is applied:
   - If the SVG is effectively single-color, convert hardcoded `fill` and/or `stroke` colors to `currentColor`.
   - Keep `fill="none"` and `stroke="none"` unchanged.
   - Preserve `url(#...)` paints, gradients, masks, clip paths, filters, and other structural features.
   - Preserve multi-color artwork unless the user explicitly asks to flatten it into a single CSS-controlled color.
4. Prefer the smallest safe change:
   - If one shared color is used throughout, replacing repeated hardcoded colors with `currentColor` is preferred.
   - If a root-level `fill` or `stroke` can safely express the same result, that is acceptable.
   - Update inline `style` attributes when they are the only place color is defined.
5. Keep important SVG behavior intact:
   - Preserve `viewBox`.
   - Preserve geometry, transforms, `fill-rule`, `clip-rule`, and opacity-related attributes unless cleanup requires a targeted rewrite.
6. After editing, quickly re-read the result and check that no hardcoded color remains on elements that should now inherit from CSS.

Decision rules:

- Treat monochrome icons as good candidates for `currentColor`.
- Treat logos, illustrations, flags, gradients, and intentionally multi-color assets as not safe for automatic color unification.
- If safety is unclear, make the conservative cleanup only: remove comments and report why color conversion was skipped.

Output:

- Briefly state which SVG files were updated.
- State whether `currentColor` conversion was applied or intentionally skipped.
- Call out any remaining manual follow-up only if the SVG structure makes safe automation ambiguous.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.