agentleFS
Sign inStart free
DanielGodriNetoDanielGodriNeto/claude-skills/skills/repo-howto/SKILL.md

repo-howto

Skill1 starsChanged 41 days agoMITView on GitHub

Use when the user wants to know how EXTERNAL open-source projects do something, or says "find GitHub repos that do X", "has someone built this", or pastes a github.com link and asks how it works or how to replicate it. Finds relevant repos, reads them, and explains the architecture and a plan to replicate it. No need for the user to paste a link or name a tool.

  • Installs packages

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:

    Token check first: if the feature is simple or the repo is small, read only the README (and at most 1-2 files) and answer.

    line 10
  2. Distinctive:

    If several repos fit, a compact comparison and one recommendation.

    line 20
  3. Distinctive:

    Do not clone or install anything from the repo.

    line 22

≈ “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

repo-howto

Goal: turn "I want feature X" or a GitHub link into a clear, short how-to.

  1. Token check first: if the feature is simple or the repo is small, read only the README (and at most 1-2 files) and answer. Use the full digest only for complex repos.
  2. Find repos (skip if the user gave a link): gh search repos "<keywords>" --sort stars --limit 8 --json fullName,description,stargazersCount,updatedAt,license. Also WebSearch if gh finds little. Prefer maintained (pushed in the last 12 months), real stars, permissive license. Pick the best 1-3.
  3. Read each pick, cheapest first:
    • gitingest <url> -o - (read-only digest; if the command is missing, use the gh fallback and tell the user, don't pip install). Pipe through head -c 60000 for big repos.
    • Fallback: gh repo view <owner/repo> and gh api repos/<owner>/<repo>/readme, then read only the key files.
    • Private repo: use gh, never send a token to a hosted gitingest site.
  4. Answer short, in the user's language:
    • What it does and how it is structured (3-6 lines, cite files).
    • How to replicate it in the user's stack (steps, libs, pitfalls).
    • License and maintenance caveats; flag anything risky (scraping ToS, secrets, abandoned).
    • If several repos fit, a compact comparison and one recommendation.

Do not clone or install anything from the repo. Read only.

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.

Check your setup, free