How do I install the Repo Onboarding skill?

Run npx skillmds@latest add ldilov/repo-onboarding in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Repo Onboarding safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Repo Onboarding?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Repo Onboarding free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Repo Onboarding?

ldilov (@ldilov) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Repo Onboarding by ldilov — Agent Skill

Name: Repo Onboarding
Author: ldilov

Repo Onboarding

repository discovery, entrypoint mapping, and fast onboarding for unfamiliar codebases. use when the repo is new, mixed, legacy, monorepo-shaped, poorly documented, or when the next safe step is blocked on understanding layout, ownership, and commands.

ldilov Updated Sep 17, 2026

File contents

Repository Onboarding

Trigger Signals

the repository is unfamiliar, mixed, legacy, or monorepo-shaped
the next safe step is blocked on understanding layout, ownership, or workflow
docs are sparse, stale, or scattered across many entrypoints

Inspect First

repo root files such as README.md, top-level manifests, CI config, container config, and deployment hints
AGENTS.md, .agents/skills/, .specify/, or other repo-native guidance surfaces when present
top-level source, app, package, service, infra, and test directories
CODEOWNERS, contribution docs, issue or PR templates, and other health signals when present

Workflow

identify the repo archetype and dominant implementation surfaces
map build, test, run, deploy, and validation entrypoints
infer ownership, boundaries, and high-risk hotspots from structure and metadata
call out drift, missing validation, generated code, or conflicting conventions
recommend the next best action and the best repo surfaces to load before changing code

Output Contract

repository summary with dominant languages, runtimes, and repo shape
key commands and entrypoints for build, test, run, and release
hotspots, blockers, and missing information that affect safe changes
recommended next action with the specific files or dirs to inspect next

Failure Modes

repo layout is too large to inspect safely in one pass
generated or vendored code hides the real ownership boundaries
no reliable build or validation entrypoints can be found

Escalation

escalate when ownership or architecture cannot be inferred safely
escalate when there is no trustworthy validation path for a risky change
escalate when docs and code disagree about the active workflow

References

skills/repo-onboarding/references/output-template.md
skills/repo-onboarding/references/discovery-checklist.md
skills/repo-onboarding/references/repo-archetypes.md
skills/repo-onboarding/references/ownership-and-health-signals.md
skills/repo-onboarding/references/command-discovery.md
skills/repo-onboarding/references/monorepo-signals.md
skills/repo-onboarding/references/examples.md

---name: repo-onboardingdescription: repository discovery, entrypoint mapping, and fast onboarding for unfamiliar codebases. use when the repo is new, mixed, legacy, monorepo-shaped, poorly documented, or when the next safe step is blocked on understanding layout, ownership, and commands.---# Repository Onboarding## Trigger Signals- the repository is unfamiliar, mixed, legacy, or monorepo-shaped- the next safe step is blocked on understanding layout, ownership, or workflow- docs are sparse, stale, or scattered across many entrypoints## Inspect First- repo root files such as `README.md`, top-level manifests, CI config, container config, and deployment hints- `AGENTS.md`, `.agents/skills/`, `.specify/`, or other repo-native guidance surfaces when present- top-level source, app, package, service, infra, and test directories- `CODEOWNERS`, contribution docs, issue or PR templates, and other health signals when present## Workflow1. identify the repo archetype and dominant implementation surfaces2. map build, test, run, deploy, and validation entrypoints3. infer ownership, boundaries, and high-risk hotspots from structure and metadata4. call out drift, missing validation, generated code, or conflicting conventions5. recommend the next best action and the best repo surfaces to load before changing code## Output Contract- repository summary with dominant languages, runtimes, and repo shape- key commands and entrypoints for build, test, run, and release- hotspots, blockers, and missing information that affect safe changes- recommended next action with the specific files or dirs to inspect next## Failure Modes- repo layout is too large to inspect safely in one pass- generated or vendored code hides the real ownership boundaries- no reliable build or validation entrypoints can be found## Escalation- escalate when ownership or architecture cannot be inferred safely- escalate when there is no trustworthy validation path for a risky change- escalate when docs and code disagree about the active workflow## References- `skills/repo-onboarding/references/output-template.md`- `skills/repo-onboarding/references/discovery-checklist.md`- `skills/repo-onboarding/references/repo-archetypes.md`- `skills/repo-onboarding/references/ownership-and-health-signals.md`- `skills/repo-onboarding/references/command-discovery.md`- `skills/repo-onboarding/references/monorepo-signals.md`- `skills/repo-onboarding/references/examples.md`

Frequently asked questions