REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Your AI SEO house. Audit your website, write useful content, compare competitors and plan backlinks inside your AI assistant. Free and open source.
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/beyondtahir-beyondseo)同じ作業で 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 一覧と同じ並び
| これ beyondseo | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | beyondtahir | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 270 | 465,460 | 233,910 | 149,364 | 144,149 |
| 最終コード更新 | 2026年11月5日 | 2026年11月17日 | 2026年4月20日 | 2026年11月17日 | 2026年11月17日 |
| ライセンス | MIT | MIT | – | Apache-2.0 | MIT |
beyondtahir による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeClaude (เว็บ/แอป)CodexCursor
提供元の README と repo のフォルダから判断
GitHub account beyondtahir (person) is only 8 months old: take extra care
★ 270 stars, few users so far · code last changed 2026年11月5日
64 scripts that can run on a computer: media/paperworks/source/explainer/assets/gsap.min.js, scripts/backlink_classifier.py, scripts/backlink_sources.py, scripts/build_skill.py and 60 more
Could not check every script (some are too large); read them first
No hooks or writes to machine settings found
Checked automatically from the repo files at commit d9475e6 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
This skill is over 5 MB or 300 files, so we do not build a ZIP. 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 を開き直し、/beyondseo と入力するか関連する作業を頼むと 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
beyondseo フォルダを ~/.agents/skills/beyondseo に置きます
~ はホームフォルダ($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 チャットで / を入力し beyondseo を選ぶ
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: beyondseo
description: Audit websites, apply authorised SEO improvements and plan content, competitors and backlinks with evidence, design checks and optional project monitoring.
metadata:
version: 2.11.0
author: Muhammad Tahir Ashraf — Beyond Tahir
---
# BeyondSEO
Help people understand their website, improve it and see what changed. Use everyday language, explain unfamiliar terms once and connect recommendations to the business goal. Read [the friendly advisor guide](playbooks/core/friendly-advisor.md) for reports, visibility questions and writing help.
## Run in the available host
For an installation request, follow [the host-specific guide](docs/agent-installation.md), including Cursor, Lovable workspace imports and agents managing Vercel projects. Confirm registration in the host's skill list separately from the crawler's runtime check. A format check or successful folder copy is not proof of workspace acceptance. For GitHub DNS or proxy errors, follow that guide’s specific upload and network guidance; report skill registration and live crawler access separately. Report the actual failed operation and error when a save or setup fails. Read [permissions and runtime requirements](docs/permissions.md) for package review and hosted execution. Installation does not authorize a website crawl, account access or publishing.
When the user supplies a Lighthouse JSON report, use [the lab review](docs/operations.md#review-a-saved-lighthouse-report) and distinguish lab data from field data and TBT from INP. When the user supplies a Search Console CSV, follow [search performance review](docs/operations.md#review-search-console-exports) to import it privately, match exact saved page captures where available and compare compatible periods without inventing query-to-page relationships or results. Read [questions and capabilities](docs/questions.md) for introductions. Resolve the skill root from this file. Use the host's available file and shell tools; no particular connector or tool name is required. Check `python3 /absolute/skill/path/scripts/run.py doctor` (Windows: `py -3`) in the actual execution environment before crawling. The launcher supports a local `.venv` or an explicit `--runtime` in a host-approved execution folder. If Python, networking or browser execution is unavailable, use supplied evidence and label the limitation; never simulate a successful crawl. Load only references needed for the request. The native CLI uses no model tokens or API keys; assistant reasoning still uses the host's model.
For Lovable execution, read [the Lovable host guide](docs/lovable.md) for private runtime recovery, bounded captures and project-safe operation.
## Complete audit checklist
Unless the user narrows the scope, complete every stage below and report each as done, partial or failed with its exact error. "Not requested" is not a reason to skip a stage. Reading public pages and running searches needs no extra permission; posting, sign-in and messages stay separately authorised, and a limit on those does not cancel research. Use `python3 <skill>/scripts/run.py` (plus any `--runtime`) where `beyondseo` is not on the path. Check a flag with `--help` before guessing.
```sh
beyondseo doctor
beyondseo crawl URL --include-www --out RUN/site
beyondseo profile --crawl RUN/site --out RUN/business
# Read the packet and write RUN/review.json with natural buyer search_queries.
beyondseo profile --crawl RUN/site --review RUN/review.json --out RUN/business-reviewed
beyondseo entity-review --crawl RUN/site --out RUN/entity
beyondseo discover --queries RUN/business-reviewed/queries.json --target URL --out RUN/discovery
# Crawl each candidate's service, About and Contact pages and review its profile the same way.
# Review about 15 candidates where evidence and the user's limits allow, aiming for five direct competitors.
# Run competitors once, repeating --candidate-profile for every candidate. Do not merge results by hand.
beyondseo competitors --profile RUN/business-reviewed/profile.json --candidate-profile RUN/candidates/a/profile.json --candidate-profile RUN/candidates/b/profile.json --discovery RUN/discovery/discovery.json --out RUN/competitors
beyondseo research-plan --profile RUN/business-reviewed/profile.json --brand NAME --selection RUN/competitors/competitors.json --out RUN/research-plan
# For each cohort site N in the plan, client first (0), with that site's own URL and brand:
beyondseo discover --queries RUN/research-plan/reputation-queries-N.json --target SITE --max-requests 48 --seconds 180 --out RUN/reputation/site-N/discovery
beyondseo backlinks --sources RUN/reputation/site-N/discovery/sources.csv --target SITE --brand BRAND --max-sources 30 --out RUN/reputation/site-N/links
# Write RUN/comparison-input.json as in docs/deep-research.md, listing every cohort site.
beyondseo compare-reputation --manifest RUN/comparison-input.json --out RUN/comparison
beyondseo audit --crawl RUN/site --profile RUN/business-reviewed/profile.json --discovery RUN/discovery/discovery.json --out RUN/audit
beyondseo present --input RUN/report.json --out RUN/report
beyondseo audit-check --run RUN
```
If `doctor` reports that Chromium is denied or unavailable and it cannot be fixed, crawl with `--mode http` instead of repeating failed browser attempts, and state that JavaScript content was not verified. Pass real host search results to `discover --host-results` when available. `audit --offline` and `present --audit` give a website-only export for a focused request or a failed stage; they are not the complete audit. For `present --input`, write the report from all the evidence using [the report layout](docs/branded-reports.md) and `examples/report-content.json`; its summary is limited to 650 characters. Treat profiles and repositories the client controls as owned, never independent proof, and name them with `reputation --related-host` when scoring.
The audit is complete only when the result has a reviewed business profile, the top actions with affected pages, named competitors or the reason none qualified, backlink and reputation evidence or the failed attempts, a 30/60/90-day plan, and the coverage limits. If a stage fails after a real attempt, finish the others and say what is missing. Never present a partial audit as complete. Keep these folder names so `audit-check` can read them. Run it last and fix what it reports. If a stage cannot be done after a real attempt, record `{"stage_name": "what was tried and the exact error"}` in `RUN/stage-notes.json`. Give the user its final status and each stage that is not done, and check every sentence listed under `unattributed_claims_to_review`.
Before writing the report, wait for every command you started to finish, then check each count in the report against the output files. Attribute a website's own claims to the website ("the site describes itself as..."), including titles such as "leading" or "No. 1", unless an independent source supports them. Do not add ratings or percentages that no evidence or stated assumption supports.
## Capability-first execution
At the start of an audit, inspect the host's actual browser, search, shell and file capabilities, whether it is Claude Code, Codex, Kimi Code, Hermes, OpenClaw or Work. Reuse an available permitted browser first for browser-assisted search. Run the native crawler to inspect the target and candidate websites; website reading and search discovery are separate jobs. Native discovery fallbacks serve both backlink and competitor research.
For broad audits, backlink comparisons and requests for deep research, follow [the deep research workflow](docs/deep-research.md). Record the actual host browser/backend and try Google through that permitted surface first, then host search and native fallbacks. Use a reviewed business profile, aim for five supported direct competitors from a broader pool, and apply the same reputation query families and verification budgets to every coho質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。