agentleFS
Sign inStart free
powerczukpowerczuk/seo-machine/skills/research/SKILL.md

research

Skill0 starsChanged 2 months agoMITView on GitHub

Keyword research, SERP analysis, competitive gaps, recommended content architecture, and draft meta elements for a topic.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文，过滤相关性，auto-ingest 高优先级论文，检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门：Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • truongtv22Skill

    Problem-Solving Techniques

    Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

    Also in 5 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 43 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • +5 more from Lambenthan
  • +1 more from skyllwt

The file

Create a free account to mount
Files
SKILL.md

/research — Keyword research & SERP analysis

Target: $ARGUMENTS

Method: ${CLAUDE_PLUGIN_ROOT}/skills/seo-fundamentals/references/keyword-research-framework.md. Numbers and targets: ${CLAUDE_PLUGIN_ROOT}/skills/seo-fundamentals/references/scoring-spec.md. If SEO tools are connected (Ahrefs, Semrush, Similarweb, DataForSEO, GSC via MCP), pull volume, difficulty, and positions from them and say which tool the numbers came from; otherwise label every volume/difficulty as an estimate.

Process

  1. Keyword discovery — variations, long-tail (3–5 words), questions (how/what/why), commercial modifiers (best/vs/review), semantically related terms. Identify the primary entity behind the keyword (the Knowledge Graph entity the page will be about).
  2. SERP analysis (top 10 for the primary keyword) — content types, length range and median, topics every result covers (must-haves), topics some cover (differentiators), topics none cover (information-gain candidates), SERP features present (snippet format, PAA, images, video, AI Overview) and who owns them.
  3. Competitive gaps — underexplored angles, outdated data in competitors, missing formats (tables, templates, tools), weak sections, missing schema. For the rigorous entity-level version run /entity-coverage.
  4. Intent classification — informational → guide/tutorial; commercial investigation → comparison/review; transactional → landing page; navigational → brand page.

Output

  1. Keyword opportunity table (15–25 rows): keyword · volume (source or "est.") · difficulty · intent · opportunity (high/med/low) · recommended content type.
  2. SERP landscape — feature ownership, length median, structural patterns, differentiation opportunities, whether an AI Overview appears and what it cites.
  3. Competitive gaps — what is missing, why it matters, approach, effort/impact.
  4. Recommended architecture — primary entity, 3 H1 options, H2 outline tagged MUST-COVER / DIFFERENTIATOR / SNIPPET TARGET, target length (SERP median +20–30%), snippet strategy, schema types.
  5. Meta preview — 3 title options (50–60 chars, entity front-loaded, click copy) and 3 descriptions (150–160 chars, value + CTA); final polish belongs to /meta-tags.

Offer next: /entity-coverage (entity matrix + information gain), /content-brief, /write-seo, /topic-clusters.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free