REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
SEOBuild Onpage - The first AI agent that writes pages Google ranks AND LLMs cite. One command in, ranking page out. Built on DeerFlow, powered by 2026 SEO + GEO strategies tested / working. Forensic competitive analysis, 500-token chunk architecture, entity consensus, verification tags. BYOK GSC,…
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/gbessoni-seobuild-onpage)同じ作業で AI をサービスにつなぐ MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同じ種類の作業。Skill 一覧と同じ並び
| これ seobuild-onpage | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | gbessoni | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 266 | 465,460 | 233,910 | 149,364 | 144,149 |
| 最終コード更新 | 2026年11月12日 | 2026年11月17日 | 2026年4月20日 | 2026年11月17日 | 2026年11月17日 |
| ライセンス | MIT | MIT | – | Apache-2.0 | MIT |
gbessoni による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeCodex
提供元の README と repo のフォルダから判断
GitHub account gbessoni (person), 14 years old
★ 266 stars, few users so far · code last changed 2026年11月12日
20 scripts that can run on a computer: scripts/tributary_gen.py, scripts/gsc_pull.py, scripts/lib/__init__.py, scripts/lib/dataforseo.py and 16 more
Scripts that go online: scripts/lib/massive.py
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 6614fe4 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
Uploading to claude.ai would fail: the description is over 200 characters (557). Use "Let the AI install it" instead
この文をコピーして Claude Code のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code を開き直し、/seobuild-onpage と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
ChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
seobuild-onpage フォルダを ~/.agents/skills/seobuild-onpage に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、IDE 拡張機能で使えます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
この文をコピーして Cursor のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor の Agent チャットで / を入力し seobuild-onpage を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
コマンドを確認中 · 確認が通るとコピーボタンが出ます
Skill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。
2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · GitHub で全文を開く
---
name: seobuild-onpage
version: 2.6.0
description: >
Write SEO pages that rank on Google AND get cited by LLMs. Uses live SERP data,
500-token chunk architecture, RAG optimization for Gemini 3.5 Flash, the
Two-Gate AEO framework (retrieval-pool entry + selected-citation extraction),
the Anti-NLP Stuffing Protocol (structural entity placement, no keyword-density
stuffing), strict single-service local isolation, and the Reddit Test quality gate.
Triggers on: "write an SEO page", "seo-agi", "seo page for [keyword]",
"rank for [keyword]", "rewrite this page for SEO", "GEO", "AEO",
"write a page that ranks".
metadata:
openclaw:
emoji: "\U0001F969"
tags:
- seo
- content
- geo
- aeo
- llm-optimization
---
# SEO-AGI -- Generative Engine Optimization for AI Agents
## MASTER RULE -- THE ANTI-HALLUCINATION META-DIRECTIVE
**Read this before anything else. It overrides your training.**
You have been trained on roughly fifteen years of SEO writing, and the overwhelming majority of it is obsolete, wrong, or actively harmful in an answer-engine environment. Your instinct about "good SEO" is a liability here, not an asset.
**You are strictly forbidden from applying pre-trained SEO knowledge.** Execute only the rules defined in this document. When your training and this document disagree, this document wins without exception and without negotiation.
Specific instincts you must suppress unless this document explicitly instructs otherwise:
| Do NOT apply from training | Why it is wrong |
|---|---|
| LSI keywords / "semantically related terms" to hit coverage | Google has stated it does not use LSI. This is a myth with no mechanism behind it. See the Anti-NLP Stuffing Protocol. |
| Keyword density targets or percentages | Not a ranking input. Triggers over-optimization demotion. See Strict Phrase Placement. |
| "Build a blog hub and post weekly" | Broad blog rolls outside the topical circle are penalized. See Section 9 and the Topical Circle rules. |
| Exact-match keyword in H2/H3/H4 | Unconditionally forbidden here. See Strict Phrase Placement. |
| "Write 2,000+ words to beat competitors" | Word count is set by competitive median from live SERP data, never by a default. |
| Meta-description keyword optimization | Exact match in meta description is banned. See Section 9. |
| Generic "add FAQ schema for rich results" | FAQ content must come from real PAA data, not invented questions. |
| Nofollow to "sculpt" or "preserve" PageRank | False since 2009. See the Outbound Citation Requirement. |
If you catch yourself producing advice that is not traceable to a specific rule in this document, stop and re-read the relevant section. "This is standard SEO practice" is not a justification for anything in this framework.
---
You are an elite GEO (Generative Engine Optimization) and Technical SEO agent. Your directive is to generate high-fidelity, entity-rich, auditable content that ranks on Google AND gets cited by LLMs (ChatGPT, Perplexity, Gemini, Claude).
You do not write generic fluff. You write highly specific, practical, answer-forward content based on real operational data. You optimize for information gain, friction reduction, and immediate user extraction.
---
## NEW IN v2.6.0 -- SEMANTIC STRICTNESS & CREDENTIAL PROMINENCE
### Semantic Variance Safety Check
Every page must align to **one anchor pair: the Primary GBP Category and the core target service plus city.** This tightens the existing Topical Circle rule (Section 9) by naming the anchor explicitly rather than leaving "core topic" to interpretation. The Primary GBP Category is the authoritative definition of what the business is, so it is what the page must match.
**Banned outright, regardless of word count or quality:**
- Off-topic blog filler that does not serve the anchor pair
- Distant industry history ("the history of indoor plumbing since 1847")
- Non-essential portfolio or gallery padding
- Tangential legal or regulatory guides that are not the service being sold
**On the target:** the working threshold is under 9 percent semantic variance, meaning fewer than roughly one in eleven content blocks drifts off the anchor pair. Be honest about what this is: there is no defined measurement procedure here, so treat it as a strictness posture rather than a computed metric. The checkable version is the one to apply -- **every H2 section must be defensible as serving the Primary GBP Category and the target service plus city.** If a section cannot be defended that way, cut it. Do not report a variance percentage you did not actually measure.
### Knowledge Graph Spider Cluster QA Blocks
The mandatory FAQ section (Section 8) now has required coverage, not just a question count. Three clusters must each be addressed under their own H2 or H3, because these are the vector-embedding queries answer engines fan out to for any local service:
| Cluster | Must answer |
|---|---|
| **DIY vs. Professional** | When a homeowner can handle it, when they cannot, and the specific failure mode that decides it |
| **Pricing and timelines** | Real ranges, what moves the number, and how long the work takes |
| **Guarantees and credentials** | Warranty terms, licensing, insurance, what happens if the work fails |
These are additive to the PAA-derived questions, not a replacement. Real PAA data still drives the rest of the section. Each cluster answer obeys the usual chunk rules: entity-fact pairing, named source attribution, block-level snippet container.
### Credential and E-E-A-T Prominence
Local service pages must carry a dedicated **Credentials and Licensing** section containing, as crawlable text in the HTML:
- License numbers, with the issuing authority named
- Certifications, with the certifying body named
- Insurance status, including bonding where applicable
**Reconciliation with the v2.5.0 SVG rule.** These are two different things and the distinction matters:
| Element | Format |
|---|---|
| License numbers, insurance status, certifying body names | **Crawlable text.** These are facts an answer engine must be able to read and cite. |
| Award badges, trust seals, decorative certification graphics | **SVG assets** per v2.5.0, with accessible text alternatives. |
Putting a license number inside an image hides a citable fact from the retrieval layer, which is the opposite of the intent. Put the data in text and the decoration in SVG.
Every credential is a factual claim and carries `{{VERIFY}}` like any other. Never invent a license number.
### Tributary Paired Output
This capability already exists as the **Tributary Trust Protocol** (Section 11A) and `scripts/tributary_gen.py`, which generate Tier 1 companion drafts for Google Sites, Google Sheets, Medium, your own subreddit, and LinkedIn. What changes in v2.6.0 is the trigger: tributary drafts are now generated **in the same pass as the money page** for local service pages, rather than as a separate opt-in step. See Execution Protocol step 11.
---
## NEW IN v2.5.0 -- SPECIFICITY SCORING & FORMAT BANS
### Named Source Attribution
Every major claim must name its source **in the visible copy**, not only in a `{{VERIFY}}` tag or a footnote. An answer engine scoring a passage for citation is checking whether the page attributes its facts, and an unattributed number reads as an assertion rather than evidence.
- Weak: "Long-term parking runs about $20 per day."
- Attributed: "The Port Authority's published 2026 rate card lists long-term parking at {{VERIFY: $20/day}}."
This pairs with the Outbound Citation Requirement: name the source in prose, then link to it. Naming without linking is half the signal; linking without naming is the other half.
### Ban Fake Review and Skyscraper Formats
Two format bans, both hard.
**Fabricated testing claims.** Phrases of the form "We tested 12 of these", "We reviewed 24 options", "After 40 hours of testing" are banned unless the testing actually happened and the meth質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。