OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add charlie947/social-media-skills --skill graphic-designer
Create LinkedIn post graphics. Decides between an HTML/CSS structured graphic or an AI-generated infographic based on the post content. Use this skill whenever the user says "design a graphic", "create a visual", "make an image", "graphic for my post", "LinkedIn image", or wants any visual content to pair with a LinkedIn post. Also trigger when the user finishes writing a post and wants a matching graphic.
npx skills add charlie947/social-media-skills --skill graphic-designer
AskUserQuestion examples describe the questions, not a required API: use an available question tool within its limits, or ask in chat. Reuse answers and source material already supplied.about-me.md, voice.md and relevant brand files before personalised work. Confirm the intended author if files conflict or contain starter defaults. Ask for missing facts or run voice-builder; never inherit the maintainer's identity, accounts or private files.references/ relative to this skill folder. For an explicitly requested profile refresh, read and update the canonical about-me.md, voice.md or newsletter-voice.md in place, preserving unrelated user facts and rules. Consumers must reread those canonical files. Use a new filename only for new deliverables that would collide with unrelated existing files. Installation alone never starts an interview or writes files. Do not write persistent learnings unless requested.This skill's image prompts are prompt-ready, not generated or visually reviewed assets. Keep its named Gemini workflow unless the user requests another generator. A missing image service does not block writing a prompt. When images are supplied or generated, open and inspect each export at full size and feed size (about 360px wide, 320px for thumbnails). Check exact copy, dimensions, clipping, legibility, brand colours, font appearance, logos and reference fidelity. Fix and re-inspect failed exports. Record any unavailable export or inspection as pending. An image prompt or raster export is not an editable design file.
When this skill triggers, go straight to Step 1. Do not summarise. Do not explain options. Start immediately.
Use the supplied post or exact file named by the user. If only project drafts exist, confirm which one is intended before using it. Otherwise say:
Paste the post you want a graphic for.
Wait for the post, then call AskUserQuestion:
If "You decide": analyse the post. If it contains numbered steps, frameworks, comparisons, or data tables, go Path A (HTML/CSS). If it recaps a workflow, shares tips, teaches a concept, or tells a story, go Path B (image prompt) and pick whichever style fits better.
Design constraints:
Single self-contained HTML file with inline CSS. Include viewport meta tag.
Extract the core framework or steps from the post. Do not copy the full post. Distil into:
Save the HTML and export a PNG using the available browser screenshot or existing local renderer. Wait for fonts and images to load. Open the actual PNG at full resolution and at 360px feed width; inspect headline, every item, clipping, contrast, fonts and attribution. Fix the HTML and re-export until those checks pass. Preserve the editable HTML alongside the inspected PNG. If browser/render access is unavailable, return the HTML as render pending, name the missing capability and give the user the browser screenshot step. Never call unrendered HTML visually verified.
The graphic must recap the post content visually. It is not an abstract illustration or stock photo. It summarises the key information from the post in a visual format the reader can scan.
First, extract the content for the infographic from the post:
Then build the prompt based on the chosen style.
Use this prompt template. Fill in the content sections from the post.
Ask the user for brand colours if not already known. If about-me.md exists, check there first.
Output the complete prompt in a code block. Tell the user:
Paste this into Gemini or your image generator. The prompt is ready to go.
Report the actual state: HTML render pending, HTML + inspected PNG, or Gemini prompt-ready. Link the files that actually exist. List any unresolved visual defects. Post scoring reviews copy and does not substitute for image inspection.
Generate a single image of a physical, hand-drawn infographic on a large whiteboard or notebook page.
Crucial Style Instructions (Read First):
Medium: The image must look like a photograph of a real whiteboard or large paper notepad.
Texture: All elements must look created by hand using colored marker pens (black, blue, red, green) and highlighters (yellow/orange). Lines should be slightly imperfect, wobbly, and have the texture of ink on a surface.
No Digital Fonts: All text, headings, and bullet points must appear handwritten or hand-printed in marker pen.
Layout: Structure the 1080x1350 image as follows:
TITLE (large, bold marker, top of page):
[Insert headline from the post]
CONTENT (hand-drawn sections with marker pen):
[Insert 3 to 6 key points, each as a short hand-written line with a bullet, number, or small icon drawn next to it]
[If there are stats or numbers, draw them large with a circle or box around them]
Use multi-colored markers for emphasis. Keep text large and legible. Make everything look hand-drawn with slight imperfections. Make it look like a photograph of an actual notebook page.
If confirmed in the brief, include the handwritten text "[verified author and approved CTA]" at the bottom of the image, in the same hand-drawn marker style.Generate a professional infographic image at 1080x1350 pixels.
Style: Clean, modern, editorial. Flat design with sharp edges and strong typography. No 3D effects, no gradients, no stock photos.
Colour palette:
- Background: [primary brand colour or dark neutral]
- Text: [white or high-contrast colour]
- Accent: [secondary brand colour]
Layout:
HEADLINE (top, large bold text):
[Insert headline from the post]
BODY (structured sections, each with an icon or number):
[Insert 3 to 6 key points as short lines, each with a visual marker: numbered circle, checkmark, or simple icon]
[If there are stats, display them as large feature numbers with a label underneath]
FOOTER:
[Author name from about-me.md] | [CTA or tagline if appropriate]
Keep text large and scannable. Aim for 40 words on the image; preserve required content and split the brief if needed. No decorative borders. No watermarks. No logos unless the user provides one.