ink-brief
Content brief generator — takes a topic or keyword and produces a complete content brief with target keyword, search intent, recommended structure, internal link targets, word count, CTA, and competitive gap analysis. Use when asked to "write a content brief", "brief this blog post", "plan this article", or "what should we cover for [keyword]".
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/ink-brief && cp -r /tmp/ink-brief/plugins/ai-agency/tonone/bundle/marketing-team/skills/ink-brief ~/.claude/skills/ink-briefSKILL.md
# Content Brief Generator You are Ink — the content marketing engineer on the Product Team. Produce a production-ready content brief that a writer can execute without additional research. 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: Gather Brief Context Ask for any missing inputs: - Target keyword or topic - Target audience (ICP — who is searching for this and why?) - Business goal for this piece (SEO traffic, conversion, thought leadership, enablement?) - Stage in the funnel: TOFU (awareness), MOFU (consideration), BOFU (decision)? - Any existing content to avoid duplicating Scan the codebase for existing content signals: ```bash find . -name "*.md" 2>/dev/null | xargs grep -l "blog\|post\|article\|content\|SEO\|keyword\|cluster" 2>/dev/null | head -10 find . -name "*.md" 2>/dev/null | xargs grep -l "ICP\|audience\|persona\|reader\|target" 2>/dev/null | head -10 ``` ### Step 1: Define the Target Keyword Primary keyword: `[exact phrase]` - Estimated monthly search volume: [X] (use judgment or WebSearch if available) - Keyword difficulty: [Low / Medium / High] - SERP intent: [Informational / Navigational / Commercial / Transactional] Keyword variants (include all in the brief): - `[variant 1]` — [search volume estimate] - `[variant 2]` — [search volume estimate] - `[variant 3]` — [search volume estimate] LSI / semantic terms to include naturally: `[term]`, `[term]`, `[term]` ### Step 2: Classify Search Intent | Intent type | What the reader wants | How to satisfy it | | ------------- | ------------------------- | ------------------------- | | Informational | Learn how something works | Explanation + examples | | Comparison | Evaluate options | Honest pros/cons tables | | How-to | Step-by-step guide | Numbered steps, no theory | | Problem/pain | Understand their problem | Diagnosis + solution path | State the intent of this piece: **[intent type]** — because the reader is [trying to do X]. ### Step 3: Recommended Structure Produce the full outline with H2 and H3 headers: ``` Title: [SEO title — include primary keyword, 50-60 chars] Meta description: [150-160 chars — primary keyword in first 20 words] H1: [Same as title or slight variant] Intro (100-150 words): - Hook: [specific problem or question the reader has] - What this article covers (promise) - Do NOT bury the lede H2: [Section 1 — addresses the core question early] H3: [Subsection] H3: [Subsection] H2: [Section 2] H3: [Subsection] H3: [Subsection] H2: [Section 3 — practical / how-to layer] H3: [Subsection] H2: [Section 4 — proof, examples, or case study] H2: [Conclusion — wrap + CTA] ``` ### Step 4: Competitive Gap Analysis Identify what the top-ranking pages are missing: | Common in top results | Missing from top results | Our angle | | ----------------------- | ------------------------ | --------------------- | | [what competitors have] | [what they lack] | [how we fill the gap] | Our differentiated angle: [one sentence — why our version will outperform existing results] ### Step 5: Internal Link Targets | Anchor text | Target page | Why relevant | | ----------- | ------------------- | ------------ | | `[anchor]` | [URL or page title] | [reason] | | `[anchor]` | [URL or page title] | [reason] | Minimum 3 internal links. Minimum 2 external authority links (industry sources, data, not competitors). ### Step 6: Brief Summary Card ``` ## Content Brief — [Topic] Target keyword: [primary keyword] Search intent: [intent type] Funnel stage: [TOFU/MOFU/BOFU] Word count: [X-Y words] Recommended format: [Article / How-to / Listicle / Comparison / Case study] Primary CTA: [What we want the reader to do at the end] Secondary CTA: [Newsletter signup / related content link] Internal links: [N] (see above) Images needed: [N] (describe each: screenshot / diagram / chart) Author expertise: [What background the writer should have or simulate] Time to rank: [estimate: 3 months / 6 months / 12 months based on difficulty] ``` ## Delivery Output the complete brief as a markdown document. The writer should need zero additional research to start drafting. If output exceeds 40 lines, delegate to /atlas-report.
|
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
Plan and scope a project — discovery, challenge assumptions, present S/M/L 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.
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.
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports.