og-image-from-template
Skill1 starsChanged 17 days agoMITView on GitHub
Use this skill when a post, page or case study is about to ship and it needs a social share image, and the firm already has a Figma template for them. Produces an exported OG image at the right dimensions, named and placed for the page's meta tags, with the title set to fit rather than truncated. Also use for "make the OG image", "social card for this post", "the preview looks broken when I share the link", "og:image".
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- morning-paper-outreachSkill
- client-activation-checkinSkill
- client-churn-autopsySkill
- client-win-backSkill
- late-payment-chaseSkill
- network-path-mappingSkill
- rate-increase-planSkill
- sales-call-debriefSkill
- weekly-funnel-reviewSkill
- buyer-readSkill
- punch-upSkill
- call-topic-miningSkill
- ceo-exec-assistantSkill
- weekly-site-and-ad-reportSkill
- icp-reviewSkill
- weekly-content-ideas-from-callsSkill
- client-performance-reviewSkill
- cold-email-sequenceSkill
- email-content-reviewerSkill
- scoring-analysis-and-distributionSkill
- delivery-audit-discovery-callSkill
- directionSkill
- rundownSkill
- source-checkSkill
- work-reviewSkill
- demandbird-exact-time-linkedin-postSkill
- kondo-owed-reply-sweepSkill
- linkedin-export-contact-importSkill
- mail-messages-contact-touchesSkill
- riverside-short-social-scheduleSkill
- youtube-transcript-panel-pullSkill
- email-voice-setupSkill
- upsell-opportunity-briefSkill
- ad-creative-content-strategySkill
- klaviyo-account-auditSkill
- facilitator-notesSkill
- local-prospectingSkill
- weekly-linkedin-postsSkill
- linkedin-watchlist-briefSkill
- pipeline-by-scriptSkill
- pre-session-flash-cardSkill
- write-in-the-owners-voiceSkill
- reddit-gtm-sprintSkill
- process-captureSkill
- sales-call-market-analyzerSkill
- linkedin-shoutout-postSkill
- plain-language-copy-checkSkill
- revenue-goal-funnel-mathSkill
- case-study-buildSkill
- cash-runway-forecastSkill
- client-profitability-readSkill
- client-proposalSkill
- content-briefSkill
- quarter-goal-filterSkill
- win-to-anglesSkill
- activity-incentive-sprintSkill
- candidate-interview-coachSkill
- client-list-stack-pitchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
Check the render before shipping, not after.
- Distinctive: line 41
MUST duplicate the template frame.
- Distinctive: line 42
MUST fill only the named content layers.
- Distinctive: line 43
MUST rewrite an overlong title rather than shrink the text or truncate it.
- Distinctive: line 44
MUST export at 1200x630 and keep the file under 300KB.
- Distinctive: line 45
MUST look at the rendered card before the page ships.
- Distinctive: line 46
NEVER detach a template instance to make content fit.
- Distinctive: line 47
NEVER put text the template did not plan for into a frame, including logos, badges and dates.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Applies when a page is ready to publish and needs its share image. Produces one exported image, correctly sized and named, from the firm's existing template rather than a new design each time.
The play
- Open the firm's OG template in Figma and duplicate the frame. Never start from a blank frame. The template exists so that every share image looks like it came from the same company, and the second a one-off is designed, that stops being true.
- Fill the template's named layers only: title, optional eyebrow or category, optional author. The layer names and what each accepts are in references/template-contract.md. Any layer not in that list is structure, not content, and is not touched.
- Fit the title rather than truncating it. Count characters before pasting, and if it overruns, rewrite it shorter. An OG title is not the page title and does not have to match it. Character budgets per size are in references/template-contract.md.
- Branch by what the page is:
- Blog post or article: title plus category eyebrow. No author unless the firm's template includes one by default.
- Case study: client name as the eyebrow, result as the title. The result is the thing worth sharing, not the client's name.
- Landing or service page: the page's promise, not its heading. Headings are written for people already on the page.
- Any page with a strong existing image: use it as the template's background layer at the template's own treatment, never raw. A raw photo behind white text fails on half of all feeds.
- Export at 1200x630 as PNG, or JPG when the image is photographic and the PNG lands over 300KB. Dimensions, naming and the file-size ceiling are in references/export-settings.md.
- Name the file after the page slug, not the title, and place it where the site expects images for that page type.
- Check the render before shipping, not after. Paste the live URL into a share-preview checker and look at the actual card. The checklist for what to look at is in references/export-settings.md.
What good looks like
- First thing I check that most people skip: the image at thumbnail size, which is how most people will see it. If the title is unreadable at 25% zoom, the design is wrong no matter how it looks in the editor.
- The mediocre version: the page's H1 pasted into the template at whatever length it happens to be, auto-shrunk to fit, exported at the wrong ratio, and never looked at again. It technically has an OG image.
- I know it is right when the card is legible at thumbnail size, the title is a sentence someone would click, and it is visibly from the same family as the last ten.
- Red flag: someone has detached the template instance to make something fit. That is a template problem to fix once, not a one-off to work around.
Rules
- MUST duplicate the template frame. Never design a one-off.
- MUST fill only the named content layers.
- MUST rewrite an overlong title rather than shrink the text or truncate it.
- MUST export at 1200x630 and keep the file under 300KB.
- MUST look at the rendered card before the page ships.
- NEVER detach a template instance to make content fit.
- NEVER put text the template did not plan for into a frame, including logos, badges and dates.
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
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.

