github-kb
Skill1 starsChanged 38 days agoMITView on GitHub
Maintain and search a local knowledge base of cloned GitHub repositories. Use when the user wants to search local repositories, reuse local source code, clone a repository into the local project collection, or maintain a local repo registry. Do not trigger for ordinary public GitHub questions that do not need the local repository collection.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- 0xtootoo29/tootoo-skillstheir own version, first seen Mar 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- 0xtootoo29/tootoo-skills★ 0same 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 repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audience-report-formattingSkill
- baidu-netdiskSkill
- baidu-netdisk-syncspace-recoverySkill
- china-proxySkill
- chrome-devtoolsSkill
- claude-maintenanceSkill
- cloudcli-device-onboardingSkill
- codex-dream-skin-fixSkill
- content-research-writerSkill
- git-history-cleanupSkill
- github-aliyun-deploySkill
- google-flow-story-videoSkill
- mac-windows-lanSkill
- meeting-materials-uploadSkill
- meeting-reimbursement-auditSkill
- openmaicSkill
- opus-code-videoSkill
- seedance-short-dramaSkill
- spec-modeSkill
- video-courseware-extractorSkill
- wechat-account-bookmarksSkill
- wechat-ai-model-writerSkill
- wechat-android-shortcutsSkill
- wechat-ios-shortcutsSkill
- wechat-medical-writerSkill
- wechat-tech-writerSkill
- wps-presentation-batchSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use a local repository collection as the first source when the task is specifically about the user's cloned projects or reusable local code.
- Very specific: line 12
Prefer an explicit project root supplied by the user.
- Distinctive: line 16
Check the local repository root for an exact or likely repository match.
- Distinctive: line 17
If a local repository exists, inspect it locally before searching remote GitHub.
- Distinctive: line 18
If the requested repository is not local and the user wants a local copy, clone it into the repository root.
- Distinctive: line 20
Never overwrite an existing local repository silently.
- Very specific: line 33
Use the environment's native GitHub connector/tool when available.
- Distinctive: line 37
Do not trigger on every mention of “GitHub”, “repo”, or “repository”.
- Distinctive: line 38
Do not clone repositories unless a local copy is useful for the requested task.
- Very specific: line 39
Do not assume ~/IdeaProjects or another machine-specific path.
- Distinctive: line 40
Do not modify the user's local registry or clone location without a clear task reason.
≈ “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
GitHub Local Knowledge Base
Use a local repository collection as the first source when the task is specifically about the user's cloned projects or reusable local code.
Repository root
Prefer an explicit project root supplied by the user. Otherwise use GITHUB_KB_ROOT when set; if neither is available, use ~/projects as a conventional default and confirm it exists before writing there.
Workflow
- Check the local repository root for an exact or likely repository match.
- If a local repository exists, inspect it locally before searching remote GitHub.
- If the requested repository is not local and the user wants a local copy, clone it into the repository root.
- Maintain an optional
CLAUDE.mdregistry in the repository root with one concise line per cloned repository. - Never overwrite an existing local repository silently.
Local registry format
# GitHub Repository Registry
- **repo-name**: One-line description
- **another-repo**: One-line descriptionGitHub access
Use the environment's native GitHub connector/tool when available. Fall back to gh or the GitHub REST API only when appropriate for the runtime.
Guardrails
- Do not trigger on every mention of “GitHub”, “repo”, or “repository”.
- Do not clone repositories unless a local copy is useful for the requested task.
- Do not assume
~/IdeaProjectsor another machine-specific path. - Do not modify the user's local registry or clone location without a clear task reason.
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.