agentleFS
holaroluwaholaroluwa/outbound-skills/skills/offer-definer/SKILL.md

offer-definer

Skill0 starsChanged 47 days agoMITView on GitHub

Turn a rough offer and pricing into a sharp, conversion-ready offer, one sentence plus the outcome, the proof, the risk reversal, and the call to action. Use when the user is deciding what to actually pitch, says "what's our offer", "make this offer stronger", "package this", or is about to write outreach and needs a crisp offer to point at. Writes the offer into outreach-brief.md. A weak offer sinks even great copy, so use this before any copywriting skill.

2 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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

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

    Write into section 2 (Offer) of outreach-brief.md, the five parts clearly labelled.

    line 25

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

Offer Definer

A weak offer can't be rescued by good copy. This skill forces the offer into the shape that converts: a single clear promise, backed by proof, de-risked, with one obvious next step.

Input needed

  • What you're selling and roughly how it's priced.
  • Ideally the value props and pains from outreach-brief.md (read them first if present).

Method

Build the offer in five parts. Each must be specific and true:

  1. One sentence, what they get, for whom, in plain words.
  2. Outcome, the concrete result, with a number or timeframe if you have one.
  3. Proof, why they should believe it: a result, a name, a guarantee, a stat. No proof means a weak offer.
  4. Risk reversal, what removes the fear of saying yes: a trial, a guarantee, a pilot, no lock-in.
  5. CTA, the single, low-friction next step. One only.

Pressure-test it: would a skeptical buyer believe each line? If not, fix it or flag the missing proof rather than papering over it.

Output

Write into section 2 (Offer) of outreach-brief.md, the five parts clearly labelled. This becomes the spine every copywriting skill points to.

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.