agentleFS
loganware05loganware05/captains-compass-cursor/.cursor/skills/repository-discovery/SKILL.md

repository-discovery

Skill2 starsChanged 33 days agoMITView on GitHub

Performs read-only repository discovery and reports architecture, tooling, risks, and conventions

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not modify product files.

    line 35
  2. Distinctive:

    Do not install dependencies without approval.

    line 36
  3. Distinctive:

    Do not rewrite documentation during discovery.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Repository Discovery

Use this Skill when

Starting a new task, onboarding to an unfamiliar repository, or before writing an implementation plan.

Inputs

  • Repository root
  • Existing project documentation
  • Git status

Procedure

  1. Identify languages, frameworks, and runtime versions.
  2. Identify package managers and build tooling.
  3. Map repository structure and application entry points.
  4. Identify test frameworks and CI/CD.
  5. Identify database and deployment configuration.
  6. Note existing Cursor instructions (AGENTS.md, rules, Skills).
  7. List high-risk files and missing documentation.
  8. Recommend Skills relevant to the current task (including source-code-context when integrating unfamiliar packages).

Output

A structured repository-discovery report for the First Mate.

Prohibited actions

  • Do not modify product files.
  • Do not install dependencies without approval.
  • Do not rewrite documentation during discovery.

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.