agentleFS
bestdeejay-designbestdeejay-design/agent-skills/skills/repo-readme-assets/SKILL.md

repo-readme-assets

Skill6 starsChanged 3 months agoMITView on GitHub

README.md (EN) + localized mirror + local animated SVG header/footer for a repository. Generates assets/header.svg and assets/footer.svg with SMIL animation (4 presets: default/minimal/dark-first/monochrome), zero external services. Scripts: generate_assets.py, validate_svg.py, extract_context.py. Triggers: 'readme header', 'animated svg', 'waving svg', 'svg banner', 'readme assets', 'readme visual', 'smil animation', 'repo header', 'readme footer', 'readme generator', 'update readme', 'readme badges'.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to create or update a repository README and its visual header/footer with local animated SVG assets.

    line 14
  2. Distinctive:

    Avoid "AI-slop" wording: "seamless", "unleash", "empower", emoji overload.

    line 70
  3. Distinctive:

    Prefer relative links to repo files (absolute links break in clones).

    line 71
  4. Very specific:

    Do not generate without confirming USERNAME when it is not obvious.

    line 111
  5. Very specific:

    Do not overwrite existing .svg without an explicit request.

    line 112
  6. Distinctive:

    Do not touch README content between header and footer.

    line 113
  7. Distinctive:

    Do not add header/footer if they already exist (only on request).

    line 114
  8. Very specific:

    Do not use to change repository settings or legal files.

    line 119

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Repo Readme Assets — README + animated SVG header/footer

Use this skill to create or update a repository README and its visual header/footer with local animated SVG assets. Zero external services: no capsule-render, no shields generators, no URL banners. Animation is SMIL only (<animate>, <animateTransform>) so it works inside <img> on GitHub without scripts or network requests.

When to use

  • A repository needs a README with a header/footer banner (local animated SVG).
  • Major change happened and the README must reflect the current project state.
  • User asks for "readme header", "animated svg", "waving svg", "svg banner", "readme assets", "readme visual", "smil animation".

Do NOT use

  • README is already current and the user did not request changes — do not "improve".
  • A single tiny fix (e.g. one badge) — edit directly, no skill needed.
  • For legal/community files (LICENSE, CONTRIBUTING, SECURITY) — use repo-community-files.
  • For description/topics/Pages/community-health — use repo-metadata-health.
  • For the social preview PNG — use repo-social-preview.

Files

  • SKILL.md — this file
  • scripts/generate_assets.py — deterministic generation of assets/header.svg + assets/footer.svg
  • scripts/extract_context.py — auto-detect name/desc/stack/colors/username from git remote
  • scripts/validate_svg.py — validate SVG against skill rules (SMIL, mask, morphing)
  • references/svg-animation.md — full SVG animation spec + header/footer templates
  • references/svg-presets.md — the four presets
  • references/color-tokens.md — detected values (USERNAME/PROJECT_NAME/COLD/WARM)
  • references/canonical-patterns.md — canonical references and gaps

Scripts

ScriptPurposeCall
generate_assets.pyDeterministic assets/header.svg + assets/footer.svg (presets: --preset default|minimal|dark-first|monochrome)python3 scripts/generate_assets.py --name X --desc Y --user Z --cold #HEX --warm #HEX [--preset default]
extract_context.pyAuto-detect generation context from git remotepython3 scripts/extract_context.py [--path DIR] [--gh-repo owner/repo] [--text]
validate_svg.pyValidate SVG rules (SMIL, mask, d-path morphing)python3 scripts/validate_svg.py assets/

Reports are JSON; exit codes 0/1 (CI-friendly).

README — required elements

  1. Header: project name, one-line description, live badge links (3–6, one style).
  2. Status block: current check numbers (typecheck/contract/integration).
  3. Quick start: install, infra, run.
  4. Repo structure: full tree (include new dirs/services).
  5. Stack/events/checks sections — kept in sync with real code.
  6. GitHub Pages link (if enabled): https://<user>.github.io/<repo>/ + homepage in About.
  7. Language switcher: **🌐 Versions:** [English](README.md) · [Русский](README.ru.md) · [Website](…).
  8. Hashtags/keywords for search (description + topics).

Rules:

  • README.md is always English (GitHub international standard).
  • README.<lang>.md is a localized mirror: propagate English changes 1:1 (headings, numbers, statuses).
  • Diverged localizations are a typical anti-pattern — run a programmatic heading-diff before release.
  • Avoid "AI-slop" wording: "seamless", "unleash", "empower", emoji overload.
  • Prefer relative links to repo files (absolute links break in clones).
  • GitHub auto-generates TOC — no manual table of contents needed.

Animated SVG header/footer

By default each repo gets assets/header.svg (start of README) and assets/footer.svg (end of README), required in both language versions.

Principle: zero external services. Animation is SMIL only.

Key techniques: "background wave" effect (a black wave in <mask> cuts color → page background shows through), d-path morphing across 4 frames (crest Q+T, identical command sequence in every frame), 30% wave desync, a highlight pass once ~16s, a twinkling speck in the footer.

  • Full spec + templates → references/svg-animation.md
  • Detected values → references/color-tokens.md
  • Presets → references/svg-presets.md

Preset choice: default (animated gradient) by default; minimal (static gradient, no waves) for docs/stable tools; dark-first (deep dark backdrop, GitHub dark theme); monochrome (b/w, no SMIL) for books/print/specs. Ask the user, else take default.

How to generate (recommended path)

By script (deterministic, then validate):

python3 scripts/generate_assets.py \
  --name "Project Name" --desc "Short description" --user "username" \
  --cold "#0ABAB5" --warm "#F64A8A"
python3 scripts/validate_svg.py assets/        # expect: all passed

Manually (when the script is unavailable): read references/svg-animation.md, substitute COLD, WARM, PROJECT_NAME, PROJECT_DESC, FONTCOLOR, USERNAME into the templates, create assets/, add the links (see "Insert into README.md" in the reference).

Generation safety

  • Do not generate without confirming USERNAME when it is not obvious.
  • Do not overwrite existing .svg without an explicit request.
  • Do not touch README content between header and footer.
  • Do not add header/footer if they already exist (only on request).
  • SVG: no <script>, no base64, SMIL only; mask with a white <rect> covering the canvas.

Boundaries

  • Do not use to change repository settings or legal files; use repo-metadata-health or repo-community-files.

Evidence and completion gate

Run the documented command against the user’s actual input. Report the command, exit status, files changed or produced, and relevant stdout/stderr. Separate blocked or pre-existing failures from failures introduced by the current work. Do not call the result complete when the script was only described or when an artifact was not reopened and checked.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.