agentleFS
HenryQWHenryQW/skills/og-image/SKILL.md

og-image

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Generate a restrained branded 1200×630 Open Graph PNG from a personal avatar, secondary product mark, title, tagline, owner label, and site URL. Use when creating, replacing, or polishing an og.png or social preview image for a website.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create one legible social card with clear identity and minimal copy.

    line 8
  2. Distinctive:

    Keep the hierarchy fixed:

    line 15
  3. Distinctive:

    Keep the title under 22 characters and tagline under 46 characters.

    line 21
  4. Distinctive:

    Create a temporary JSON config with absolute paths:

    line 24
  5. Distinctive:

    Run the bundled renderer from the target project root:

    line 47
  6. Distinctive:

    Keep the editable source assets.

    line 63

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

OG Image

Create one legible social card with clear identity and minimal copy. Reuse the site's existing avatar, logo, colors, and wording; do not invent branding.

Workflow

  1. Inspect current metadata, favicon/avatar sources, product logo, and theme colors. Prefer the highest-resolution square avatar source over .ico.
  2. Keep the hierarchy fixed:
    • personal avatar and owner in the top-left;
    • site URL in the top-right;
    • title and one tagline as the main copy;
    • product mark as the secondary visual;
    • one short accent rule and, when useful, one brief footer label.
  3. Keep the title under 22 characters and tagline under 46 characters. If copy exceeds either limit, shorten it with the user or make a deliberate custom layout instead of silently shrinking text.
  4. Create a temporary JSON config with absolute paths:

    {
      "title": "Henry Pi Harness",
      "tagline": "Built on Pi. Tuned by Henry.",
      "owner": "Henry Wang",
      "descriptor": "Personal Pi harness",
      "site": "pi.henry.wang",
      "footer": "Extensions for Pi",
      "avatar": "/absolute/path/avatar.png",
      "mark": "/absolute/path/product-logo.svg",
      "output": "/absolute/path/public/og.png",
      "colors": {
        "background": "#101828",
        "foreground": "#f0eee9",
        "muted": "#cdd1d9",
        "border": "#394152",
        "accent": "#1d4ed8"
      }
    }
  5. Run the bundled renderer from the target project root:

    node "$SKILL_DIR/scripts/render-og.mjs" /tmp/og-image.json

    The target project must already provide sharp. Reuse it when present. Do not add a dependency without approval; use the project's existing image renderer when Sharp is unavailable.

  6. Open the PNG and inspect it at full size. Check safe margins, text clipping, avatar clarity, mark prominence, and contrast. Revise once only when a visible issue exists.
  7. Wire the absolute public URL into og:image and twitter:image, including width 1200, height 630, and useful alt text. Build the site and inspect generated metadata.

Keep the editable source assets. Never use an SVG directly as the social image; render a PNG for broad crawler support.

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.