How do I install agent-orchestration-improve-agent?
Download plugins/agentic-awesome-skills-claude/skills/agent-orchestration-improve-agent/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does agent-orchestration-improve-agent live?
The publisher keeps it at https://github.com/sickn33/agentic-awesome-skills.
Which agents can use agent-orchestration-improve-agent?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.
name: agent-orchestration-improve-agent
description: "Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration."
risk: critical
source: community
date_added: "2026-02-27"
Agent Performance Optimization Workflow
Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.
[Extended thinking: Agent optimization requires a data-driven approach combining performance metrics, user feedback analysis, and advanced prompt engineering techniques. Success depends on systematic evaluation, targeted improvements, and rigorous testing with rollback capabilities for production safety.]
Use this skill when
Improving an existing agent's performance or reliability
Analyzing failure modes, prompt quality, or tool usage
Running structured A/B tests or evaluation suites
Designing iterative optimization workflows for agents
Do not use this skill when
You are building a brand-new agent from scratch
There are no metrics, feedback, or test cases available
The task is unrelated to agent performance or prompt quality
Instructions
Establish baseline metrics and collect representative examples.
Identify failure modes and prioritize high-impact fixes.
Apply prompt and workflow improvements with measurable goals.
Validate with tests and roll out changes in controlled stages.
Execution boundaries
Do not run hosted evaluations, delegate, message teams, configure recurring reports or deploy merely because a phase names them. Follow the user's existing authorization and actual host workflow. Keep traces private/redacted, cap cost and steps, isolate candidate changes, and require supported exact-version checks. parallel-test-runner and named agent roles are not bundled; use a real harness or report the gap.
Safety
Avoid deploying prompt changes without regression testing.
Roll back quickly if quality or safety metrics regress.
Phase 1: Performance Analysis and Baseline Metrics
Analyze supplied traces and available metrics. Named roles below are optional roles, not installed executables or permission to delegate.
1.1 Gather Performance Data
Use: context-manager
Task: analyze the authorized trace window using actual available tools
No analyze-agent-performance command is bundled.
Rollback Triggers:
- Success rate drops >10% from baseline
- Critical errors increase >5%
- User complaints spike
- Cost per task increases >20%
- Safety violations detected
Rollback Process:
1. Detect issue via monitoring
2. Alert team immediately
3. Switch to previous stable version
4. Analyze root cause
5. Fix and re-test before retry
4.4 Continuous Monitoring
Real-time performance tracking:
Dashboard with key metrics
Anomaly detection alerts
User feedback collection
Automated regression testing
Weekly performance reports
Success Criteria
The following are illustrative targets, not universal success conditions. Choose the actual criteria before testing, distinguish relative changes from percentage points and report uncertainty:
Task success rate improves by ≥15%
User corrections decrease by ≥25%
No increase in safety violations
Response time remains within 10% of baseline
Cost per task doesn't increase >5%
Positive user feedback increases
Post-Deployment Review
After 30 days of production use:
Analyze accumulated performance data
Compare against baseline and targets
Identify new improvement opportunities
Document lessons learned
Plan next optimization cycle
Continuous Improvement Cycle
Establish regular improvement cadence:
Weekly: Monitor metrics and collect feedback
Monthly: Analyze patterns and plan improvements
Quarterly: Major version updates with new capabilities
Annually: Strategic review and architecture updates
Remember: Agent optimization is an iterative process. Each cycle builds upon previous learnings, gradually improving performance while maintaining stability and safety.
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
How do I install agent-orchestration-improve-agent?
Download plugins/agentic-awesome-skills-claude/skills/agent-orchestration-improve-agent/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does agent-orchestration-improve-agent live?
The publisher keeps it at https://github.com/sickn33/agentic-awesome-skills.
Which agents can use agent-orchestration-improve-agent?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.