reallink-manage-skills
Skill4 starsChanged 3 months agoMITView on GitHub
Find, install, create, or upload reallink skills between the current project's .claude/skills directory and the real-link-tech/reallink-skills repository. Also use before complex or domain-specific tasks when the agent should first check whether an existing local or shared skill can solve the problem.
In this repository15 other files it gives its agents.
- apt-replay-runSkill
- ctx-stashSkill
- eca-editorSkill
- memreport-analyzeSkill
- pix-gpu-debugSkill
- prospero-razorgpu-debugSkill
- ps5-devkit-bridgeSkill
- quick-analyze-gpuprofileSkill
- rdc-analysisSkill
- skill-vetterSkill
- streaming-pool-json-htmlSkill
- uefn-reallink-bridgeSkill
- ue-trace-analysisSkill
- video-summarySkill
- vt-json-htmlSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 9 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Before handling a complex, multi-step, or domain-specific task:
- Very specific: line 11
If no local skill clearly applies, run find against reallink-skills.
- Very specific: line 12
If the repository match is strong, run auto-install before continuing the original task.
- Distinctive: line 13
Only proceed without a skill when no strong local or shared skill is available.
- Distinctive: line 17
All operations are implemented by:
- Very specific: line 33
Use these for repository discovery and local installation into .claude/skills.
- Very specific: line 43
check both local .claude/skills and reallink-skills for duplicates,
- Distinctive: line 44
stop if a similar skill already exists,
- Very specific: line 45
call skill-creator only when creation is actually needed.
- Distinctive: line 47
Only create a new skill when the target knowledge is:
- Very specific: line 53
When creating a new skill, keep the generated description focused on trigger conditions and user intent, not implementation details.
- Very specific: line 55
When create succeeds, always ask the user:
- Distinctive: line 71
create or update the repository copy,
- Distinctive: line 72
commit and push automatically when allowed.
- Distinctive: line 76
Keep all related command abilities in this single skill:
- Distinctive: line 87
Before finalizing a new skill, make sure:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Preflight Rule
Before handling a complex, multi-step, or domain-specific task:
- Inspect the current project's
.claude/skillsdirectory for a directly relevant local skill. - If no local skill clearly applies, run
findagainstreallink-skills. - If the repository match is strong, run
auto-installbefore continuing the original task. - Only proceed without a skill when no strong local or shared skill is available.
Core Script
All operations are implemented by:
python "<skill-path>/scripts/manage_reallink_skills.py" <subcommand> ...Supported Subcommands
Search And Install
searchfindinstalldownloadauto-install
Use these for repository discovery and local installation into .claude/skills.
Create
create-checkcheck-createcreate
Use these to:
- check both local
.claude/skillsandreallink-skillsfor duplicates, - stop if a similar skill already exists,
- call
skill-creatoronly when creation is actually needed.
Only create a new skill when the target knowledge is:
- reusable beyond the current one-off task,
- non-trivial and worth preserving,
- specific enough that a future agent can recognize when to use it quickly.
When creating a new skill, keep the generated description focused on trigger conditions and user intent, not implementation details.
When create succeeds, always ask the user:
是否需要我立即使用 reallink-upload-skills 把这个新 skill 上传到 reallink-skills 仓库?Upload
upload-checkcheck-uploadupload
Use these to:
- compare a local skill against
reallink-skills, - block on conflicting similar skills,
- create or update the repository copy,
- commit and push automatically when allowed.
Command Rule
Keep all related command abilities in this single skill:
- repository lookup:
searchorfind - local install:
installordownload - duplicate check before creation:
create-checkorcheck-create - actual creation:
create - duplicate check before upload:
upload-checkorcheck-upload - repository submission:
upload
Creation Quality Gate
Before finalizing a new skill, make sure:
- it does not duplicate an existing local or shared skill,
- its description is specific enough to be discovered later,
- it captures a repeatable workflow rather than a one-off answer.
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.

