Content Engine
Pre-requisites
Invoke business-context skill. Read GTM spec for this product.
Content ↔ Motion mapping
| Motion |
Content priority |
Output type |
| Developer-led (Sigil) |
Technical depth + honest data |
GitHub README, write-ups, responsible disclosure, HN posts |
| Content-led (InstaIndex) |
SEO + AEO — compound over time |
Blog posts targeting questions, AI-optimised answers |
| Community-led |
Helpfulness first, product second |
Reddit answers, Slack community posts, forum replies |
| Relationship-led (Operable) |
Thought leadership + proof |
LinkedIn posts, industry event talk abstracts, case studies |
AEO Framework (AI Engine Optimisation)
InstaIndex's own AEO is a proof-of-concept. Apply this to every content piece.
What AI search engines want
- Direct answers — lead with the answer, not the context
- Structured format — headers, short paragraphs, numbered steps
- Specificity — dates, numbers, named tools, exact processes
- Authority signals — cited data, named sources, verifiable claims
- Question-answer pairing — match the query format buyers use
AEO checklist for every piece
AEO question targets per product
Sigil:
- "how do I audit AI agent code for security vulnerabilities"
- "MCP server security risks"
- "Claude Code security audit"
- "AI agent supply chain risk"
InstaIndex:
- "why is my website not indexed by AI search engines"
- "how to get indexed by ChatGPT search"
- "IndexNow vs Google Search Console"
- "how to speed up Google indexing 2025"
- "AEO vs SEO difference"
PolicyPA:
- "how to choose private health insurance Australia"
- "best health insurance comparison site Australia"
- "how do health insurance comparison sites make money"
Content formats by channel
Blog posts (InstaIndex, Sigil)
Structure:
- Question hook — title is the question, or title answers the question
- Direct answer — first 2 sentences answer it completely
- Why it matters — context for people who need more
- The specific detail — what makes this post uniquely useful
- One thing to do — actionable close
Target: 800-1200 words for AEO focus. 2000+ for deep technical credibility (Sigil).
LinkedIn posts (Operable, Reece personal brand)
Format: insight → proof → implication → call to action
- No hashtag spam
- Dry voice — "most funds are still doing X manually. here's what the data says"
- Investment operations specificity — not generic fintech
GitHub README (Sigil)
The README is the top-of-funnel. It must:
- State the specific problem in line 1
- Show the detection rate in the first screen
- Have a working example in under 5 commands
- Link to the responsible disclosure paper
HN posts (Sigil)
"Show HN: Sigil — automated security audit for AI agent code"
- Lead with what makes it interesting technically (37 vector patterns, 97.96% validated)
- Acknowledge what it doesn't do
- Invite critique — security community respects honesty
Content calendar framework
Sigil: 1 technical post per month (GitHub, cross-post to security blogs)
InstaIndex: 2 AEO-optimised posts per week (compound SEO)
Operable: 1 LinkedIn post per week (thought leadership, investment ops specific)
PolicyPA: 1 media pitch per month once product is live
Output
Save content pieces to .nomark/growth/<product>/content-<date>-<slug>.md.
Include:
- Headline
- AEO question targeted
- Full draft
- Distribution plan (channel + timing)
- Success metric (views, shares, ranking signal)
1---2name: content-engine3description: Produces content strategy and individual content pieces calibrated to a product's GTM motion. Covers SEO (traditional), AEO (AI search optimisation), and distribution. Reads business context and GTM spec first. Use for blog posts, LinkedIn content, GitHub documentation, technical write-ups, community posts.4---56# Content Engine78## Pre-requisites910Invoke `business-context` skill. Read GTM spec for this product.1112---1314## Content ↔ Motion mapping1516| Motion | Content priority | Output type |17|---|---|---|18| Developer-led (Sigil) | Technical depth + honest data | GitHub README, write-ups, responsible disclosure, HN posts |19| Content-led (InstaIndex) | SEO + AEO — compound over time | Blog posts targeting questions, AI-optimised answers |20| Community-led | Helpfulness first, product second | Reddit answers, Slack community posts, forum replies |21| Relationship-led (Operable) | Thought leadership + proof | LinkedIn posts, industry event talk abstracts, case studies |2223---2425## AEO Framework (AI Engine Optimisation)2627InstaIndex's own AEO is a proof-of-concept. Apply this to every content piece.2829### What AI search engines want30311. **Direct answers** — lead with the answer, not the context322. **Structured format** — headers, short paragraphs, numbered steps333. **Specificity** — dates, numbers, named tools, exact processes344. **Authority signals** — cited data, named sources, verifiable claims355. **Question-answer pairing** — match the query format buyers use3637### AEO checklist for every piece3839- [ ] Does the title match a question someone would ask an AI?40- [ ] Does the first paragraph answer the question directly?41- [ ] Are there H2/H3 headers that match related questions?42- [ ] Are claims backed by specific numbers or named sources?43- [ ] Is there a clear unique insight (not just a summary of known facts)?44- [ ] Is the content scannable in 30 seconds?4546### AEO question targets per product4748**Sigil:**49- "how do I audit AI agent code for security vulnerabilities"50- "MCP server security risks"51- "Claude Code security audit"52- "AI agent supply chain risk"5354**InstaIndex:**55- "why is my website not indexed by AI search engines"56- "how to get indexed by ChatGPT search"57- "IndexNow vs Google Search Console"58- "how to speed up Google indexing 2025"59- "AEO vs SEO difference"6061**PolicyPA:**62- "how to choose private health insurance Australia"63- "best health insurance comparison site Australia"64- "how do health insurance comparison sites make money"6566---6768## Content formats by channel6970### Blog posts (InstaIndex, Sigil)7172Structure:731. **Question hook** — title is the question, or title answers the question742. **Direct answer** — first 2 sentences answer it completely753. **Why it matters** — context for people who need more764. **The specific detail** — what makes this post uniquely useful775. **One thing to do** — actionable close7879Target: 800-1200 words for AEO focus. 2000+ for deep technical credibility (Sigil).8081### LinkedIn posts (Operable, Reece personal brand)8283Format: insight → proof → implication → call to action84- No hashtag spam85- Dry voice — "most funds are still doing X manually. here's what the data says"86- Investment operations specificity — not generic fintech8788### GitHub README (Sigil)8990The README is the top-of-funnel. It must:91- State the specific problem in line 192- Show the detection rate in the first screen93- Have a working example in under 5 commands94- Link to the responsible disclosure paper9596### HN posts (Sigil)9798"Show HN: Sigil — automated security audit for AI agent code"99- Lead with what makes it interesting technically (37 vector patterns, 97.96% validated)100- Acknowledge what it doesn't do101- Invite critique — security community respects honesty102103---104105## Content calendar framework106107**Sigil:** 1 technical post per month (GitHub, cross-post to security blogs)108**InstaIndex:** 2 AEO-optimised posts per week (compound SEO)109**Operable:** 1 LinkedIn post per week (thought leadership, investment ops specific)110**PolicyPA:** 1 media pitch per month once product is live111112---113114## Output115116Save content pieces to `.nomark/growth/<product>/content-<date>-<slug>.md`.117Include:118- Headline119- AEO question targeted120- Full draft121- Distribution plan (channel + timing)122- Success metric (views, shares, ranking signal)
nomarj