Capture Assets

The asset must solve a real small task and produce an explainable result. Email capture does not make weak material valuable, and an opaque score is not analysis.

If .agents/marketing-context.md exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read resource-workflow.md for downloadable formats, stage fit, gating, delivery, promotion, and measurement. Read tool-workflow.md when computation, interaction, or live data materially improves the result.

Operating contract

1. Define audience, triggering situation, immediate task, useful output, inputs, sensitivity, connection to the paid product, and the follow-up appropriate to intent.
2. Choose between a static resource and a tool from utility, data availability, production cost, maintenance, distribution, and consent; specify gating from user value and permission.
3. Produce the complete resource or the smallest tool that yields a trustworthy result, with explicit assumptions and formulas.
4. Specify landing, delivery, access, states, privacy, accessibility, analytics, versioning, rights, and stale behavior.
5. Measure qualified use and downstream value, not downloads or visits alone.

Do not require unrelated personal data, conceal future messaging, withhold a promised result after inputs are submitted, fabricate benchmarks, or build a maintenance burden with no owner.

Return

Concept and rejected options, the finished resource or specification, landing and delivery copy, data and rights requirements, distribution, lifecycle follow-up, QA, measurement, and refresh or retirement condition.