repository-guide
Skill2 starsChanged 2 months agoApache-2.0View on GitHub
Follow the repository's development and verification conventions.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- lablup/backend.aitheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- lablup/backend.ai★ 679same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Distinctive: line 8
When the user asks to be caught up on this repository, use the generic shell in two foreground steps:
- Very specific: line 11
Read enough of README.md to identify what the repository is for.
- Distinctive: line 22
Keep the default user path tool-free, validate the smallest relevant test set, and report any verification that could not be run.
≈ “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.
Files
Repository orientation
When the user asks to be caught up on this repository, use the generic shell in two foreground steps:
- Read enough of
README.mdto identify what the repository is for. For example:sed -n '1,160p' README.md. - Inspect a bounded recent slice of Git history using the repository's normal
history command. Choose a useful bounded range; do not assume a fixed
commit count. For example:
git log --oneline --decorate --no-merges --max-count=<useful-bound>.
Then answer in two or three spoken sentences: explain the repository's purpose and mention at least one recent change. Do not include URLs, raw diffs, shell commands, tool traces, or policy details in the spoken answer.
Keep the default user path tool-free, validate the smallest relevant test set, and report any verification that could not be run.
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
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.