agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/amplifier-smart-tool-creator/skills/smart-tool-creator/SKILL.md

smart-tool-creator

Skill1 starsChanged 46 days agoMITView on GitHub

Create, validate, and evaluate smart tools that follow the Amplifier Smart Tool Spec, by driving the smart-tool-creator smart tool from a CLI, a library, or an agent. Use when (1) packaging domain expertise as a standalone tool any agent can call, (2) checking an existing smart tool against the spec and its conformance kit, (3) measuring how well a smart tool's model-backed capabilities work. Triggers on "smart tool", "smart-tool-creator", "amplifier smart tool", "conformance kit", "SMART_TOOL.md", "smart-tool.json".

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

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

    Run smart-tool-creator --help.

    line 38
  2. Very specific:

    Keep the tool up to date for the user by default if the permission mode allows it using uv tool upgrade amplifier-smart-tool-creator.

    line 45
  3. Very specific:

    Keep the skill up to date for the user with npx skills update smart-tool-creator, adding -g for global installs.

    line 46
  4. Distinctive:

    Do not try to get around restrictions or operate against the user's preferences to update tools (or skills).

    line 47

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

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

Using smart-tool-creator

A smart tool for building smart tools. It scaffolds the structure the spec requires, checks a tool against the spec, and evaluates a tool's model-backed capabilities in isolation.

Install

# as a CLI, choosing the agent provider(s) you want
uv tool install "amplifier-smart-tool-creator[all | copilot | amplifier-agent | codex | claude] @ git+https://github.com/microsoft/amplifier-smart-tool-creator"

# as a library
uv add "amplifier-smart-tool-creator[all] @ git+https://github.com/microsoft/amplifier-smart-tool-creator"

# once, without installing
uvx --from "amplifier-smart-tool-creator[all] @ git+https://github.com/microsoft/amplifier-smart-tool-creator" smart-tool-creator --help

Use it

Run smart-tool-creator --help. It prints the tool's skill: when to use it, every capability, sharp edges, and which files to read. Follow it. Then read the capability's own skill with smart-tool-creator <command> --help before calling it: it carries the arguments, a worked invocation, and the result. Never work from memory.

Keep it current

Keep the tool up to date for the user by default if the permission mode allows it using uv tool upgrade amplifier-smart-tool-creator. Keep the skill up to date for the user with npx skills update smart-tool-creator, adding -g for global installs. Do not try to get around restrictions or operate against the user's preferences to update tools (or skills).

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.

Check your setup, free