distribution-ops
Distribution Ops
Overview
This skill turns a chosen path into a channel-specific go-to-market sequence. The goal is to choose the strongest realistic channel, not to create a laundry list of generic marketing ideas.
Load references/channel-patterns.md when selecting channels. Load
references/channel-metrics.md when defining thresholds.
When to use
- When the user has a chosen offer or product and needs go-to-market sequencing
- When warm intros, audience, partnerships, or directories must be translated into a real plan
- When channel choice is a bottleneck
Do NOT use when:
- The offer or opportunity is still unclear
- The user needs opportunity selection rather than channel execution
Workflow
1. Choose the strongest starting channel
Pick one primary channel first, based on:
- trust
- access
- conversion plausibility
- speed to signal
2. Sequence supporting channels
Only add supporting channels if they help the main one.
3. Define assets and metrics
For the primary channel, define:
- assets needed
- outreach or content sequence
- success metrics
- kill criteria
4. Produce the plan
Return both:
- a readable channel plan
- a JSON block using
assets/distribution-plan-template.json
Default sections:
Channel ThesisPrimary ChannelSupporting ChannelsAsset ChecklistMetrics And Kill CriteriaStructured Plan
Checklist
- One primary channel is clearly chosen
- The choice matches the user's actual access, not generic advice
- Metrics and kill criteria are explicit
- Supporting channels help the primary one rather than distracting from it
- Readable plan and structured JSON are both present
Key principles
- Start where trust already exists — Warm access or trusted audience beats clever tactics.
- One channel first — Strong sequencing beats multi-channel thrash.
- Kill weak channels quickly — A bad channel should be cut, not rationalized.
More from accolver/skill-maker
skill-maker
Create or iteratively improve agent skills with eval-driven refinement when the task is to build a new SKILL.md package or tune an existing skill’s trigger accuracy and performance.
26git-conventional-commits
Generate conventional commit messages from staged git changes when the task is to name or format a commit, not to review code or write release notes.
16pdf-toolkit
Operate the bundled PDF scripts to extract, OCR, create, merge, split, or convert PDFs when the task explicitly involves PDF document processing.
14nostr-event-builder
Construct valid Nostr event JSON and tag structures from requirements when the task is to create or validate concrete events rather than choose which NIPs to use.
12error-handling
Standardize application error handling—taxonomy, propagation, response shapes, logging, and correlation IDs—when the task is to improve consistency of existing error behavior across a codebase.
12pr-description
Generate pull-request descriptions from branch diffs when the task is to explain change scope, motivation, testing, risk, and reviewer guidance for a reviewable branch.
12