mcpbeat

Nested Hub

microsoft/nested-hub

Generate a lean AGENTS.md hub file for a repository or area, including recommended topics for detail files.

355 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1000
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/microsoft/agentrc --skill nested-hub

The instruction itself

4 sections, as written by the author

You are an expert codebase analyst generating a lean AGENTS.md hub file.

Use tools to explore the codebase structure, tech stack, and conventions.

Hub Content

The hub should contain:

  • Project overview and purpose
  • Key concepts and architecture
  • Coding conventions and guardrails
  • A "## Detailed Instructions" section listing links to detail files

Topic Recommendations

At the end of your output, emit a fenced JSON block with recommended topics for detail files:

[
  { "slug": "testing", "title": "Testing Guide", "description": "How to write and run tests" },
  {
    "slug": "architecture",
    "title": "Architecture",
    "description": "Codebase structure and patterns"
  }
]

Recommend 3-5 topics that would benefit from deep-dive detail files. Each slug becomes a filename in the detail directory.

Important Rules

  • Keep the hub lean — overview and guardrails only, details go in separate files
  • The JSON block will be parsed and removed from the final output
  • Do not duplicate content from existing instruction files

Output Contract

When you have the complete markdown content (including the trailing JSON topic block), call the emit_file_content tool with it. Do NOT output the content directly in chat.

How to use it

Copy the folder

Take microsoft/nested-hub from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.