Agent skill · Audited from source
Temper
skill · sharpdeveye/maestroMIT licenceAudited 19 Oct 2026 · source 4e163a7a8095
Is it safe? With care — CAUTION, grade B (89/100). We read this skill's source at commit 4e163a7a8095 and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 1 finding, 0 critical or high. What it does: Use when the workflow feels over-engineered, has premature optimizations, unnecessary abstraction layers, or complexity beyond actual requirements.
Cite
Cite this page
ModelsAtlas. “Temper (sharpdeveye/maestro)”. Retrieved 19 Oct 2026. https://modelsatlas.com/skills/sharpdeveye/temper
Trust audit
Audit 0.4.1 · source read 19 Oct 2026
CAUTION means the audit found things worth knowing before you trust this skill. Grade B is shared by 16,667 of 17,602 audited skills.
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
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | WARN | 1 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (1)
MEDIUMPrompt injectionreview.instruction_override · SKILL.md
Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
- Why
- The skill forces invocation of external, undefined workflows (/agent-workflow, /teach-maestro) and mandates a mandatory preparation protocol that overrides the agent's own judgment.
- Fix
- rewrite it so the instruction says plainly what it does, and asks the user before it acts
Audit 0.4.1 · source sha 4e163a7a8095 · 19 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishersharpdeveye GitHub userOwner of the repository this skill is read from
- Source foldersharpdeveye/maestro/source/skills/temperThe 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
What it tells the agent
Full source on GitHub ↗Its description: Use when the workflow feels over-engineered, has premature optimizations, unnecessary abstraction layers, or complexity beyond actual requirements.
--- name: temper description: "Use when the workflow feels over-engineered, has premature optimizations, unnecessary abstraction layers, or complexity beyond actual requirements." argument-hint: "[target]" 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 agent-architecture reference in the agent-workflow skill for topology patterns and when multi-agent is justified. --- Pull back from over-engineering. The most common mistake isn't building too little — it's building too much. ### Over-Engineering Detection **Signs you've over-engineered:** - Multi-agent for a single-agent problem - Premature optimization before you have performance data - Abstraction layers with one implementation - Configuration for things that never change - Evaluation loops on non-critical outputs - Framework before features ### The Complexity Test For each component: 1. **Is this solving a problem we actually have?** (not "might have") 2. **Is this the simplest solution that works?** 3. **Would removing this break anything?** (if not, remove it) 4. **Can someone new understand this in 5 minutes?** (if not, simplify) ### Tempering Strategies **Collapse Unnecessary Agents** ```text OVER-ENGINEERED: User → Classifier → Router → Specialist → Formatter → Checker (6 components) TEMPERED: User → Single Agent with good prompt (1 component, same quality) ``` **Remove Premature Abstraction** ```text OVER-ENGINEERED: class AgentOrchestrator with 5 strategy interfaces TEMPERED: async function runWorkflow(input) — direct, readable ``` **Simplify Configuration** ```text OVER-ENGINEERED: config.yaml (200 lines, 47 params, 3 inheritance levels) TEMPERED: config.yaml (20 lines, essential params only, sensible defaults) ``` ### What NOT to Temper - Error handling — essential, not overhead - Logging — saves you when things go wrong - Input validation — prevents cascading failures - Core guardrails — safety is non-negotiable - The golden test set — how you know it still works ### Recommended Next Step After tempering, run `/evaluate` to confirm quality is preserved, or `/diagnose` for a full health check. **NEVER**: - Temper without measuring output quality before and after - Remove error handling in the name of simplicity - Simplify below the level of correctness - Remove features users actively rely on
Excerpt, first 2,593 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.
Install
Pinned to the audited commit 4e163a7
git clone https://github.com/sharpdeveye/maestro git -C maestro checkout 4e163a7a8095
The author documents no install command, so this uses the repository directly. Our verdict covers commit 4e163a7a8095 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- !CAUTION B 89 / 100
first audit · source
4e163a7a8095
Similar skills
sharpdeveye/maestro
Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
sharpdeveye/maestro
Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.
sharpdeveye/maestro
Use when any Maestro command is invoked — provides foundational workflow design principles across prompt engineering, context management, tool orchestration, agent architecture, feedback loops, knowledge systems, and…
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.
sharpdeveye/maestro
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
sharpdeveye/maestro
Capture a session summary — what was done, what decisions were made, and what to do next.
Questions about Temper
What does the Temper skill do?
Is Temper safe to install?
What can Temper access on my machine?
How current is this page?
Sources
- github.com/sharpdeveye/maestro/tree/main/source/skills/temper — the audited source at commit 4e163a7a8095 and every finding aboveObserved · 19 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Temper skill do?
- Is Temper safe to install?
- What can Temper access on my machine?