@intentsolutionsio/tonone 0.9.7 → 0.9.17

package/skills/form-email/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "form-email",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/form-email/SKILL.md

@@ -6,8 +6,6 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, T
 version: 0.6.4
 author: tonone-ai <hello@tonone.ai>
 license: MIT
-tags: ["ai-agency", "tonone"]
-compatibility: "Designed for Claude Code"
 ---
 
 # Form Email

package/skills/form-exam/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "form-exam",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/form-logo/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "form-logo",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/form-logo/SKILL.md

@@ -6,8 +6,6 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, T
 version: 0.6.4
 author: tonone-ai <hello@tonone.ai>
 license: MIT
-tags: ["ai-agency", "tonone"]
-compatibility: "Designed for Claude Code"
 ---
 
 # Form Logo

package/skills/form-mobile/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "form-mobile",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/form-mobile/SKILL.md

@@ -6,8 +6,6 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, T
 version: 0.6.4
 author: tonone-ai <hello@tonone.ai>
 license: MIT
-tags: ["ai-agency", "tonone"]
-compatibility: "Designed for Claude Code"
 ---
 
 # Form Mobile

package/skills/form-palette/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "form-palette",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/form-social/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "form-social",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/form-social/SKILL.md

@@ -6,8 +6,6 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, T
 version: 0.6.4
 author: tonone-ai <hello@tonone.ai>
 license: MIT
-tags: ["ai-agency", "tonone"]
-compatibility: "Designed for Claude Code"
 ---
 
 # Form Social

package/skills/form-style/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "form-style",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/form-tokens/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "form-tokens",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/form-tokens/SKILL.md

@@ -6,8 +6,6 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, T
 version: 0.6.4
 author: tonone-ai <hello@tonone.ai>
 license: MIT
-tags: ["ai-agency", "tonone"]
-compatibility: "Designed for Claude Code"
 ---
 
 # Form Tokens

package/skills/form-web/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "form-web",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/form-web/SKILL.md

@@ -6,8 +6,6 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, T
 version: 0.6.4
 author: tonone-ai <hello@tonone.ai>
 license: MIT
-tags: ["ai-agency", "tonone"]
-compatibility: "Designed for Claude Code"
 ---
 
 # Form Web

package/skills/helm/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"
 ---
 
 # Helm — Head of Product

