# Serval Svg

> Use this skill when the user wants a direct, product-facing answer about what serval-svg supports: supported SVG tags, supported attributes, platform coverage, or whether a concrete SVG fits the published support surface, without exposing repository internals.

- Skill: `lynx-family/serval-svg` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add lynx-family/serval-svg`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lynx-family/serval-svg/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lynx-family (https://skillmd.com/u/lynx-family)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lynx-family/serval-svg

---


# Serval SVG

## Overview

This is the public support-answer skill for `serval-svg`.

Its job is to answer support questions directly, accurately, and without
depending on internal implementation detail.

## Canonical Inputs

Load these first:

- `../../docs/support-matrix.json`
- [references/response-guidelines.md](references/response-guidelines.md)

For a concrete SVG file, use the public analysis mode:

```bash
python3 svg/tools/svg_support_audit.py analyze --svg-file path/to/input.svg --platform all
```

## Scope

This skill should answer:

- whether a tag is `supported`, `partial`, or `unsupported`
- which attributes are supported for that tag
- which attributes are only partially supported
- which attributes are unsupported
- whether support changes by backend
- whether a concrete SVG stays inside the published support surface

## Response Rules

- Start from `support-matrix.json`.
- Do not load or cite `deepwiki.md` for normal support answers.
- Do not explain parser internals, render internals, or backend source files.
- Treat unlisted tags and unlisted attributes as unsupported unless the public
  contract says otherwise.
- If support is partial, say so plainly.
- If platform support differs, say so plainly.
- Keep the answer direct and product-facing.

## Escalation

Escalate to `serval-svg-expert` when the user wants:

- to know why support behaves a certain way
- source-file evidence
- a repository audit
- refreshed support artifacts
- feature-development guidance
- implementation planning or code changes

