Index of every page on this site: llms.txt
All skills
haorantang97 avatar

/create-visual-assets

@d6c47b1
by Lab 305haorantang97/labkit8 stars
Run it yourself

Create or revise a repository's hero, theme variants, social preview and badge row. Use for repository visual assets or a README renovation; apply the supplied reference and product identity. Use an appropriate image tool for raster illustration.

  • 1 file
  • 3.3 KB
  • License
  • Updated last month
  • GitHub
Use this Skill: https://skilld.dev/gh/haorantang97/labkit/create-visual-assets

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈67 tokens for metadata: the name and description. ≈752 when used: this file.

Description uses 3.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈269 characters, or 3.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Repository visual assets

Read the repository presentation standard before designing. Inspect the repository identity and its existing rendered assets, not just filenames.

Resolve style from the user's reference or assets/STYLE.md. A supplied reference is already a style choice. If the user asks for the same style, preserve its layout principles, palette, typography and spacing while creating a distinct mark; do not duplicate its logo or signature silhouette; change the target name and factual copy. Do not reinterpret a same-style request as permission to invent a different visual identity. Ask only for a consequential missing preference. With no reference, choose a restrained product-specific direction and record it.

Design a visual motif that explains the repository: a collection uses its own name and represents its independent tools. Internal module names stay inside their component. Match palette, typography and supporting graphics across the page. Do not default to a copied blank rectangle with a new title.

Produce light and dark SVGs for vector compositions. Preserve established asset paths where practical; otherwise update every consumer. Use a viewBox, accessible title/description, deliberate spacing and readable text. Choose dimensions for the composition and inspect scaling rather than enforcing a fixed template size. For photos or complex raster artwork, use the relevant image-generation/editing capability.

Embed theme variants through picture/source plus img fallback, with descriptive alt text and a sensible display width. Store presentation assets at the repository level, outside the installable skill. Record the motif, colors, type choices, references and dimensions in the repository's assets/STYLE.md; keep any saved generation prompts with those presentation files. Follow the installation boundary when arranging them.

When social sharing is in scope, create a dedicated 1280 × 640 PNG with the same identity and a legible title at thumbnail size. Verify separately whether GitHub's social-preview setting actually uses it.

Use a small badge row tied to real facts. CI links must name their actual coverage. License badges must match the applicable license; release badges need a real tag/release. Avoid empty links, static update dates that imply activity, unsupported popularity and inflated module counts.

Render and inspect both themes at README width and a narrow width. Read the words inside the artwork, check clipping/contrast, then inspect the hero in the assembled page. Search for obsolete parent names and template tokens. Report asset creation, visual inspection and remote configuration separately.

Use the latest approved artwork as the implementation source. A single intentionally dark photographic hero may serve both page themes when approved and visually checked; do not auto-invert it or replace it with a vector approximation.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at d6c47b1. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated last month

README badge

README badge for haorantang97/labkit/create-visual-assets