Menu
Add a new open source project to the marketing pipeline. Researches real user pain, auto-detects project type, generates everything.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Fetch engagement metrics from all platforms and show how posts are performing. Sends a Slack digest if configured.
Generate social media posts for a project. Draft them yourself following the voice rules below, then validate with the anti-slop gate.
Run the daily post rotation — drafts and posts for all live projects across their channels.
Launch a project to all directories, generate drafts for all channels, and post everywhere. The full launch sequence.
Publish a draft to a social channel (Bluesky, Dev.to, Hashnode, or Mastodon).
Check credential configuration and API connectivity.
| name | onboard |
| description | Add a new open source project to the marketing pipeline. Researches real user pain, auto-detects project type, generates everything. |
| user-invocable | true |
| allowed-tools | ["Bash(marketing onboard *)","Bash(marketing plan)","WebSearch","WebFetch","Write","Read"] |
This is a multi-step process. Do NOT skip the research phase.
You only need ONE thing from the user: the GitHub repo (owner/repo or full URL).
Everything else is auto-detected:
If the user says "onboard my project at owner/repo" that's enough to proceed.
Before generating any marketing content, research how real people describe the problem this tool solves.
Save findings to /tmp/pain-research-{name}.md.
marketing onboard --name <name> --repo <owner/repo> --pain-context /tmp/pain-research-<name>.md
The --kind flag is optional — the pipeline auto-detects it from the README. Only pass it if you want to override the detection.
Show the user what was generated. Suggest next steps: