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
- timscheuerai/content-vaulttheir own version, first seen Oct 15, 2026
- whyashthakker/agent-skills-marketingtheir own version, first seen Jun 21, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- timscheuerai/content-vault★ 38same name
- whyashthakker/agent-skills-marketing★ 15same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository54 other files it gives its agents.
- AGENTS.mdAGENTS.md
- context/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- context/CLAUDE.mdCLAUDE.md
- brand-reviewSkill
- brand-systemSkill
- capture-contextSkill
- content-strategySkill
- crm-presync-checkSkill
- flowchartSkill
- graphics-designerSkill
- gtm-startSkill
- launch-videoSkill
- lead-sourcingSkill
- linkedin-copywriterSkill
- long-formSkill
- manim-videoSkill
- newsletter-writerSkill
- outbound-copywriterSkill
- oxygen-dedupeSkill
- oxygen-deliverabilitySkill
- oxygen-diagnosticsSkill
- oxygen-email-infraSkill
- oxygen-gtmSkill
- oxygen-knowledgeSkill
- oxygen-linkedin-marketingSkill
- oxygen-quickstartSkill
- oxygen-recipesSkill
- oxygen-sequencer-enrollSkill
- oxygen-sequencerSkill
- oxygen-table-tidySkill
- oxygen-uniboxSkill
- oxygen-workflow-authoringSkill
- personalize-ai-columnSkill
- qmdSkill
- repurpose-contentSkill
- researcherSkill
- setup-workspaceSkill
- shorts-audioSkill
- shorts-cutSkill
- shorts-editSkill
- shorts-motionSkill
- shorts-qaSkill
- signals-sweepSkill
- spin-tagsSkill
- split-test-designerSkill
- video-useSkill
- voice-calibrationSkill
- week-postsSkill
- x-copywriterSkill
- youtube-descriptionSkill
- youtube-publisherSkill
- youtube-scriptSkill
- youtube-thumbnailSkill
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
- Very specific: line 8
Read the user's audience, offer and cleared proof in company/private/ and context/.
- Distinctive: line 18
Keep required tools, accounts, costs and unsupported steps visible next to setup.
≈ “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.
Files
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:
- An editable blank starting point.
- A complete worked example, explicitly labeled synthetic when appropriate.
- Instructions that get a new reader to one useful result.
- 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.
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
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.

