agentleFS
Sign inStart free
ramkesh430ramkesh430/facebook-agent-skill/skills/fb-photo/SKILL.md

fb-photo

Skill1 starsChanged 16 days agoMITView on GitHub

Plan and write Facebook photo posts and multi-photo albums - which image leads, the order, text overlays, captions per photo, alt text and export sizes. Use when the user has photos to post, wants an album, a "swipe" multi-image post, a product showcase, an event recap, or a before/after.

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. Very specific:

    Read ~/.claude/facebook/voice.md.

    line 17
  2. Distinctive:

    One photo: when there's one moment worth stopping for.

    line 22
  3. Distinctive:

    If text overlay is needed: 6 words max, high contrast, large.

    line 34
  4. Distinctive:

    Keep key content away from edges.

    line 51
  5. Distinctive:

    If the user wants files made (resizes, overlays), produce them with an image library in the workspace and keep originals untouched.

    line 53
  6. Very specific:

    Write the post text with /fb-post (Job A: the photo carries the hook).

    line 58
  7. Distinctive:

    No engagement bait ("which one?

    line 68
  8. Very specific:

    Run all text through /fb-human.

    line 69

≈ “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

fb-photo

Photos are still Facebook's most shareable format for local businesses, families and events. The first image decides whether the rest get seen.

Before you start

Read ~/.claude/facebook/voice.md. Ask what the photos are (or look at them if attached), and what the post is for: sell, show proof, recap, or tell a story.

Single photo vs multi-photo

  • One photo when there's one moment worth stopping for.
  • 2-5 photos (grid layout) when the set tells a story: before/after, process, a product range. The first photo is the cover and is shown largest.
  • Album for event recaps or catalogues people will browse. Albums are for browsing, not for reach.

The cover photo of the post

It does the job a hook does:

  • A face or hands doing something, or the finished result. Not a logo.
  • One clear subject, readable on a phone at thumbnail size.
  • If text overlay is needed: 6 words max, high contrast, large. Facebook's audience skews older; size the text for them.
  • Real photos beat stock. Stock reads as an ad and gets scrolled like one.

Order for a multi-photo post

1  the result or the most surprising image
2  the context (where, who)
3-4 the process or details
5  the people (team, customer with permission) or the call to action image

Sizes

  • Feed photo: 1080 x 1350 (4:5) takes the most screen on mobile. 1080 x 1080 is safe.
  • Multi-photo grid: keep all images the same ratio, or Facebook crops unpredictably.
  • Keep key content away from edges; previews crop.

If the user wants files made (resizes, overlays), produce them with an image library in the workspace and keep originals untouched.

Text

Write the post text with /fb-post (Job A: the photo carries the hook). For albums, also write a one-line caption per photo; captions on individual photos are what people read while browsing.

Alt text for every photo: what's in it, in one plain sentence.

Rules

  • Permission for every identifiable customer or child in a photo. Ask.
  • Never edit a result photo to look better than the real result.
  • No engagement bait ("which one? react ❤️ or 😮").
  • Run all text through /fb-human. Nothing is posted; the user posts it.

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.

Check your setup, free