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