content-engine

Generate GTM-calibrated content and distribution plans with SEO and AEO optimization.

5|2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/NOMARJ/sigil --skill content-engine-nomarj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-engine
Source: https://github.com/NOMARJ/sigil/tree/main/packs/business/skills/growth/content-engine
Command: npx skills add https://github.com/NOMARJ/sigil --skill content-engine-nomarj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produces actionable, GTM-aligned content and distribution plans so product and marketing teams can consistently generate SEO- and AEO-optimised outputs that match each go-to-market motion and audience. It reduces guesswork and speeds up content production while ensuring technical accuracy and discoverability for AI search and traditional search engines.

Core Features & Use Cases

  • Content strategy mapping: Maps product GTM motions (developer-led, content-led, community-led, relationship-led) to prioritized content formats and channels.
  • AEO + SEO optimization: Uses an AEO checklist—direct answers, structured format, specificity, authority signals, and question-answer pairing—to craft AI-search-friendly content.
  • Multi-format outputs: Produces blog posts, LinkedIn posts, GitHub READMEs, technical write-ups, HN copy, community replies, and distribution plans with success metrics.
  • Operational outputs: Saves completed pieces and metadata to a reproducible location and enforces target formats and word counts for channel-specific needs.

Quick Start

Create an 800–1200 word AEO-optimised blog post for Sigil that targets "how do I audit AI agent code for security vulnerabilities" and include headline, AEO question target, full draft, distribution plan, and success metric, then save it to .nomark/growth/sigil/content-<date>-audit-ai-agent.md.

Frequently Asked Questions about content-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write AEO-optimized blog posts that rank in AI search results?

AEO-optimized blog posts use an AEO checklist featuring direct answers, structured formatting, specificity, authority signals, and question-answer pairing to target specific AI search queries. This ensures content discoverability for AI search engines and traditional SEO.

How do I align content strategy with different go-to-market motions?

Aligning content strategy with GTM motions requires mapping product motions—developer-led, content-led, community-led, and relationship-led—to prioritized content formats and channels. This matching ensures outputs target the correct audience for each motion.

What is the best way to generate technical READMEs and LinkedIn posts from a GTM spec?

Generating multi-format outputs like GitHub READMEs and LinkedIn posts from a GTM spec involves reading business context, applying channel-specific word counts, and producing distribution plans. This creates tailored technical write-ups and social copy.

Can I produce community posts and HN copy alongside long-form content for developer-led motions?

Yes, producing community posts and HN copy alongside long-form content supports developer-led motions. The workflow generates these formats together while enforcing target formats and saving completed pieces to a reproducible location.

Do I need a GTM spec to start creating content with an AEO checklist?

Yes, a GTM spec and business context are required to start creating content. The process reads this input to calibrate the content strategy, apply the AEO checklist, and output markdown files with headlines, drafts, and success metrics.

Why does my content strategy struggle to match audience intent across multiple channels?

Content strategy struggles to match audience intent when it lacks GTM calibration across developer-led, content-led, community-led, and relationship-led motions. Applying a structured AEO checklist and distribution plan ensures technical accuracy and channel-specific discoverability.