amplifier-tool-leverage-patterns Skill

Source

• Creator: microsoft
• Repository: microsoft/amplifier-bundle-skills
• Skill file: skills/amplifier-tool-leverage-patterns/SKILL.md

What it does

Use when deciding how to expose an Amplifier workflow or automation tool — .dot attractor pipeline, Python lib, tool module, or CLI. Covers the four leverage levels, the DRY rule that keeps logic in ONE home, which levels a real consumer actually needs (and when a level is just ceremony), and the attractor-only case wh

Skill instructions

Amplifier Tool Leverage Levels The Pattern Problem: You've built a workflow/automation tool on Amplifier. Different consumers want to use it different ways — an attractor pipeline wants to compose it, a web app wants to import it, an agent wants to call it as a tool, a human wants a CLI. You don't want four copies of the logic. Approach: Pick ONE home for the logic, then expose up to four leverage levels as thin adapters over that home. Build only the levels a real consumer demands. | Level | Surface | Consumer | What it is | |-------|---------|----------|------------| | L1 | .dot attractor pipelines | Other pipelines / Resolve | One .dot per command + a shared subgraph (folder-shape), run on the loop-pipeline engine (amplifier-bundle-attractor) | | L2 | Python lib | Other codebases | Each command an importable method; clean public API in init.py | | L3 | Amplifier tool modules | Agents | bundle.md + modules/tool-<name/ wrapping each command as an agent-callable tool | | L4 | CLI | Hum