本文へ移動
cccskills
無料GitHub で公開

ink-recon

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

apex

無料

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

apex-gate

無料

Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

apex-plan

無料

Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

tonone-ai のスキルをすべて見る

このスキルの問題を報告する