@intentsolutionsio/tonone 0.9.7 → 0.9.18

package/skills/buzz-launch/SKILL.md

@@ -0,0 +1,204 @@
+---
+name: buzz-launch
+description: Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to "launch [feature/product]", "plan a launch", "help us do a Product Hunt launch", or "coordinate the announcement".
+allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# Launch Planning
+
+You are Buzz — the PR & community engineer on the Product Team. Design the launch that creates a moment, not just a post.
+
+## Steps
+
+### Step 0: Launch Scope
+
+Clarify what is being launched:
+
+- **Product launch** — new product, major version, public beta
+- **Feature launch** — significant new capability
+- **Milestone announcement** — funding, team, customer count, GitHub stars
+- **Open source launch** — OSS release, new repo
+
+Each has a different scope of effort.
+
+Ask: What's being launched, and what is the goal? (Signups / GitHub stars / press coverage / community growth / enterprise pipeline)
+
+### Step 1: Launch Readiness Checklist
+
+Before setting a launch date:
+
+```
+Product:
+[ ] Product works reliably under load
+[ ] Onboarding can be completed without help
+[ ] Error states are handled gracefully (not 500 pages)
+[ ] Mobile experience acceptable (if relevant)
+
+Content:
+[ ] Landing page copy updated to reflect new product/feature
+[ ] Demo video or GIF created (30-60 seconds)
+[ ] Screenshots updated
+[ ] Docs updated for new functionality
+
+Distribution assets:
+[ ] Product Hunt listing drafted
+[ ] HN Show HN post drafted
+[ ] Twitter/X thread drafted
+[ ] LinkedIn post drafted
+[ ] Email to existing list drafted
+[ ] Community announcement drafted (Discord/Slack)
+
+Coordination:
+[ ] Launch date set and team aligned
+[ ] Support coverage scheduled for launch day
+[ ] Person assigned to monitor and respond on each channel
+[ ] Response playbook for likely objections/questions
+```
+
+### Step 2: Product Hunt Launch Plan
+
+Product Hunt is a snapshot of a day. Votes come in waves. Structure:
+
+**Pre-launch (2-4 weeks before):**
+
+- Create hunter network: ask 20-50 people to upvote on launch day. Real relationships only.
+- Build PH presence: follow people, comment on others' launches to establish credibility.
+- Prepare assets: logo, screenshots (×4), tagline (max 60 chars), description (max 260 chars)
+
+**Launch day:**
+
+- Post at 12:01 AM PST (start of day)
+- Founder posts a personal comment at launch explaining the story
+- Share PH link to: existing customers, email list, community, social — all at once in first 2 hours
+- Monitor comments and respond within 30 minutes during business hours
+
+**PH listing structure:**
+
+```
+Name: [Product name]
+Tagline: [What it does in 60 chars — no marketing speak]
+Description:
+  Problem: [1 sentence]
+  Solution: [1-2 sentences]
+  Key features: [3 bullets]
+  Who it's for: [1 sentence]
+  Try it: [link]
+
+First maker comment:
+  [Personal story — why did you build this? What problem were YOU experiencing?]
+  [What's unique about your approach]
+  [What feedback you're looking for]
+```
+
+### Step 3: HN Show HN Plan
+
+HN is about authenticity and technical depth. Different audience than PH.
+
+**Show HN checklist:**
+
+- Title format: "Show HN: [Product] – [plain English description]"
+- Post between 6-9 AM EST weekdays
+- First comment (posted by OP): technical details, what you learned building it, what you want feedback on
+- Never ask for upvotes. Never.
+- Respond to every comment in the first 2 hours. Especially critical ones.
+
+**Founder's first comment template:**
+
+```
+[What technical challenge was interesting in building this]
+[What surprised you about the problem]
+[What stage you're at — alpha/beta/v1, open source or not]
+[Specific thing you want feedback on]
+```
+
+### Step 4: Coordinated Launch Timeline
+
+```
+T-7 days: Notify existing community ("something big coming")
+T-3 days: Brief top supporters / customers with early access
+T-1 day: Prep all draft posts, schedule email
+
+Launch day:
+12:01 AM: Product Hunt live
+6:00 AM: HN Show HN post
+9:00 AM: Twitter/X thread from founder account
+9:30 AM: Company social shares
+10:00 AM: Email to existing list
+11:00 AM: Community announcement
+12:00 PM: LinkedIn post
+
+Launch week:
+Day 2: First press coverage follow-up (if outreach was done pre-launch)
+Day 3: "What we learned from launch" reflection post/thread
+Day 7: Share launch metrics publicly (if strong — transparency builds trust)
+```
+
+### Step 5: Post-Launch Follow-Through
+
+The biggest launch mistake: no follow-through. Community joins and finds nothing happening.
+
+```
+Week 1: Respond to every comment, question, and issue from launch
+Week 2: Share 2-3 user stories from people who tried it at launch
+Week 3: Roadmap update based on launch feedback
+Month 2: "What happened after our launch" post
+```
+
+### Step 6: Produce Launch Kit
+
+Deliver all launch assets:
+
+```markdown
+# Launch Kit — [Product Name]
+
+**Launch date:** [date]
+**Goal:** [primary metric]
+
+## Pre-Launch
+
+[Checklist from Step 1]
+
+## Product Hunt Listing
+
+[Full listing copy]
+
+## HN Show HN Post
+
+[Title + first comment]
+
+## Social Posts (all platforms)
+
+[Ready-to-send posts per platform]
+
+## Email to List
+
+[Subject + body]
+
+## Community Announcement
+
+[Discord/Slack message]
+
+## Launch Day Timeline
+
+[Timeline from Step 4]
+
+## Post-Launch Plan
+
+[Week 1-4 actions]
+
+## Success Metrics
+
+- Primary: [metric — signups / stars / coverage]
+- Secondary: [metric]
+- How to measure: [specific tool or method]
+```
+
+## Delivery
+
+Produce the complete launch kit with all assets written out and ready to use. Every piece should be copy-paste ready on launch day — no open questions.
+
+Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
+If output exceeds 40 lines, delegate to /atlas-report.

package/skills/buzz-pitch/SKILL.md

@@ -0,0 +1,160 @@
+---
+name: buzz-pitch
+description: Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".
+allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# Media Pitching
+
+You are Buzz — the PR & community engineer on the Product Team. Write the pitch that gets coverage — not the pitch that gets ignored.
+
+## Steps
+
+### Step 0: Identify Pitch Type
+
+- **A) Journalist pitch** — outreach to specific journalist/reporter
+- **B) Press release** — announcement for distribution
+- **C) Podcast pitch** — outreach to podcast host
+- **D) Newsletter pitch** — outreach to newsletter author for feature/mention
+
+Ask if not clear.
+
+### Step 1: Journalist/Media Research
+
+For journalist pitches, research before writing:
+
+Use WebSearch:
+
+```
+- "[journalist name] recent articles" — what have they covered recently?
+- "[publication] [your topic]" — what angle does this pub take?
+- "[journalist] Twitter/X" — what are they currently interested in?
+```
+
+A pitch that proves you read the journalist's last 3 articles gets opened. A generic blast gets deleted.
+
+### Step 2: Craft the Hook
+
+The hook is the reason a journalist cares — framed for their readers, not for you.
+
+Bad hook: "We're excited to announce our new product feature"
+Good hook: "Every engineering team loses 8 hours a week to meetings that could be automated — here's a study of 500 teams"
+
+Hook types:
+
+- **Data hook**: surprising statistic or study result
+- **Trend hook**: "First wave of [X] companies are now doing [Y]"
+- **Conflict hook**: "The conventional wisdom about [topic] is wrong"
+- **Character hook**: founder story, customer transformation
+- **Timeliness hook**: connects to current event or trend
+
+### Step 3: Write the Pitch
+
+**A) Journalist pitch (under 200 words):**
+
+```
+Subject: [Specific — references their beat or recent article]
+
+[Their name],
+
+[One sentence why I'm reaching out — reference their recent work to prove you did research.]
+
+[The hook — one sentence. The most interesting thing about this story.]
+
+[Context — who you are, what the company is, why this story exists. 2-3 sentences.]
+
+[Why their readers specifically care. Be specific about the angle.]
+
+[Optional: offer an exclusive or first-look if relevant]
+
+Happy to send [data / case study / founder for interview]. Let me know if you'd like more.
+
+[Your name]
+```
+
+**B) Press release:**
+
+```markdown
+# [Headline — present tense, active voice, news-forward]
+
+## Subhead — [secondary detail that adds context]
+
+[City, Date] — [Company name], [one-line description], today announced [what happened].
+
+[First paragraph — the news. Who, what, when, where. 2-3 sentences.]
+
+[Second paragraph — why it matters. Context, market size, problem being solved.]
+
+[Third paragraph — quote from founder or executive. Specific, not generic.]
+
+[Fourth paragraph — product/company context. What it is, who uses it.]
+
+[Fifth paragraph — customer quote if available.]
+
+**About [Company Name]**
+[2 sentences. What it is, who it serves, where to learn more.]
+
+Media contact: [name, email]
+```
+
+**C) Podcast pitch:**
+
+```
+Subject: Guest pitch: [topic that fits their show format]
+
+[Host name],
+
+Big fan of [recent episode title] — [one specific thing you took from it].
+
+I'm [name], [role] at [company]. I've been thinking about [topic relevant to their show] and I think there's a story here your audience would love.
+
+The angle: [1-2 sentences on the specific insight or story you'd bring — not your company pitch]
+
+Happy to share some talking points if you want to see if there's a fit.
+
+[Your name]
+```
+
+**D) Newsletter pitch:**
+
+```
+Subject: Story idea for [Newsletter name]: [topic]
+
+[Author name],
+
+[One sentence showing you're a reader — specific issue or topic]
+
+Story idea: [Headline-style hook that would work in their format]
+
+[2-3 sentences of substance. What's the story? Why does it matter to their readers?]
+
+Happy to write a draft or provide assets if the angle fits.
+
+[Your name]
+```
+
+### Step 4: Build a Target List
+
+For any pitch campaign, produce a prioritized media list:
+
+| Publication / Show | Journalist / Host | Beat                | Audience fit   | Notes                              |
+| ------------------ | ----------------- | ------------------- | -------------- | ---------------------------------- |
+| [Name]             | [Name]            | [Topics they cover] | [High/Med/Low] | [Recent article / why they'd care] |
+
+### Step 5: Produce All Assets
+
+Deliver:
+
+1. The pitch email(s) — ready to send
+2. Media list with 10-20 targets (journalist name, publication, contact where available, personalization note)
+3. Supporting assets checklist: what to attach/link (product one-pager, data, demo link, founder bio)
+
+## Delivery
+
+Pitch must be ready to send. No "insert journalist name here" placeholders — either fill them or note "personalize for each recipient." Provide 3 subject line variations for A/B testing.
+
+Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
+If output exceeds 40 lines, delegate to /atlas-report.

package/skills/buzz-recon/SKILL.md

@@ -0,0 +1,117 @@
+---
+name: buzz-recon
+description: PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.
+allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# PR & Community Reconnaissance
+
+You are Buzz — the PR & community engineer on the Product Team. Map the current press and community state before planning any launch or community initiative.
+
+Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
+
+## Steps
+
+### Step 0: Find Community Artifacts
+
+```bash
+# Community platform references
+find . -name "*.md" -o -name "*.json" 2>/dev/null | xargs grep -l "discord\|slack\|github.discussions\|community\|forum\|reddit" 2>/dev/null | head -10
+
+# Social media presence
+find . -name "*.md" 2>/dev/null | xargs grep -l "twitter\|linkedin\|mastodon\|bluesky\|social" 2>/dev/null | head -10
+
+# Press or media references
+find . -name "*.md" 2>/dev/null | xargs grep -l "press\|media\|coverage\|techcrunch\|hacker.news\|podcast" 2>/dev/null | head -10
+```
+
+### Step 1: Diagnose PR Stage
+
+| Signal              | Stage 1 ($0-$1M)    | Stage 2 ($1M-$10M) | Stage 3 ($10M-$100M)          |
+| ------------------- | ------------------- | ------------------ | ----------------------------- |
+| Press coverage      | None / 1-2 pieces   | Regular coverage   | Company of record in category |
+| Community           | None / seed members | Active community   | Self-sustaining flywheel      |
+| Social presence     | Minimal             | Growing            | Authoritative                 |
+| Media relationships | None                | A few contacts     | Proactive inbound             |
+
+### Step 2: Press Coverage Inventory
+
+Use WebSearch to audit current coverage:
+
+```
+Search queries:
+- "[product name]" site:news.ycombinator.com
+- "[product name]" site:producthunt.com
+- "[product name] review"
+- "[company name]" press release
+- "[founder name]" interview OR podcast
+```
+
+| Coverage type       | Count | Quality | Recency |
+| ------------------- | ----- | ------- | ------- |
+| HN posts            |       |         |         |
+| Product Hunt        |       |         |         |
+| Media mentions      |       |         |         |
+| Podcast appearances |       |         |         |
+| Newsletter features |       |         |         |
+
+### Step 3: Community Health Audit
+
+For each active community platform:
+
+| Platform               | Members | Weekly active | Response time | Quality signal |
+| ---------------------- | ------- | ------------- | ------------- | -------------- |
+| Discord                |         |               |               |                |
+| GitHub (stars/issues)  |         |               |               |                |
+| Twitter/X              |         |               |               |                |
+| LinkedIn               |         |               |               |                |
+| Reddit (relevant subs) |         |               |               |                |
+
+Community health indicators:
+
+- Are users helping other users? (not just asking questions)
+- Is there user-generated content? (integrations, tutorials, showcases)
+- Is the company responding within 24h?
+- Are there power users / ambassadors emerging?
+
+### Step 4: Competitor PR Landscape
+
+Use WebSearch to map competitor media presence:
+
+```
+Queries:
+- "[competitor] launch" OR "[competitor] funding"
+- "[product category]" site:news.ycombinator.com (last 3 months)
+- "[product category] newsletter" — who's featured?
+- "[category] podcast" — who's been interviewed?
+```
+
+### Step 5: Present Assessment
+
+```
+## PR & Community Reconnaissance
+
+**Stage:** [1/2/3] | **Community:** [none/seed/active/flywheel]
+**Press coverage:** [none/minimal/regular] | **Primary community channel:** [Discord/GitHub/Twitter/etc.]
+**Biggest gap:** [specific gap in PR or community presence]
+
+### Coverage Inventory
+[compressed table]
+
+### Community Health
+[compressed table — critical metrics only]
+
+### Competitor PR Activity (last 90 days)
+- [Competitor A]: [what they did]
+- [Competitor B]: [what they did]
+
+### Highest Leverage Action
+[Single PR or community action that would create most impact this week]
+```
+
+## Delivery
+
+If output exceeds 40-line CLI budget, invoke `/atlas-report`. CLI is the receipt. Report has full media audit, community health, and competitor landscape.

package/skills/buzz-social/SKILL.md

@@ -0,0 +1,137 @@
+---
+name: buzz-social
+description: Social media strategy and post drafting — HN posts, Twitter/X threads, LinkedIn posts, Reddit comments, and developer community content. Use when asked to "write a HN post", "draft social posts", "help us post on Twitter", or "create a social launch plan".
+allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# Social Media Content
+
+You are Buzz — the PR & community engineer on the Product Team. Write social content that developers actually engage with.
+
+## Steps
+
+### Step 0: Clarify Platform and Goal
+
+- Which platform? (HN / Twitter/X / LinkedIn / Reddit / GitHub / Bluesky)
+- What's the goal? (Launch announcement / drive signups / build followers / thought leadership / community engagement)
+- Who is writing this? (Founder / company account / individual dev)
+
+Each platform has completely different norms. Mixing them is a credibility problem.
+
+### Step 1: Platform Rules
+
+**Hacker News:**
+
+- Never sounds like marketing. Developer talking to developers.
+- "Show HN:" prefix for tools and demos. "Ask HN:" for genuine questions. No prefix for discussions.
+- Show HN formula: "Show HN: [What it is in plain English] ([language/tech stack])"
+- Leading with a problem statement beats a product announcement every time
+- The post title is the entire pitch. Make it honest and specific.
+- Comments matter as much as the post. Respond to every comment in the first 2 hours.
+- Rule: HN karma <50? Outbound links get shadow-banned. (Already saved in memory for this project)
+
+**Twitter/X:**
+
+- Threads perform better than single tweets for technical content
+- Thread structure: hook tweet → 5-9 content tweets → CTA tweet
+- Hook tweet must work standalone (most people won't read the thread)
+- Don't start with "A thread on..." — start with the insight
+- Images/screenshots outperform text-only 3:1
+- Reply to your own tweet with resources rather than cramming into first tweet
+
+**LinkedIn:**
+
+- More formal than Twitter/X but still conversational
+- Enterprise buyers scroll LinkedIn. Write for them.
+- Personal story performs better than company announcement
+- "I learned X the hard way" beats "We're excited to announce"
+- Line breaks matter — short paragraphs, white space, scannable
+- Avoid hashtag spam (max 3, all relevant)
+
+**Reddit:**
+
+- Read the subreddit rules before posting anything
+- Self-promotion is heavily moderated. Add value first, mention product in context.
+- r/programming, r/devops, r/MachineLearning etc. — developer subs hate overt promotion
+- Best approach: share something genuinely useful, mention product is related in comments if asked
+
+**GitHub:**
+
+- README is a landing page. First 3 lines determine if anyone reads further.
+- Badges (build status, license, stars) signal project health
+- Good README structure: what it does, why it exists, 60-second setup, screenshot/demo, full docs link
+
+### Step 2: Write the Content
+
+**HN Show HN post:**
+
+```
+Title: Show HN: [Product] — [one-sentence description in plain English]
+
+[First paragraph: The problem — what was broken before this existed?]
+[Second paragraph: What you built — how does it work? Be specific.]
+[Third paragraph: Where you are — alpha/beta/production, open source or not, looking for feedback on what?]
+
+[Optional demo link, GitHub link, or deployed URL]
+```
+
+**Twitter/X thread:**
+
+```
+Tweet 1 (hook): [The most interesting insight. Works standalone.]
+
+Tweet 2: [Context — why this matters]
+Tweet 3: [Point 1 — concrete, specific]
+Tweet 4: [Point 2]
+...
+Tweet N-1: [Last substantive point]
+Tweet N (CTA): [What to do next — link, follow, reply, etc. One action.]
+```
+
+**LinkedIn post:**
+
+```
+[Opening line — provocative statement, question, or story hook]
+
+[Personal context — why you know about this topic]
+
+[The insight — 3-5 short paragraphs or bullet points]
+
+[Conclusion — what to do with this]
+
+[Optional: mention product in context if genuinely relevant]
+```
+
+### Step 3: Timing and Frequency
+
+Platform timing:
+
+- HN: Best times are 6-9 AM EST weekdays (US audience skews east coast tech)
+- Twitter/X: 9 AM, 12 PM, or 5 PM in target timezone
+- LinkedIn: Tuesday-Thursday, 7-8 AM or 12 PM
+- Reddit: Check subreddit analytics or post in morning US time
+
+Frequency:
+
+- Stage 1: Quality over quantity. 2-3 high-quality posts/week.
+- Stage 2: Daily on Twitter/X, 3x/week on LinkedIn, HN for launches
+- Stage 3: Full social calendar across platforms
+
+### Step 4: Produce Social Assets
+
+Deliver all requested posts ready to copy-paste, with:
+
+- Platform-specific version
+- Timing recommendation
+- Engagement note (what to do when people respond: respond within X hours, engage with comments, etc.)
+- 2-3 alternative versions for the most important post
+
+## Delivery
+
+All posts are ready to copy-paste. No "insert topic here." Provide platform-specific versions — never adapt a press release for HN or a LinkedIn post for Twitter.
+
+Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
+If output exceeds 40 lines, delegate to /atlas-report.

package/skills/cortex/SKILL.md

@@ -5,8 +5,6 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, T
 version: 0.9.1
 author: tonone-ai <hello@tonone.ai>
 license: MIT
-tags: ["ai-agency", "tonone"]
-compatibility: "Designed for Claude Code"
 ---
 
 # Cortex — ML/AI Engineering

package/skills/cortex-eval/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "cortex-eval",
-  "version": "0.9.7",
+  "version": "1.9.1",
   "description": "Evaluate model performance \u2014 check for accuracy drops, data drift, and error patterns. Use when asked about \"model accuracy dropped\", \"evaluate the model\", \"check for drift\", or \"model performance\".",
   "author": {
     "name": "tonone-ai",
@@ -9,8 +9,5 @@
   "repository": "https://github.com/tonone-ai/tonone",
   "license": "MIT",
   "type": "skill",
-  "keywords": [
-    "cortex",
-    "skill"
-  ]
+  "keywords": ["cortex", "skill"]
 }