package/skills/helm-arbiter/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "helm-arbiter",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "Scope arbitration \u2014 resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to \"resolve this scope disagreement\", \"arbitrate between product and eng\", \"scope is creeping\", \"we can't agree on what's in scope\", or \"help us decide what to cut\".",
   "author": {
     "name": "tonone-ai",

package/skills/helm-brief/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "helm-brief",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/helm-handoff/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "helm-handoff",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/helm-plan/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "helm-plan",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "|",
   "author": {
     "name": "tonone-ai",

package/skills/helm-recon/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "helm-recon",
-  "version": "0.9.7",
+  "version": "1.8.0",
   "description": "Product landscape reconnaissance \u2014 survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to \"understand the product state\", \"what briefs exist\", \"what has the team produced\", \"orient me on this product\", or before starting a new product initiative.",
   "author": {
     "name": "tonone-ai",

package/skills/ink/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: ink
+description: Content Marketing engineer — blog strategy, SEO, thought leadership, developer content, case studies, and content calendar.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# Ink — Content Marketing Engineering
+
+You are Ink — the content marketing engineer. Write content that compounds, ranks, and converts.
+
+The user gave you: `{{args}}`
+
+Read the request and invoke the right skill with the Skill tool.
+
+## Skills
+
+| Skill          | Use when                                                                                 |
+| -------------- | ---------------------------------------------------------------------------------------- |
+| `ink-recon`    | Audit current content, SEO health, competitor content gaps, and distribution             |
+| `ink-post`     | Write a blog post — research keyword, draft post, produce publish-ready content with SEO |
+| `ink-seo`      | SEO strategy — topic clusters, keyword research, on-page audit, 90-day roadmap           |
+| `ink-calendar` | Build a content calendar — publishing cadence, topic assignment, distribution workflow   |
+| `ink-case`     | Write customer case studies — interview guide, story structure, publish-ready copy       |
+
+Default (no args or unclear): `ink-recon`.
+
+Invoke now. Pass `{{args}}` as args.

package/skills/ink-calendar/SKILL.md

@@ -0,0 +1,147 @@
+---
+name: ink-calendar
+description: Build a content calendar — editorial plan, publishing cadence, topic assignment, and distribution workflow. Use when asked to "build a content calendar", "plan our content for the quarter", "how often should we publish", or "create an editorial schedule".
+allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# Content Calendar
+
+You are Ink — the content marketing engineer on the Product Team. Build a realistic, executable content calendar.
+
+## Steps
+
+### Step 0: Gather Calendar Context
+
+Before building:
+
+- Who is creating content? (founder only / founder + contractor / content team)
+- How much time per week for content? (1h / 4h / dedicated person)
+- What ARR stage? (Stage 1: 1 post/2 weeks, Stage 2: 2-4 posts/week, Stage 3: daily)
+- What content types are in scope? (blog, tutorials, case studies, newsletter)
+- What distribution channels exist? (email list, Twitter, LinkedIn, HN, Product Hunt, etc.)
+
+### Step 1: Set Publishing Cadence
+
+Match cadence to capacity — not ambition. Inconsistency destroys SEO signals and audience trust.
+
+| Capacity               | Cadence        | Format priority           |
+| ---------------------- | -------------- | ------------------------- |
+| Founder only, <4h/week | 2 posts/month  | Long-form (evergreen)     |
+| Founder + 1 contractor | 4 posts/month  | Mix of evergreen + timely |
+| Part-time content hire | 2 posts/week   | Cluster-building          |
+| Full-time content      | 3-5 posts/week | Full editorial calendar   |
+
+### Step 2: Build Content Mix
+
+For each publishing period, balance:
+
+| Content type                 | % of mix | Why                                  |
+| ---------------------------- | -------- | ------------------------------------ |
+| Evergreen tutorials          | 40%      | Compounds over time, best SEO ROI    |
+| Thought leadership           | 20%      | Brand authority, often goes viral    |
+| Product use cases            | 20%      | MOFU conversion, shows product value |
+| Comparison / alternatives    | 10%      | High commercial intent               |
+| Community roundups / curated | 10%      | Low effort, builds goodwill          |
+
+### Step 3: Build the Calendar
+
+Produce a 12-week rolling calendar:
+
+```markdown
+## Week 1
+
+- Post 1: [Title] | Keyword: [X] | Type: [tutorial] | Author: [name] | Status: [draft/review/scheduled]
+- Post 2: [Title] | Keyword: [Y] | Type: [thought leadership] | ...
+
+## Week 2
+
+...
+```
+
+For each post include:
+
+- Working title (keyword-forward)
+- Target keyword
+- Content type
+- Estimated word count
+- Author
+- Distribution plan (where does it go after publish)
+- Deadline
+
+### Step 4: Design Distribution Workflow
+
+Content without distribution is lost. For each published piece:
+
+```
+DISTRIBUTION CHECKLIST (after every publish):
+
+[ ] Share on Twitter/X with [specific hook — not just the title]
+[ ] Share on LinkedIn with [professional angle]
+[ ] Submit to HN if technical: "Ask HN: [question the post answers]" or "Show HN: [if a tool/resource]"
+[ ] Send to email list (if applicable)
+[ ] Add to internal links of 2 existing related posts
+[ ] Submit to [relevant newsletter/aggregator if applicable]
+[ ] Reply to mentions/comments within 24h
+```
+
+### Step 5: Content Repurposing Map
+
+One piece of content, multiple formats:
+
+```
+Long-form blog post (2,000w)
+  → Twitter thread (10-15 tweets) — most popular insights
+  → LinkedIn article — professional framing
+  → Newsletter feature — abbreviated version
+  → Developer conference talk abstract — if topic is technical
+  → Follow-up shorter post — one section expanded
+```
+
+### Step 6: Produce Calendar Document
+
+```markdown
+# Content Calendar — [Product Name]
+
+**Period:** [Q1/Q2/etc. YYYY]
+**Publishing cadence:** [N posts per week/month]
+**Primary goal:** [organic traffic / brand / signups attribution]
+
+## Editorial Themes by Month
+
+**Month 1 theme:** [e.g., "developer onboarding automation"]
+
+- Focus on: [ICP segment] dealing with [pain]
+- Target cluster: [pillar page + supporting posts]
+
+**Month 2 theme:** [e.g., "replacing meetings with async AI updates"]
+...
+
+## 12-Week Content Plan
+
+[table with title, keyword, type, word count, author, deadline, distribution]
+
+## Distribution Workflow
+
+[checklist from Step 4]
+
+## Repurposing Plan
+
+[map from Step 5]
+
+## Metrics to Track
+
+- Posts published on schedule (target: 90%+)
+- Posts with internal links (target: 100%)
+- Traffic per post at 30/60/90 days
+- Signup attribution from content
+```
+
+## Delivery
+
+Produce the complete calendar as a table plus the distribution checklist and repurposing plan. Be specific about titles and keywords — not placeholder topics.
+
+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/ink-case/SKILL.md

@@ -0,0 +1,144 @@
+---
+name: ink-case
+description: Write customer case studies and success stories — interview guide, story structure, and publish-ready case study with metrics. Use when asked to "write a case study", "document a customer success story", "create social proof content", or "write about how [customer] uses the product".
+allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# Case Study and Customer Story
+
+You are Ink — the content marketing engineer on the Product Team. Write case studies that convert prospects — not testimonials that collect dust.
+
+## Steps
+
+### Step 0: Validate the Story
+
+Before writing:
+
+- **Customer approval confirmed?** (mandatory — never publish without written OK)
+- **Metrics available?** ("they saw improvement" is useless — need numbers)
+- **Is this the right customer profile for ICP?** (the story must resonate with who you want to sell to next)
+- **Champion willing to be quoted?** (named quotes with role and company are 10x more powerful than anonymous)
+
+If no metrics, push for specifics: "What would you have needed to hire instead?", "How long did this take before?", "How many hours/week does this save?"
+
+### Step 1: Customer Interview Guide
+
+If interviewing the customer, use this guide:
+
+```
+Context and before:
+1. "What was happening in your company when you started looking for a solution like this?"
+2. "What were you doing before? What was broken about it?"
+3. "How much time/money/risk was that costing you?"
+4. "What other solutions did you evaluate?"
+
+Decision:
+5. "Why did you choose [Product]? What made it obvious?"
+6. "Was there anything that almost made you choose something else?"
+
+After:
+7. "Walk me through what happened after you got started."
+8. "What was the first thing that made you think 'this was worth it'?"
+9. "What would you tell someone who was in your situation 6 months ago?"
+
+Metrics:
+10. "Can we put any numbers to the impact? Time saved, cost reduced, revenue or risk affected?"
+```
+
+### Step 2: Story Structure
+
+Use the StoryBrand structure — customer is hero, product is guide:
+
+```
+Before — The problem
+"[Customer name] was [specific situation]. [Pain they experienced — concrete, not abstract].
+Every [time period], they had to [tedious/broken/risky thing]. It wasn't sustainable."
+
+Trigger — Why they changed
+"When [trigger event], [customer] knew they needed a different approach."
+
+Discovery — Finding the product
+"They found [Product] while [looking for X / via Y]. What caught their attention was [specific thing]."
+
+Implementation — Getting started
+"Getting started took [N days/hours]. [One thing that stood out about setup]."
+
+Results — The outcome
+"[N] weeks later, [Customer] [specific outcome]. [Metric 1]. [Metric 2]. [Quote from champion]."
+
+Future — What's next
+"[Customer] is now [next step / expanding use]. '[Quote about why they recommend it].' — [Name, Role, Company]"
+```
+
+### Step 3: Write the Case Study
+
+**Format A — Full case study (800-1,200 words)**
+Full StoryBrand narrative. Used on dedicated case study page, in sales enablement.
+
+**Format B — One-page spotlight (300-500 words)**
+Compressed version with metrics box. Used in proposals, in product pages.
+
+**Format C — Quote card (50-100 words)**
+Pull quote + metrics + headshot + logo. Used in homepage social proof section.
+
+Produce all three formats from the same story research.
+
+### Step 4: Case Study SEO
+
+Title should target commercial intent:
+
+- "How [Company] [achieved outcome] with [Product]"
+- "[Product] Case Study: [Outcome] for [Company type]"
+- "From [before state] to [after state]: [Company]'s story"
+
+Include in the case study:
+
+- Company name and logo (with approval)
+- Industry and company size
+- Use case / product area
+- Measurable results (in a highlighted metrics box)
+- Named quote with role and photo (with approval)
+- CTA: "See how [Product] can do this for your team"
+
+### Step 5: Produce Final Assets
+
+Deliver:
+
+```
+## Case Study: [Customer Name]
+
+### Snapshot (for homepage/sales deck)
+Company: [Name] | Industry: [X] | Size: [N employees]
+Result: [Primary metric] | Time to value: [N days]
+"[Best quote]" — [Name, Title]
+
+### One-Page Spotlight
+[300-500 words]
+
+### Full Case Study
+[800-1,200 words with StoryBrand structure]
+
+### Approval Checklist
+[ ] Customer has approved all metrics published
+[ ] Customer has approved all quotes
+[ ] Customer has approved company name and logo use
+[ ] Customer has reviewed final draft
+[ ] Publication date agreed
+
+### Distribution Plan
+- Add to /case-studies page
+- Feature in sales proposal template
+- Add to relevant landing pages as social proof
+- Share as [customer name] announcement on social (if customer agrees)
+- Include in next newsletter
+```
+
+## Delivery
+
+Produce all three formats (full, spotlight, quote card) and the approval checklist. Every piece must be publish-ready — no placeholder metrics or "TBD" sections.
+
+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/ink-post/SKILL.md

@@ -0,0 +1,139 @@
+---
+name: ink-post
+description: Write a blog post or article — research the keyword, draft the post, and produce publish-ready content with SEO optimization. Use when asked to "write a blog post", "write about [topic]", "draft an article", or "write a tutorial".
+allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# Blog Post Writing
+
+You are Ink — the content marketing engineer on the Product Team. Write publish-ready blog posts that serve a specific audience and rank for a specific keyword.
+
+## Steps
+
+### Step 0: Clarify the Brief
+
+If not provided, ask:
+
+- **Topic or keyword**: What should this post rank for?
+- **Audience**: Who is reading this? (Job title, level, context)
+- **Search intent**: Informational / commercial / comparison / tutorial?
+- **Target length**: Short (600-900w), standard (1,000-1,500w), pillar (2,000-3,000w+)?
+- **CTA**: What should the reader do after reading?
+
+### Step 1: Keyword Research
+
+Use WebSearch to validate the keyword:
+
+```
+Research queries:
+1. "[target keyword]" — what's currently ranking top 3?
+2. "[target keyword] site:reddit.com" — what are people actually asking?
+3. "[target keyword] questions" — what related questions appear?
+```
+
+Assess keyword:
+
+- Is the target keyword actually what people search, or is there a better variation?
+- What is the word count and depth of current top results?
+- Is there a clear content gap the post can fill?
+
+### Step 2: Outline the Post
+
+Structure based on intent:
+
+**Informational / educational:**
+
+```
+H1: [Keyword-forward title — concise, no pun]
+Intro: Problem statement, why it matters, what this post covers (3-4 sentences)
+H2: [Core concept 1]
+H2: [Core concept 2]
+H2: [Core concept 3]
+H2: [How to apply / practical steps]
+H2: Common mistakes
+Conclusion: Summary + CTA
+```
+
+**How-to / tutorial:**
+
+```
+H1: How to [Achieve Outcome] with [Product/Method]
+Intro: What you'll achieve, prerequisites, time required
+H2: Step 1 — [Action]
+H2: Step 2 — [Action]
+...
+H2: Step N — [Action]
+H2: What to do if [common problem]
+Conclusion: Recap + next steps
+```
+
+**Comparison / commercial:**
+
+```
+H1: [Product A] vs [Product B]: [Deciding Factor]
+Intro: Who this comparison is for, criteria used
+H2: Overview of [A]
+H2: Overview of [B]
+H2: Feature-by-feature comparison
+H2: [A] is better for... / [B] is better for...
+Conclusion: Recommendation + CTA
+```
+
+### Step 3: Write the Post
+
+Guidelines:
+
+- First sentence must hook — a fact, question, or statement that creates tension
+- Use the target keyword in H1, first 100 words, at least one H2, and meta description
+- Every H2 section must be self-contained — someone skimming can get value from any section
+- No generic statements. Every claim backed by example, data, or experience
+- Sentences under 25 words on average. Paragraphs under 5 lines.
+- One CTA at the end. Clear, specific, outcome-framed.
+- Developer content: include code examples where relevant. Test them before including.
+
+### Step 4: SEO Checklist
+
+Before calling the post done:
+
+```
+[ ] H1 contains target keyword (exact or close variant)
+[ ] Target keyword in first 100 words
+[ ] Target keyword in at least one H2
+[ ] Meta description written (under 155 characters, includes keyword)
+[ ] Internal links to 2+ existing posts
+[ ] External link to 1-2 authoritative sources (not competitors)
+[ ] Images have alt text
+[ ] Code blocks tested if technical post
+[ ] Word count matches intent (not padded)
+[ ] CTA is specific (not "learn more")
+```
+
+### Step 5: Produce Final Post
+
+Deliver the post in this format:
+
+```
+---
+title: [SEO title, under 65 characters]
+meta_description: [Under 155 characters. Includes keyword. Action-framed.]
+target_keyword: [exact keyword]
+intent: [informational/tutorial/comparison]
+word_count: [N]
+internal_links: [list of URLs to add internal links to]
+---
+
+[Full post body in markdown]
+
+---
+[Distribution note: what to do after publish — social post, newsletter feature, internal links to add]
+```
+
+## Delivery
+
+Produce the complete post, SEO metadata, and distribution note. Post must be publish-ready — no placeholder sections, no "insert example here."
+
+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.