agentsclimarketplace

Repo onboarding

Skill hoangsonww/Claude-Code-Agent-Monitor/.agents/skills/repo-onboarding

Understand this repository quickly before making changes. Use for architecture discovery, ownership mapping, command selection, and initial implementation planning.From its SKILL.md

Install
npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill repo-onboarding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • runs commandsInstructs the agent to run 4 commands, including `npm run test:server` and 3 more.

SKILL.md

0.7 KB, 131 tokens by cl100k_base, as published. Nobody here has run it

Repo Onboarding Skill

Workflow

  • Read AGENTS.md, README.md, and ARCHITECTURE.md.
  • Determine target layer: server/, client/, mcp/, or docs.
  • Identify the minimal file set needed for the task.
  • Select verification commands before editing.

Verification defaults

  • Backend: npm run test:server
  • Frontend: npm run test:client
  • MCP: npm run mcp:typecheck and npm run mcp:build

References

  • references/module-map.md
  • references/verification-map.md

What ships with it: 3 files

875 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most codebase onboarding skills give in 131 tokens

Counted across 307 of the 325 authors here whose files we hold, read 2026-09-06

  • Focus first session on one successful outcomein 34 of 307, across 15 files
  • Show progress and celebrate completionsin 32 of 307, across 13 files
  • Prefer interactive doing over tutorialsin 32 of 307, across 13 files
  • Remove every step between signup and core valuein 32 of 307, across 13 files
  • Keep checklists to 3-7 items ordered by valuein 32 of 307, across 13 files
  • Read product marketing context before asking questionsin 28 of 307, across 13 files
  • Focus fixes on the biggest funnel drop-offsin 22 of 307, across 7 files
  • Define activation as the action most correlated with retentionin 20 of 307, across 6 files
  • Give one clear next action at every stepin 19 of 307, across 8 files
  • Understand product context and current state before recommendingin 15 of 307, across 3 files
  • Limit guided tours to five dismissable stepsin 15 of 307, across 6 files
  • Trace one request from entry to responsein 14 of 307, across 8 files

Said here and by no other author read

  • Read AGENTS.md, README.md, and ARCHITECTURE.md
  • Determine the target layer
  • Identify the minimal file set for the task
  • Select verification commands before editing
  • Run the designated verification commands
  • Consult the module and verification maps

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.