agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/amplifier-bundle-work/skills/skill-installer/SKILL.md

skill-installer

Skill0 starsChanged 27 days agoMITView on GitHub

Discover and install Amplifier-compatible skills from a local folder or Git repository into the requested project, personal directory, or bundle.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 0

    Distinctive

    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
  1. Very specific:

    Use .amplifier/skills for a requested project install, ~/.amplifier/skills for a personal install, or the exact bundle directory the user …

    line 17
  2. Very specific:

    Use .agents/skills when the user requests a shared cross-client install.

    line 23
  3. Very specific:

    Check resource closure before copying an individual skill.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “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

Skill Installer

Resolve the requested repository/path and revision. Use existing authorized Git credentials, never embedded tokens. Inspect the skill package, license, scripts, resource links, and dependencies before installation. Do not execute source scripts or preprocessing merely to list skills. If a foreign skill needs tool, runtime, or host translation, use adapt-skill when available or report those requirements before calling it usable.

Use .amplifier/skills for a requested project install, ~/.amplifier/skills for a personal install, or the exact bundle directory the user selected. Refuse silent collisions. Copy the whole permitted package while excluding repository metadata, credentials, generated caches, and dependency directories. Reject symlinks escaping the package and keep originals intact.

Use .agents/skills when the user requests a shared cross-client install. Work discovers both conventions; project skills precede user skills, and native paths win within a scope. Check the actual winning path from load_skill after install.

Check resource closure before copying an individual skill. Work's Office skills share ../_shared helpers, so install the collection through its behavior or include that sibling directory without overwriting an existing different version. A lone SKILL.md or leaf directory is not the complete package in this case.

For Git sources, follow the requested branch and record the tested revision in validation evidence. Do not pin bundle or module source declarations. Register through the host's real skill-source configuration when that is preferable to copying. Namespaced bundle sources are resolved through Foundation; relative ./skills is unsafe when the host starts elsewhere. Refresh discovery through the supported tool or a fresh session, then call load_skill for every installed name and verify resources. Report the destination, revision, invocation, dependencies, and validation. Do not claim that skill installation also installed its external services.

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.

Reviews can't be read right now.

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