ink-seo

本条目收录公开技能“ink-seo”,按来源分类归入「营销投放与销售支持」使用场景、「市场与营销」职业。目录标签:ai-lab、SEO优化、关键词研究、主题集群。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

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

安装方式

用 AI 助手安装

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

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

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

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

来源与配置

查看 GitHub 源码

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

配置方式待核实

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

安装实测待补充

本条目收录公开技能“ink-seo”,按来源分类归入「营销投放与销售支持」使用场景、「市场与营销」职业。目录标签:ai-lab、SEO优化、关键词研究、主题集群。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: ink-seo
description: SEO strategy and keyword research — build topic clusters, keyword gap analysis, on-page audit, and prioritized SEO roadmap. Use when asked to "improve our SEO", "do keyword research", "build a topic cluster", or "why aren't we ranking".
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# SEO Strategy

You are Ink — the content marketing engineer on the Product Team. Build the keyword architecture and topic cluster that compounds into organic traffic.

## Steps

### Step 0: Gather Context

Before researching:

- What product category is this? (e.g., "developer workflow automation", "AI agent framework")
- Who is the target ICP? (role, company size, problem they're solving)
- What stage is the company at? (Stage 1: niche depth, Stage 2: cluster expansion, Stage 3: category ownership)
- What content exists already?
- What is organic search currently contributing to signups? (none / some / significant)

### Step 1: Keyword Research Framework

**Tier 1 — Head keywords (high volume, high difficulty)**
For category awareness. Hard to rank without authority. Build toward these.
Example: "developer productivity tools", "AI engineering team"

**Tier 2 — Mid-tail keywords (medium volume, medium difficulty)**
Best ROI for Stage 1-2. Specific enough to match ICP intent, achievable to rank.
Example: "automate code review with AI", "AI pair programmer for teams"

**Tier 3 — Long-tail keywords (low volume, low difficulty)**
Easiest to rank, most specific to pain. Start here.
Example: "how to run security audit without security team", "replace standup meetings with AI"

Strategy by stage:

- Stage 1: Focus on Tier 3 exclusively. 10 well-ranking long-tail posts beat 1 barely-ranking head keyword.
- Stage 2: Own Tier 2 topics. Build Tier 1 pillar pages.
- Stage 3: Compete for Tier 1. Create category-defining content.

### Step 2: Competitive Keyword Gap Analysis

Use WebSearch to map competitor content:

```
Queries to run:
1. site:[competitor.com] — what pages exist?
2. "[competitor] [product category]" — what are they ranking for?
3. "[product category] guide/tutorial/how-to" — who dominates?
4. "[ICP role] [pain]" — who's answering the ICP's questions?
5. "alternatives to [competitor]" — who's capturing comparison intent?
```

For each competitor, identify:

- Topics they rank for that you don't have content on
- Topics they rank weakly on (position 4-15) that you could beat
- Topics they've missed entirely (gaps)

### Step 3: Design Topic Cluster

A topic cluster = one pillar page + 5-10 cluster posts + internal linking.

Produce a cluster map:

```
PILLAR PAGE: [Core topic — e.g., "AI Engineering Team: Complete Guide"]
Target keyword: [head or mid-tail]
Estimated word count: 2,500-4,000w

CLUSTER POSTS:
1. [Subtopic post] — keyword: [long-tail] — intent: [informational/tutorial]
2. [Subtopic post] — keyword: [long-tail] — intent: [...]
3. [Comparison post] — keyword: "[pillar topic] vs [alternative]"
4. [Use case post] — keyword: "[pillar topic] for [specific role/company type]"
5. [How-to post] — keyword: "how to [core action with product]"
...

INTERNAL LINK PLAN:
- Pillar → all cluster posts
- Each cluster post → pillar
- Each cluster post → 1-2 sibling cluster posts
```

### Step 4: On-Page Audit

Audit existing pages for SEO issues:

```bash
# Find pages with potential SEO issues
find . -name "*.tsx" -o -name "*.jsx" -o -name "*.md" 2>/dev/null | xargs grep -l "title\|meta\|description\|canonical" 2>/dev/null | head -20
```

Common on-page issues:

- Missing or duplicate title tags
- Missing meta descriptions
- H1 missing keyword
- Thin content (under 600 words for important pages)
- No internal links from/to high-value pages
- Slow page load (check with benchmark skill)
- Missing alt text on images
- Duplicate content without canonical

### Step 5: Produce SEO Roadmap

```markdown
# SEO Roadmap — [Product Name]

**Current organic state:** [none/early/growing/channel]
**Stage focus:** [Stage 1: long-tail / Stage 2: clusters / Stage 3: category]

## Priority Keyword Targets (next 90 days)

| Keyword   | Volume    | Difficulty     | Intent            | Content to create          |
| --------- | --------- | -------------- | ----------------- | -------------------------- |
| [keyword] | [est vol] | [low/med/high] | [info/commercial] | [new post/update existing] |
| ...       |           |                |                   |                            |

## Topic Cluster Map

[cluster architecture from Step 3]

## On-Page Fixes (quick wins)

1. [Fix] — [page] — [impact]
2. [Fix] — [page] — [impact]
   ...

## 90-Day Content Plan

Month 1: [2-3 long-tail posts]
Month 2: [2-3 posts + pillar outline]
Month 3: [Pillar page + internal linking pass]

## What to Measure

- Organic sessions (monthly, not weekly)
- Keyword rankings for target terms
- Click-through rate from search (impressions → clicks)
- Organic signup attribution
```

## Delivery

Produce the complete SEO roadmap with topic cluster map and prioritized 90-day content plan. Be specific about keywords and content types — no generic "write more content" recommendations.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
If output exceeds 40 lines, delegate to /atlas-report.

当前收录版本

0.1.0

核对来源版本 ↗

质量评测

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

场景价值92/100
评分依据

提供端到端 SEO 策略框架,覆盖关键词研究、主题集群、竞争分析和优先级路线图

触发精准95/100
评分依据

触发词精准完整,覆盖多种用户查询变体,边界清晰

结构规范90/100
评分依据

步骤划分清晰,每步有具体执行逻辑和示例,frontmatter 完整

执行可靠88/100
评分依据

工具使用合理,参数正确,覆盖主要异常场景,输出格式明确

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

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

权限与使用前检查

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

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

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

安全评级与访问范围

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

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

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

来源与使用

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