agentleFS
KhaiTrang1995KhaiTrang1995/nexus-kb/.agents/skills/repo-onboarding/SKILL.md

repo-onboarding

Skill1 starsChanged 5 months agoMITView on GitHub

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

11 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read AGENTS.md, README.md, and docs/architecture.md.

    line 9

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Repo Onboarding Skill

Workflow

  • Read AGENTS.md, README.md, and docs/architecture.md.
  • Determine target area: root docs, agent configuration, Hermes runtime template, or qdrant-multi-node-cluster/.
  • Identify the minimal file set needed for the task.
  • Select verification commands before editing.

Verification defaults

  • Documentation: manual link, heading, and source-of-truth consistency check.
  • Qdrant demo: cd qdrant-multi-node-cluster && make test.
  • Agent configuration: verify referenced files exist and local-only artifacts remain ignored.

References

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.