mk.repos

Catalog and audit repositories by correlating GitHub data, local paths, and repos.json.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mayknxyz/my-kit --skill mk-repos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mk.repos
Source: https://github.com/mayknxyz/my-kit/tree/main/kit/.claude/skills/mk.repos
Command: npx skills add https://github.com/mayknxyz/my-kit --skill mk-repos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cataloging and auditing repositories and their MCP servers to keep a centralized, searchable inventory across local disks and GitHub.

Core Features & Use Cases

  • Auto-detects tech stacks and per-repo MCP server configurations and stores them in a shared catalog.
  • Cross-references GitHub repos, local disks, and the repos.json catalog to surface uncataloged and stale entries.
  • Enables quick actions to add or remove MCP servers from a repo and maintain consistency across the ecosystem.

Quick Start

Catalog a repo by running /mk.repos.add <repo-name-or-path> to start tracking its MCP servers.

Frequently Asked Questions about mk.repos

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catalog local git repositories and their MCP server configurations?

To catalog git repositories, you correlate GitHub data and local disk paths with a repos.json catalog. This process records auto-detected tech stacks and MCP server configurations into a centralized inventory for quick reference and governance.

What is the best way to audit and detect tech stacks across multiple repositories?

The best way to audit tech stacks is by cross-referencing GitHub repositories and local disks against a repos.json catalog. This auto-detects stack configurations and surfaces uncataloged or stale entries across your ecosystem.

How do I add a new repository to a centralized repos.json catalog?

You add a repository to the repos.json catalog by running an add command with the repo name or local path. The system enforces duplicate checks, resolves local paths, and writes the new entry with its detected MCP servers.

Can I manage template-based MCP server entries for individual repos?

Yes, you can manage per-repo MCP servers by reading and matching .mcp.json files. The system supports both template-based and custom MCP entries, allowing you to add or remove servers to maintain ecosystem consistency.

Why does my repository catalog show stale or uncataloged entries?

Stale or uncataloged entries appear when local disk locations and GitHub data diverge from your repos.json catalog. Auditing cross-references these sources to surface inconsistencies and enforce governance across your inventory.

Do I need a local disk path to track a GitHub repository in the catalog?

Yes, tracking a GitHub repository requires resolving its local disk path to correlate data accurately. The cataloging process cross-references GitHub metadata, local file locations, and the repos.json catalog to maintain a coherent inventory.