SEO 内容简报规划指南

依据主题、关键词、受众和业务目标,整理搜索意图、文章结构、竞争差距、内链方向、字数建议与行动号召。适合规划博客或营销内容;如需扫描本地资料,应先确认检索范围和文件权限,并人工核对来源与事实。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "ink-brief":https://skillpi.com/zh/skills/deepskill-6cfa4e60e869bc54826f99e9cb089d8cfdeaa246f6e2aa944a3165998f5a075b。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/marketing-team/skills/ink-brief/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/bundle/marketing-team/skills/ink-brief --skill ink-brief
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

依据主题、关键词、受众和业务目标,整理搜索意图、文章结构、竞争差距、内链方向、字数建议与行动号召。适合规划博客或营销内容;如需扫描本地资料,应先确认检索范围和文件权限,并人工核对来源与事实。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: ink-brief
description: 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]".
allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# 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.

当前收录版本

0.1.0

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值65/100
评分依据

提供完整的内容简报生成功能,适用于 SEO 和内容营销场景

触发精准85/100
评分依据

触发词覆盖多种变体,边界清晰

结构规范90/100
评分依据

Phase/步骤清晰,包含完整的执行流程

执行可靠85/100
评分依据

工具来源明确,参数使用正确

证据可验 (前四项均值)81/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。