Svg Cover Generator

Create polished, editable SVG cover artwork for reports, articles, slide decks, social cards, ebook covers, posters, and landing-page hero images. Use when a...

Security Scan

The skill's files, instructions, and tooling are consistent with generating and validating self-contained SVG covers and do not request unrelated credentials or perform suspicious network/actions.

Purpose & Capability

The name/description match the included templates, layout recipes, design rules, and a simple SVG validator. There are no unrelated binaries, credentials, or services required.

Instruction Scope

SKILL.md stays within the stated purpose: collecting a brief, following layout rules, producing an inline-styled SVG, and optionally writing the file and running the local validator. It does not instruct reading arbitrary system files, contacting external endpoints, or exfiltrating data.

Install Mechanism

No install spec is provided (instruction-only). The repo includes templates and a short Python validator; nothing is downloaded from external sources or installed automatically.

Credentials

No environment variables, credentials, or config paths are requested. The skill's needs are minimal and proportionate to producing/editing SVGs.

Persistence & Privilege

always is false and the skill does not request or modify other skills or global agent settings. It may be invoked autonomously (normal), but it has no broad privileges or persistence requirements.

Assessment

This skill appears coherent and low-risk for its purpose. A few practical points to consider before installing or running it: 1) The skill may write SVG files to paths you specify — only provide file paths you control and review files before overwriting important files. 2) The included validator (scripts/check_svg.py) parses the SVG file you point it at and prints structural errors; running it requires read access to the target file (expected behavior). 3) Templates reference font-family names but do not embed or fetch web fonts — if you need exact typography, embed fonts yourself. 4) The skill does not contact external endpoints or require secrets. If you want extra assurance, inspect the small validator script and template files locally (they are readable and short) before use.

Generate one self-contained SVG cover that is visually intentional, easy to edit, and ready to save as .svg.

Quick Flow

1. Confirm the target format, dimensions, text content, and mood.
2. Read design-rules.md and layout-recipes.md before composing.
3. Pick one layout recipe that matches the brief.
4. Write a complete SVG with inline styles and no external dependencies.
5. Validate the SVG structure before finishing.

Intake

If the user already gave a clear brief, do not over-question. Otherwise collect the minimum missing inputs:

• Title
• Optional subtitle or byline
• Intended use: report cover, social card, slide cover, poster, hero image
• Canvas size or aspect ratio
• Brand colors or visual mood
• Whether the output should feel corporate, editorial, playful, technical, minimal, or bold

Reasonable defaults:

• Use 1600x900 for general landscape covers.
• Use 1080x1350 for portrait social-style covers.
• Use 1080x1080 for square covers.
• Use a clean sans-serif fallback stack inside the SVG unless the user provided a font direction.

Composition Rules

• Prefer bold typography and a small number of strong shapes over busy illustration.
• Keep the title as the dominant element.
• Use 2-4 colors unless the brief asks for a richer palette.
• Use gradients, grids, bands, masks, or geometric clusters to create atmosphere.
• Keep all text editable as <text> unless the user explicitly asks for paths.
• Avoid embedded raster images unless the user explicitly provides one and wants it included.

Build Procedure

1. Choose a layout

Select a layout from layout-recipes.md that fits the brief.

2. Build the SVG

Always produce:

• An <svg> root with xmlns, width, height, and viewBox
• A background layer
• A content layer for title and supporting text
• One visual motif layer such as lines, circles, blocks, mesh-like gradients, or abstract geometry

Keep styles inline in a <style> block or on elements. Do not rely on external CSS, web fonts, or remote assets.

3. Make the output usable

• Escape XML-sensitive characters in text.
• Keep the hierarchy readable with grouping and brief comments when helpful.
• Ensure contrast is strong enough for the title to remain legible.
• Leave comfortable margins so text does not touch the canvas edge.

Validation

Before finishing, check:

• The file is valid XML-style SVG.
• viewBox matches the intended composition size.
• Required text from the brief is present.
• There are no external asset references.
• The artwork is self-contained and editable.

If the SVG is saved to a file, run:

python3 scripts/check_svg.py /path/to/file.svg

Output

When the user asked for the SVG itself, return the full SVG in a fenced svg block.

When the user asked for a file, write the SVG to the requested path and summarize:

• dimensions
• chosen layout
• palette
• validation result

Resources

• Use design-rules.md for visual and technical rules.
• Use layout-recipes.md for composition choices.
• Use assets/templates/ as starting points when a blank canvas would slow things down.
• Use scripts/check_svg.py to catch structural mistakes before handing off the file.