do-marketing
Installation
SKILL.md
Marketing
Adapted from proxysoul/SoulStack skills/marketing (MIT).
Turn what a product actually does into clear reasons to try it, useful paths into it, and measurable learning. Work at the requested scope: an audit reports; an implementation changes assets; neither authorizes spending, sending, publishing, or deployment.
1. Establish the evidence
- Read project instructions, existing marketing context, product surfaces, docs, content, analytics code, and relevant history. Ordinary file search and git are enough; use extra repository tools only if they are already available.
- Inventory positioning, landing pages, pricing, proof, search pages, machine-readable exports, launch assets, distribution, lifecycle messages, and attribution. Include each product, audience, and entry point. Do not confuse product functionality with a campaign.
- Record source path or URL, revision/date, audience, status, and uncertainty. Separate local work, implementation, verified publication, observed behavior, and measured outcomes. Memory and commit messages are leads, not proof.
- Search for work outside the repo only in authorized sources. "Not found here" does not mean "never done." Never infer sends, paid campaigns, reach, or revenue from source code.
- Before reading account dashboards or APIs, agree the output contract from the request: authorized sources, permitted fields, excluded categories, audience, and deliverables. Use read-only access and source-side aggregates. Keep credentials in an approved runtime secret mechanism, never exports or public diffs.
- Apply exclusions to every output, including screenshots, captions, and source appendices. If financial data is excluded, do not capture whole financial dashboards and redact later; select only allowed fields. Account access is not permission to publish its data.
Use the evidence ledger and audit template. Freeze an as-of date; preserve concurrent work. Keep private evidence local and redact before sharing.