agentleFS
real-link-techreal-link-tech/reallink-skills/skills/reallink-manage-skills/SKILL.md

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.

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
  1. Distinctive:

    Before handling a complex, multi-step, or domain-specific task:

    line 8
  2. Very specific:

    If no local skill clearly applies, run find against reallink-skills.

    line 11
  3. Very specific:

    If the repository match is strong, run auto-install before continuing the original task.

    line 12
  4. Distinctive:

    Only proceed without a skill when no strong local or shared skill is available.

    line 13
  5. Distinctive:

    All operations are implemented by:

    line 17
  6. Very specific:

    Use these for repository discovery and local installation into .claude/skills.

    line 33
  7. Very specific:

    check both local .claude/skills and reallink-skills for duplicates,

    line 43
  8. Distinctive:

    stop if a similar skill already exists,

    line 44
  9. Very specific:

    call skill-creator only when creation is actually needed.

    line 45
  10. Distinctive:

    Only create a new skill when the target knowledge is:

    line 47
  11. Very specific:

    When creating a new skill, keep the generated description focused on trigger conditions and user intent, not implementation details.

    line 53
  12. Very specific:

    When create succeeds, always ask the user:

    line 55
  13. Distinctive:

    create or update the repository copy,

    line 71
  14. Distinctive:

    commit and push automatically when allowed.

    line 72
  15. Distinctive:

    Keep all related command abilities in this single skill:

    line 76
  16. Distinctive:

    Before finalizing a new skill, make sure:

    line 87

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Preflight Rule

Before handling a complex, multi-step, or domain-specific task:

  1. Inspect the current project's .claude/skills directory for a directly relevant local skill.
  2. If no local skill clearly applies, run find against reallink-skills.
  3. If the repository match is strong, run auto-install before continuing the original task.
  4. 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

  • search
  • find
  • install
  • download
  • auto-install

Use these for repository discovery and local installation into .claude/skills.

Create

  • create-check
  • check-create
  • create

Use these to:

  • check both local .claude/skills and reallink-skills for duplicates,
  • stop if a similar skill already exists,
  • call skill-creator only 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-check
  • check-upload
  • upload

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: search or find
  • local install: install or download
  • duplicate check before creation: create-check or check-create
  • actual creation: create
  • duplicate check before upload: upload-check or check-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.

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.