Agent skill

Amplify

by sharpdeveye in sharpdeveye/maestro

A skill your agent uses when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.

MITAuto-check passed

Install Amplify

skills CLI
$ npx skills add sharpdeveye/maestro --skill amplify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sharpdeveye/maestro amplify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sharpdeveye/maestro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/source/skills/amplify .claude/skills/amplify && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
amplify
GitHub stars
592
Token cost
~782 tokens
SKILL.md length
346 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.

  • Works in 4 steps: Identify the gap: What can't the… → Choose the strategy: Which amplification… → Implement incrementally: Add one… → …
  • The workflow works but needs to handle more complex cases
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Produce higher-quality output through better tools

What it does

Amplify is an agent skill from sharpdeveye/maestro. Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Workflow fluency for AI coding agents. 1 core skill · 25 commands · 7 domain references · memory layer · audit trail — works across Cursor, Claude Code, Gemini CLI, Copilot, and… The licence is MIT.

When your agent uses it

  • The workflow works but needs to handle more complex cases
  • Produce higher-quality output through better tools

Example prompts

  • “/amplify”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit 00f9115. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Amplify loads about 782 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 346 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~782

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sharpdeveye/maestro at commit 00f9115, republished under its MIT licence (© sharpdeveye). 346 words, ~782 tokens.

Download SKILL.mdSave it as .claude/skills/amplify/SKILL.md (or your agent's skills folder).
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
StrategyCost ImpactLatency ImpactQuality Impact
Better promptsNoneNoneMedium-High
Better toolsLowLow-MediumHigh
Better context (RAG)MediumMediumHigh
Better modelsHighMedium-HighHigh
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

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

© sharpdeveye, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in source/skills/amplify of sharpdeveye/maestro.

Open the folder on GitHubat commit 00f9115

Compare with similar skills

Amplify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Amplify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Amplify this skillsharpdeveye/maestro592—~782Automated safety check: PassMIT
Error Handlingaffaan-m/ECC275k1 repos~2.7kAutomated safety check: PassMIT
Error Handlingthedaviddias/Front-End-Checklist74k—~416Automated safety check: PassMIT
Error Handlingaffaan-m/ECC275k—~2.4kAutomated safety check: PassMIT
Python Error Handlingwshobson/agents40k—~1.5kAutomated safety check: PassMIT
Error Handling Patternswshobson/agents40k11 repos~1kAutomated safety check: PassMIT

Similar skills

  • Error Handling

    affaan-m/ECC

    Patterns for robust error handling across TypeScript, Python, and Go.

    275k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed
  • Error Handling

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Implement proper error handling.

    74k GitHub stars~416 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Error Handling

    affaan-m/ECC

    TypeScript、Python、Goにわたる堅牢なエラー処理のパターン。型付きエラー、エラー境界、リトライ、サーキットブレーカー、ユーザー向けエラーメッセージをカバーします。

    275k GitHub stars~2.4k tokensUpdated 3 days ago
    Auto-check passed
  • Python Error Handling

    wshobson/agents

    Python error handling patterns including input validation, exception hierarchies, and partial failure handling.

    40k GitHub stars~1.5k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications.

    40k GitHub starsUsed in 11 repos~1k tokens
    DevelopmentAuto-check passed
  • Studio Error Handling

    supabase/supabase

    Official

    Error display and troubleshooting pattern for Supabase Studio.

    111k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

More from sharpdeveye/maestro

All 25 skills in this repo
  • Accelerate

    sharpdeveye/maestro

    A skill your agent uses when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.

    592 GitHub stars~745 tokensUpdated 5 mo ago
    Auto-check passed
  • Chain

    sharpdeveye/maestro

    A skill your agent uses when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.

    592 GitHub stars~607 tokensUpdated 5 mo ago
    Auto-check passed
  • Compose

    sharpdeveye/maestro

    A skill your agent uses when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.

    592 GitHub stars~720 tokensUpdated 5 mo ago
    Auto-check passed
  • Diagnose

    sharpdeveye/maestro

    A skill your agent uses when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.

    592 GitHub stars~1.5k tokensUpdated 5 mo ago
    Auto-check passed
  • Extract Pattern

    sharpdeveye/maestro

    A skill your agent uses when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.

    592 GitHub stars~664 tokensUpdated 5 mo ago
    Auto-check passed
  • Fortify

    sharpdeveye/maestro

    A skill your agent uses when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.

    592 GitHub stars~688 tokensUpdated 5 mo ago
    Auto-check passed

Questions about Amplify

What does Amplify do?

A skill your agent uses when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models. Amplify is an agent skill from sharpdeveye/maestro. Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.

When should I use Amplify?

Amplify fits situations like: the workflow works but needs to handle more complex cases; produce higher-quality output through better tools.

How do I install Amplify in Claude Code?

Run `npx skills add sharpdeveye/maestro --skill amplify -a claude-code`. Or copy the skill folder (source/skills/amplify in sharpdeveye/maestro) into .claude/skills/amplify in your project. Claude Code loads it when a task matches its description.

How do I install Amplify in Codex?

Run `npx skills add sharpdeveye/maestro --skill amplify -a codex`. Or copy the skill folder (source/skills/amplify in sharpdeveye/maestro) into .agents/skills/amplify in your project. Codex loads it when a task matches its description.

Can I use Amplify in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sharpdeveye/maestro --skill amplify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/amplify, .gemini/skills/amplify, .github/skills/amplify and .opencode/skills/amplify in your project.

What does Amplify need to run?

SKILL.md names no scripts, command-line tools or credentials: Amplify is instructions for the agent only.

Does Amplify access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Amplify safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Amplify use?

Amplify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Amplify use?

About 782 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Amplify?

Skills that share tags, products or a category with Amplify: Error Handling (affaan-m/ECC, 275k stars), Error Handling (thedaviddias/Front-End-Checklist, 74k stars), Error Handling (affaan-m/ECC, 275k stars) and Python Error Handling (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Amplify?

sharpdeveye (a GitHub user) maintains it in sharpdeveye/maestro, which has 592 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on April 29, 2026.

Source: sharpdeveye/maestro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.