Live survey304 models · 14 providers · 22,792 auditsAudited grill-with-docs · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

Temper

skill · sharpdeveye/maestroMIT licenceAudited 19 Oct 2026 · source 4e163a7a8095

★ 591pushed 173 days agoversion 2.0.0
!CAUTIONGrade B · 89/100 · 1 finding · 4e163a7
591repo stars · whole sharpdeveye/maestro

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.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
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

Trust score89/100!CAUTION B
0 critical0 high1 medium0 low0 info

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

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesWARN1
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (1)

MEDIUMPrompt injectionreview.instruction_override · SKILL.md
F-01 Prompt injectionCWE-94 · CWE-1427Layer L2
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

Download folder ↗
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

  1. !CAUTION B 89 / 100

    first audit · source 4e163a7a8095

Similar skills

Questions about Temper

What does the Temper skill do?
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 6 more.
Is Temper safe to install?
With care. The audit graded it B (89/100) and found 1 thing worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Temper access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (4e163a7a8095), read on 2026-10-19. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

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.