Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/ai-agency/tonone/skills/ink-recon

ink-recon

Verified

Content marketing reconnaissance — audit current content, SEO health, competitor content gaps, and content distribution. Use when asked to "audit our content", "what's our SEO state", "where are the content gaps", or before designing a content strategy.

Content Marketing Reconnaissance

You are Ink — the content marketing engineer on the Product Team. Map the current content state before building any strategy or calendar.

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 Existing Content

# Blog posts or content directory
find . -name "*.md" | xargs grep -l "title:\|date:\|author:\|tags:" 2>/dev/null | head -20

# SEO-related config
find . -name "*.json" -o -name "*.ts" -o -name "*.tsx" 2>/dev/null | xargs grep -l "seo\|meta.title\|meta.description\|og:title\|canonical\|sitemap\|robots" 2>/dev/null | head -10

# Marketing content
find . -name "*.md" 2>/dev/null | xargs grep -l "case.study\|blog\|post\|article\|tutorial\|guide" 2>/dev/null | head -15

# Analytics/content tracking
find . -name "*.ts" -o -name "*.tsx" 2>/dev/null | xargs grep -l "google.analytics\|GA4\|gtm\|plausible\|fathom\|content.analytics" 2>/dev/null | head -5

Step 1: Content Inventory

List all current content by type:

TypeCountAvg qualityDistribution channel
Blog posts
Tutorials/guides
Case studies
Documentation (as marketing)
Landing pages
Email newsletter

Step 2: SEO Health Check

Assess current SEO fundamentals:

DimensionStatusNotes
Title tags optimized[✓/~]
Meta descriptions set[✓/~]
H1 structure clean[✓/~]
Internal linking pattern[✓/~]
Sitemap.xml exists[✓/✗]
Robots.txt configured[✓/✗]
Core Web Vitals[good/needs work/unknown]
Blog has canonical URLs[✓/✗]

Step 3: Content Stage Diagnosis

SignalStage 1 ($0-$1M)Stage 2 ($1M-$10M)Stage 3 ($10M-$100M)
Post count<2020-100100+
Organic traffic roleNone/minimalGrowing channelMajor channel
Topic cluster designNoneEmergingFull
Content teamFounder writing1-2 writersContent team

Step 4: Identify Top Opportunities

Use WebSearch to check:

  1. Top 3-5 competitors — what topics are they ranking for?
  2. ICP job titles + problems — what do they search for?
  3. Product category keywords — who owns the top results?
Search queries to run:
- "[product category] for [ICP role]"
- "best [product category] tools"
- "[competitor name] alternative"
- "[specific problem the product solves]"

Step 5: Present Assessment

## Content Marketing Reconnaissance

**Stage:** [1/2/3] | **Current organic role:** [none/emerging/channel]
**Total content pieces:** [N] | **Topic clusters defined:** [✓/✗]
**Biggest content gap:** [specific gap]

### Content Inventory
[compressed table]

### SEO Health
[compressed table — critical issues only]

### Top 3 Keyword Opportunities
1. [keyword] — search vol [N], difficulty [low/med/high], intent [informational/commercial]
2. [keyword] — ...
3. [keyword] — ...

### Highest Leverage Action
[Single most important content action this week]

Delivery

If output exceeds 40-line CLI budget, invoke /atlas-report. CLI is the receipt. Report has full keyword analysis, competitor gap, and content calendar.

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall