repo-aeo — Repo Discoverability Kit (RDK)
English | Русский
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add repo-aeo-mcp -- npx -y repo-aeo-mcp@1.1.2รันในเทอร์มินัล
{ "mcpServers": { "repo-aeo-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
English | Русский
MCP server for continuous repository discoverability monitoring: npm search score, GitHub visibility signals, llms.txt freshness and site checks. Read-only by default.
Make any repository, npm package and docs site findable and recommendable for humans, AI agents and search engines.
RDK scores how discoverable your repository is, fixes the parts that can be fixed automatically, and keeps it from regressing in CI. It is the tool you point at a repo that is good but invisible.
The audit runs 44 checks in under 300 ms offline on this repository
(measured with rdk audit --format json, duration_ms field) and carries 0
runtime dependencies, so npx stays fast and the supply chain stays small.
Prerequisites: Node.js >= 18
# 1. add RDK to your repository
npm install --save-dev repo-aeo
# 2. scaffold the config and the missing files
npx repo-aeo init --apply
# 3. see the score and the prioritised fix list
npx repo-aeo audit
# 4. run the test suite
npm test
Two-minute setup for a repository you do not own yet: clone it, run
npx repo-aeo init --apply, then npx repo-aeo audit. Everything the CLI writes is a
reviewable diff — it never publishes, tags or force-pushes. The one exception
lives in CI: the opt-in autofix job force-pushes its own dated
rdk/autofix-<date> bot branch and opens a reviewable PR.
You fork nothing and install nothing permanently. Pick the surface that matches how you work — each pulls the engine on demand:
Commit to it and exactly two files ever appear in your repository: the
workflow above and .discoverability/project.yml, the generated source of
truth for your metadata. The two RDK repositories (engine and the action
wrapper) stay ours — they are the factory, not a dependency you carry.
You shipped a good package, but nobody finds it: npm search buries it, AI assistants recommend the incumbents, and the README explains the philosophy for 90 lines before the first runnable example.
Fixing that once is the easy half. The hard half is keeping it fixed: six months later a contributor's PR "tidies up" the README with a banner and a table of contents, the quickstart sinks below line 60, the tests stay green — and the package quietly disappears from search results and AI answers again. Nobody notices, because nothing in CI watches discoverability.
RDK makes it a tested property: audit locally, gate in CI on every pull request.
Three layers, because a one-off script is not enough:
npx repo-aeo init # create .discoverability/project.yml + minimal safe files
npx repo-aeo audit # score 0-100 + findings (json | markdown | github-comment)
npx repo-aeo fix # preview safe autofixes; --apply to write them
npx repo-aeo npm-surface # package.json publish surface + npm pack --dry-run
npx repo-aeo github-sync # push description/homepage/topics (needs --apply --ack --reason --plan-digest)
npx repo-aeo channels # list every distribution channel, applicability and next action (read-only)
npx repo-aeo submit # submit to a distribution channel: --channel <id> (needs --apply --ack --reason --plan-digest)
npx repo-aeo track # campaign dashboard: live status, adopt existing PRs, sync the ledger
npx repo-aeo skill install # link the agent skill into OpenCode/Claude/Codex skill dirs
npx repo-aeo-mcp serve # the same engine as an MCP server: 9 read-mostly tools
claude mcp add rdk -- npx repo-aeo-mcp serve
docker run -i repo-aeo-mcp serve
Every write operation requires an explicit flag. audit is read-only and works
offline; --online adds link checks and live GitHub metadata.
$ npx repo-aeo audit # measured on fixtures/demo-repo, offline
score: 52/100 (grade F) · checks: 20/43 passed · findings: 10 error, 13 warn, 10 info (19 autofixable) · mode: offline (use --online for link + GitHub checks)
$ npx repo-aeo fix --dry-run # review the diff
$ npx repo-aeo fix --apply # 16 files: README sections, AGENTS.md draft, llms.txt, CITATION.cff, ...
$ npx repo-aeo npm-surface --pack
| exports | conditions: import, require; subpaths: . |
⚠️ present in the repo but not in the tarball: llms.txt
# .github/workflows/rdk.yml — in YOUR repository
- uses: actions/checkout@v4
- uses: WhiteBite/rdk-discoverability@v1
with:
min_score: ${{ vars.RDK_MIN_SCORE || 0 }}
GitHub downloads the action, the action pulls the engine from npm — nothing to install or fork. This is the same action this repository's own CI runs.
The CLI itself never force-pushes; the workflow's opt-in autofix job (gated by
safety.allow_autofix) force-pushes only its own dated rdk/autofix-<date>
bot branch and opens a PR for review.
$ npx repo-aeo-mcp score
Discoverability score: 100/100 (grade A)
checks passed: 44/44 - errors 0 - warnings 0 - autofixable 0
trend: no history yet
The first run records the score; every subsequent run prints the delta instead
(for example trend: 90 -> 96 (up)).
skills/repo-discoverability/SKILL.md → description triggers on
"make repo discoverable", "add topics", "improve README for users and agents",
"prepare npm metadata", "generate AGENTS.md", "optimize for AI search",
"run a distribution campaign", "submit to awesome lists"
AGENTS.md, llms.txt and llms-full.txt for a repo.package.json metadata, exports and tarball contents before an npm release..discoverability/submissions.json.Six weighted axes, renormalised over the axes that apply to your project:
Grades: A ≥ 90 · B ≥ 80 · C ≥ 70 · D ≥ 55 · F below. Full model:
docs/scoring.md.
.discoverability/project.yml feeds the
README, AGENTS.md, llms.txt, npm metadata and GitHub topics — no drift
between them.Most tools in this space anchor to a served website (llms.txt validators, GEO graders, Lighthouse), a published package (npms.io) or a docs build (framework generators). RDK anchors to the git working tree: it audits and repairs the repository itself, before anything is served or published.
Orthogonal by design: Scorecard grades how safe a repo is to consume, community standards grade human onboarding, packers serialize content, DeepWiki hosts a generated wiki and CHAOSS measures community behaviour over time. None of them repairs the repository; RDK does not replace any of them.
llms-full.txt files or Cloudflare's per-product variants.--online probe, not a full served-vs-file diff
like llms-txt-check..github/, root or docs/; RDK's checks
look at fixed paths.Consumed on demand by agents: the spec states the file is "used on demand, when an agent needs information about a topic while assisting a user", for inference rather than training. OpenClaw ships llms.txt discovery as default agent behavior since 2026-02; Chrome's Lighthouse Agentic Browsing scores sites on it; Cloudflare, Mintlify, GitBook, Wix and Yoast publish or generate it as the ecosystem convention, and tools like mcpdoc feed it to IDE agents.
What it does not buy: none of GPTBot, ClaudeBot, PerplexityBot,
Google-Extended or Bingbot documents fetching /llms.txt during training or
indexing crawls — their official bot pages contain no mention of it. The
defensible value is inference-time agents, repo-reading tooling and the
discoverability audits above, not crawler traffic.
rdk fix twice produces no diff) is a tested gate,
where codemod ecosystems treat it as folklore.Actively developed. v0.1 ships the CLI, the skill, the Action and the MCP server. IDE packaging is next (roadmap issues).
MIT — see LICENSE. Citation metadata: CITATION.cff.
MCP server for continuous repository discoverability monitoring: npm search score, GitHub visibility signals, llms.txt freshness and site checks. Read-only by default.
{ "mcpServers": { "repo-aeo-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Repo Aeo ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 MCP server for continuous repository discoverability monitoring: npm search score, GitHub visibility signals, llms.txt freshness and site checks. Read-only by default.