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의 Skill(지시 묶음) 1개, 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질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.