amplifier-philosophy Skill
Amplifier design philosophy using Linux kernel metaphor. Covers mechanism vs policy, module architecture, event-driven design, and kernel principles. Use when designing new modules or making architectural decisions. Published by microsoft in amplifier-bundle-skills.
Decision snapshot
Is this a fit?
Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is amplifier-philosophy Skill?
Amplifier design philosophy using Linux kernel metaphor. Covers mechanism vs policy, module architecture, event-driven design, and kernel principles. Use when designing new modules or making architectural decisions. Published by microsoft in amplifier-bundle-skills. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Design and media use cases
Declared skill metadata
- Declared license: MIT
- Source file: modules/tool-skills/tests/fixtures/skills/amplifier-philosophy/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use amplifier-philosophy Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-bundle-skills
- Skill file: modules/tool-skills/tests/fixtures/skills/amplifier-philosophy/SKILL.md
What it does
Amplifier design philosophy using Linux kernel metaphor. Covers mechanism vs policy, module architecture, event-driven design, and kernel principles. Use when designing new modules or making architectural decisions.
Skill instructions
Amplifier Philosophy: The Linux Kernel Metaphor Core Principle: Mechanism Not Policy If two teams might want different behavior, it belongs in a module, not the kernel. The kernel provides mechanisms (mount, emit, dispatch). Modules provide policies (what to mount, when to emit, how to handle). Architecture Patterns Kernel (amplifier-core) Keep it minimal and stable: - Session management (sessioncreate, mount, unmount) - Event emission (emit) - Hook registration - Context access Never add to kernel: - Provider selection - Tool routing - Plan generation - Default behaviors - File I/O Modules (Everything Else) All capabilities as modules: - Providers: LLM backends (Anthropic, OpenAI, Ollama) - Tools: Capabilities (filesystem, bash, web) - Orchestrators: Execution strategies - Context Managers: State management - Hooks: Lifecycle observers Mount Point System Think of modules as devices mounted at paths: /mnt/providers/{name} - LLM backends /mnt/tools/{name} - Agent capabilities /mnt/hooks
Verified compatibility and discovery
Frequently asked questions
What is amplifier-philosophy?
amplifier-philosophy is a open-source AI agent skill with Copy skill directory. Amplifier design philosophy using Linux kernel metaphor. Covers mechanism vs policy, module architecture, event-driven design, and kernel principles.
Who is amplifier-philosophy best for?
amplifier-philosophy is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install amplifier-philosophy?
Install or run amplifier-philosophy using Copy skill directory. Check amplifier-philosophy for the latest setup command.
Is amplifier-philosophy actively maintained?
amplifier-philosophy may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
