microsoft/amplifier-smart-tools

microsoft/amplifier-smart-tools

Description: Smart Tools powered by Amplifier Agent

Language: Python

License: MIT

Stars: 0

Forks: 1

Open issues: 0

Created: 2026-08-27T04:30:36Z

Pushed: 2026-08-27T04:55:34Z

Default branch: main

Fork: no

Archived: no

README:

Amplifier Smart Tools

The home of the Smart Tools specification, its conformance kit, and the catalog of reference implementations.

A format for packaging domain expertise into tools that any agent can use.

What are Smart Tools?

A smart tool is a self-contained tool that ships with its own AI capability built in. It behaves like an ordinary library or CLI, and its straight code paths run with no model provider configured. Alongside those, it exposes higher-level commands that invoke AI under the hood, so a caller states what it wants rather than loading a domain's worth of context and doing the work itself.

At its core, a smart tool is a library, a manifest describing it, and a thin CLI over the top. Anything else is an optional adapter over the same library.

my-smart-tool/
├── SMART_TOOL.md # Required: the manifest, what it is and what it needs
├── pyproject.toml # Required: the package definition
├── src/ # Required: the library, plus a thin CLI over it
└── ... # Optional: MCP server, web UI, other adapters

Why Smart Tools?

Hard-won domain expertise tends to stay where it was built, consumable only from inside the harness it was built for and only with the right context loaded. Smart tools package that expertise so it travels:

• Consumable anywhere: Copilot, Claude Code, a Python service, a shell

script, or any future agent.

• Useful without a model: deterministic paths run with no provider

configured, so a caller that never touches the smart commands never needs credentials.

• The knowledge stays in the tool: the caller states an intent and gets a

structured result it can hand straight to code.

What's in this repository

| Path | What it is | |------|------------| | [spec/](spec/README.md) | The specification — start here | | [conformance/](conformance/README.md) | A machine-checkable conformance kit: is this a conforming smart tool? | | [spec/examples.md](spec/examples.md) | Catalog of reference implementations | | [ROADMAP.md](ROADMAP.md) | What the specification deliberately leaves open |

The specification

• [Specification](spec/README.md): start here
• [Structure](spec/structure.md): the layers a smart tool is built from
• [Manifest](spec/manifest.md): how a smart tool describes itself
• [Invocation](spec/invocation.md): calling a smart tool
• [Roadmap](ROADMAP.md): what is deliberately left open

Conformance

The [conformance kit](conformance/README.md) turns the specification's must/must-not prose into executable checks. It is generic over any smart tool, stdlib-only, and honest about what it cannot evaluate (a rule it cannot check is reported SKIP, never a fabricated PASS). Run it against any tool's distribution root:

python3 conformance/run.py path/to/your-smart-tool

Reference implementations

Working smart tools that demonstrate the shape live in [spec/examples.md](spec/examples.md). The first is **amplifier-smart-tool-tmux**, which enforces this repository's conformance kit in its own CI.

Provenance

The Smart Tools specification originated at DavidKoleczek/amplifier-smart-tools-spec and is developed here as its canonical home. The conformance kit was contributed alongside the first reference implementation.

Contributing

> [!NOTE] > This project is not currently accepting external contributions, but we're actively working toward opening this up. We value community input and look forward to collaborating in the future. For now, feel free to fork and experiment!

Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit Contributor License Agreements.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

License

[MIT](LICENSE)