Amplify

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 4e163a7a8095 · 19 Oct 2026Report an issue or request a re-scan

• Publishersharpdeveye GitHub userOwner of the repository this skill is read from
• Source foldersharpdeveye/maestro/source/skills/amplifyThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict4e163a7a8095A new audit runs when the source changes
• Repository statusNot archivedLast push 173 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.

---
name: amplify
description: "Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models."
argument-hint: "[target area]"
category: enhancement
version: 2.0.0
user-invocable: true
---

## MANDATORY PREPARATION

Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
Consult the tool-orchestration reference in the agent-workflow skill for adding tools effectively.


---

Take a working workflow and make it more capable. Amplification adds new abilities without breaking existing functionality.

### Amplification Strategies

**Better Prompts**

- Add few-shot examples for edge cases the model currently mishandles
- Add chain-of-thought for tasks where reasoning quality matters
- Add negative instructions for common mistakes
- Upgrade output schema with more structured fields

**Better Tools**

- Add tools for capabilities the model currently lacks
- Improve existing tool descriptions for better selection accuracy
- Add confirmation steps for high-stakes operations
- Add tools for verification/validation of outputs

**Better Context**

- Add RAG for domain-specific knowledge
- Add real-time data sources for current information
- Add user profile/history for personalization
- Add project documentation as reference context

**Better Models**

- Upgrade to a more capable model for critical steps
- Use model cascading (cheap model for simple, capable model for complex)
- Add vision capabilities if processing images/documents
- Add code execution capabilities if generating code

### Amplification Process

1. **Identify the gap**: What can't the workflow do that it should?
2. **Choose the strategy**: Which amplification approach addresses the gap?
3. **Implement incrementally**: Add one capability at a time
4. **Verify**: Run the evaluation suite to confirm improvement without regression

### Impact Assessment

| Strategy | Cost Impact | Latency Impact | Quality Impact |
|----------|-----------|---------------|----------------|
| Better prompts | None | None | Medium-High |
| Better tools | Low | Low-Medium | High |
| Better context (RAG) | Medium | Medium | High |
| Better models | High | Medium-High | High |

### Amplification Checklist

- [ ] Gap identified with concrete evidence (not assumption)
- [ ] Single strategy selected (don't amplify everything at once)
- [ ] Baseline quality score recorded before change
- [ ] Change implemented and tested
- [ ] Quality score improved without regression
- [ ] Cost/latency impact documented

### Recommended Next Step

After amplification, run `/evaluate` to verify the new capability works, or `/iterate` to set up quality monitoring for the enhanced workflow.

**NEVER**:

- Amplify without a specific gap to address (amplification without purpose is bloat)
- Add capabilities without testing them
- Upgrade models without recalculating cost
- Add tools without updating tool descriptions

Excerpt, first 3,127 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/sharpdeveye/maestro
git -C maestro checkout 4e163a7a8095

Works in

1. 2026-10-19
   ✓SAFE B 89 / 100

   first audit · source 4e163a7a8095

Questions about Amplify

• github.com/sharpdeveye/maestro/tree/main/source/skills/amplify — the audited source at commit 4e163a7a8095 and every finding aboveObserved · 19 Oct 2026

Spotted something wrong? Report a correction · Methodology