---
name: lead-magnets
description: Designs a useful downloadable resource and a specific request-to-delivery-to-value pilot. Use when planning lead magnets, gated guides, checklists, resource giveaways, or comment-to-get-a-resource campaigns.
license: MIT
disable-model-invocation: true
---

# Lead magnets

Deliver a complete useful artifact and measure what people do with it. An email address or a keyword comment is not yet demand for the paid product.

Run `node scripts/run-state-check.js lead-magnets`. Requires Product truth, ICP hypothesis, Diagnosis, and Channel bet. A calculator or interactive utility belongs in `free-tools`; this skill covers guides, checklists, templates, datasets, and worked examples.

Read [references/resource-pilot.md](references/resource-pilot.md). Use [assets/play-brief.md](assets/play-brief.md) when a reusable handoff helps; fill only fields that matter to this pilot.

## Process

1. Choose one job the audience already needs to complete, backed by inspected questions or customer evidence. Define the artifact's useful result before deciding whether to gate it.
2. Build the content outline and one fully worked sample using real supported facts or explicitly synthetic inputs. State limitations and the natural paid next job. Do not promise a resource that does not exist.
3. Choose access: public link, optional save/update request, or an explicit artifact request. Ask only for information needed to fulfill that promise. Compare likely friction with buyer relevance rather than maximizing form fields.
4. If using a comment keyword or request, separate requesters from likers and general engagers. A request to receive a guide does not imply agreement to a sales sequence. Draft the exact fulfillment message and the boundary on subsequent contact.
5. Specify the placement in the chosen channel, owner, delivery timing, capacity, and what happens if a link or resource fails. Keep one fulfillment record per requester to avoid duplicate delivery. This skill does not send or enable automation.
6. Define a bounded pilot with sample unit, resource/time cost, useful-result event, qualified next step, observation window, and success/kill thresholds. A request count alone cannot establish the paid bridge.
7. Apply `review` to the mechanism and `write` to the invitation and fulfillment drafts. Leave real dates, features, terms, and prices unresolved when unsupported rather than filling them with guesses.

## Output

Artifact outline and worked sample; access/fulfillment policy; pilot brief; channel, paste-ready invitation and delivery message, exact destination, and what to watch. No unsolicited message to every engager.

Write **Success / kill**. Record actual fulfillment/use/qualified-action results in **Last observation** only after the founder reports them. Keep personal requester data in the ignored local outreach directory, not public skill examples.

## Done

The artifact can be used, the promise can be fulfilled, and the proposed test distinguishes requests from use and use from qualified product demand. No campaign or collection form was activated.