repo-map

Map canonical ownership and distribution across four Arth repositories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill repo-map-arthtech-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-map
Source: https://github.com/ArthTech-AI/Marketplace-extensions/tree/main/skills/repo-map
Command: npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill repo-map-arthtech-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes confusion about where Arth content belongs by showing the canonical ownership map for the four related repositories and their distribution roles.

Core Features & Use Cases

  • Repository Boundary Guidance: Explains which repo owns agents, skills, hooks, bundles, customer docs, marketplace mirrors, and the engine container.
  • Cross-Repo Decision Support: Helps you choose the correct place to edit install steps, release content, docs, or engine behavior without breaking source-of-truth rules.
  • Use Case: When you need to update an install flow, bundle, or doc reference, this Skill tells you whether the change belongs in claude-agents, arthai-marketplace, arthai-plugins, or arth-intelligence.

Quick Start

Ask for the repo map section you need, such as the install flow or docs ownership, before making any cross-repo change.

Frequently Asked Questions about repo-map

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

FAQPage Schema
Where do Arth install flows and documentation references belong across multiple repositories?▼

Arth repository mapping identifies the source-of-truth boundaries for install flows and documentation, directing edits to the correct repository among claude-agents, arthai-marketplace, arthai-plugins, or arth-intelligence to maintain canonical ownership.

How do I know which repository owns engine code and bundles in the Arth ecosystem?▼

Repository mapping clarifies ownership boundaries, specifying which repository controls engine containers, bundles, and distribution roles so you can apply cross-repo changes without violating source-of-truth rules or breaking gh-pages propagation.

What is the correct way to update cross-repo documentation for Arth projects?▼

Cross-repo documentation updates require checking the canonical ownership map first to determine whether changes belong in arthai-marketplace, arthai-plugins, or arth-intelligence, ensuring docs are edited at their source before propagation.

Can I edit Arth skills and hooks in any repository without breaking distribution?▼

No, editing skills and hooks outside their source-of-truth repository breaks distribution. Repository mapping identifies the canonical owner for agents and skills, ensuring edits propagate correctly through gh-pages and bundle distribution channels.

Why does my Arth bundle update not reflect after cross-repo changes?▼

Bundle updates fail when edited outside the source-of-truth repository. Repository mapping identifies the correct ownership boundaries for bundles and engine code, preventing propagation issues across claude-agents and related repositories.

When do I need repository mapping for Arth deployment and architecture decisions?▼

Repository mapping is needed before making any cross-repo change involving install steps, release content, docs, or engine behavior, ensuring updates target the correct repository and respect architectural boundaries across the four Arth repositories.