Skip to content

sergebulaev/facebook-skills / .codex-marketplace/facebook-skills

facebook-marketing

Verified

Plan, draft, audit, and publish posts for a Facebook Page. Use when the user wants to write a short punchy Page post or a longer story post, remove AI tells from a draft, reverse-engineer the hook from a high-share Page post, draft replies to comments on their Page, or plan a week of Facebook Page content. Page posts publish via the Publora API. User provides notes or a Facebook Page post URL, the skill drafts, the user approves, then it publishes.

references/story-bank.md

View on GitHub
# Story Bank

The raw material your Facebook posts are made of: what you have actually done, in
numbers, with names and dates. The Voice Profile holds *how you sound*. This holds
*what you have to say*.

Every writing skill in this bundle reads it before drafting, so it stops asking you
for "a specific number or moment" on every single request and starts drawing from
what you already told it once.

On a Facebook Page the sections that earn the most are Recurring stories and
Scars: the audience is closer to you than on any other platform here, and
reach follows what people comment on, which is almost always a story about a
person rather than a claim about a market.

> **Keep this out of git.** It holds career detail, figures, failures and named
> people. It is a file in this repository, so a push carries it wherever you push,
> a public fork included. Add `references/story-bank.md` to your `.gitignore`
> before you fill it, or keep the filled copy outside the repo. Nothing here is
> sent to us or to any service; git is the only way it travels.

Fill it by running `fb-humanizer --mode interview`, which interviews you and writes
this file. You can also edit it by hand at any time; the skill reads whatever is here.

## Status

- filled: no
- updated: (date)
- sessions: (how many interviews have contributed)

---

## 1. Timeline

Where you have worked and what changed at each stop. Dates matter: "March 2024"
beats "last year", because a post can anchor on it. A Facebook audience often
knows you personally, so the history is context they already half-have.

- (...)

## 2. Receipts

The numbers you can state without checking. This is the section drafts reach for
most, because one odd-precision figure with a named referent is the single
strongest signal that a human wrote the post.

Good: "cut deploy time from 22 minutes to 9, team of four, Q2 2025".
Useless: "improved efficiency significantly".

- (number, what it measures, when, who or what it belongs to)

## 3. Shipped

Things that exist because you worked on them. Products, migrations, hires, papers,
events, rescues.

- (what it was, your part in it, what it cost or returned)

## 4. Turning points

The moments where you changed your mind or the plan changed under you. These carry
posts better than successes do, and they are the hardest to invent.

- (what happened, what you believed before, what you believe now)

## 5. Scars

What went wrong and what it taught you. Kept separate from turning points because
the shape differs: a scar is a cost you paid, not a view you revised.

- (what broke, the real cost, what you do differently)

## 6. Positions

Opinions you would defend in a room that disagreed. A position with no cost to
holding it is not a position; note what holding it costs you.

- (the claim, who disagrees, why you hold it anyway)

## 7. Recurring stories

The three or four you already tell out loud, at dinner or in interviews. They are
proven: you know they land. Write them here before a draft dulls them.

- (the story in two lines, and the point it makes)

## 8. Names you can use

People, companies, tools and places you are free to name in public, and the ones
you are not. Drafts stay vague when they do not know which is which.

- Free to name: (...)
- Never name: (...)
- Ask first: (...)

## 9. Off limits

Subjects that stay out of posts regardless of how well they would perform: active
deals, litigation, health, other people's business, anything under NDA.

- (...)


---

## How drafts use this

- A draft needs a concrete detail: it takes one from **Receipts** or **Shipped**
  rather than asking you mid-session.
- A hook needs a reversal or a confession: **Turning points** and **Scars** are
  where those live.
- A post needs an argument: **Positions** supplies the claim and the opposition.
- Anything a draft cannot source from here, it asks about or leaves out. It does
  not invent a number. If you see an unfamiliar figure in a draft, that is a bug
  worth reporting.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall