agentleFS
timscheueraitimscheuerai/gtm-architecture-template/.agents/skills/lead-magnet-creator/SKILL.md

lead-magnet-creator

Skill2 starsChanged 2 months agoMITView on GitHub

Build a complete, reusable lead magnet with a clear reader outcome, worked example, editable starting point and tested delivery path.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Read the user's audience, offer and cleared proof in company/private/ and context/.

    line 8
  2. Distinctive:

    Keep required tools, accounts, costs and unsupported steps visible next to setup.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Build an asset people can use

Read the user's audience, offer and cleared proof in company/private/ and context/. Start with the reader's next job: a decision, a calculation, a configured workflow or a finished draft. Write the asset's promise in one sentence with a concrete output.

Choose the format that does that job: calculator for repeated decisions, template for recurring work, repository for executable/configurable workflows, checklist for a bounded inspection, guide for a method needing explanation. Do not turn every request into a Notion page.

Build four things:

  1. An editable blank starting point.
  2. A complete worked example, explicitly labeled synthetic when appropriate.
  3. Instructions that get a new reader to one useful result.
  4. A way to check the result, including known failure cases.

Keep required tools, accounts, costs and unsupported steps visible next to setup. The free asset must fulfill its headline without requiring a sales call. Put optional extensions after the first win. Verify every promised file and link; remove references to scripts that are not bundled.

For a repo, test a clean checkout and inspect generated outputs. For a document, read the export; for a sheet, check formulas and boundaries. Evaluate whether a reader can use it from the artifact alone. Do not claim a preview or scaffold is an operational integration.

Deliver the actual asset and a short launch brief: intended reader, problem, promise, included pieces, quick win, prerequisites and stable URL if published. Add a relevant, optional next step. Save to external boards or publish only within the user's request. Use linkedin-copywriter or x-copywriter for a separately requested launch post.

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.