Agent skill · Audited from source
Refine
skill · sharpdeveye/maestroMIT licenceAudited 19 Oct 2026 · source 4e163a7a8095
Is it safe? Yes — SAFE, 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. What it does: Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping.
Cite
Cite this page
ModelsAtlas. “Refine (sharpdeveye/maestro)”. Retrieved 19 Oct 2026. https://modelsatlas.com/skills/sharpdeveye/refine
Trust audit
Audit 0.4.1 · source read 19 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. 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 | PASS | 0 |
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 (0)
No findings at any severity. We re-audit when the source changes.
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/refineThe 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 works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping.
--- name: refine description: "Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping." argument-hint: "[target area]" category: fix 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. --- This is the final quality pass. The workflow works — now make it excellent. ### Refinement Checklist **Prompts** - [ ] Every prompt follows the 4-zone pattern (role, context, instructions, output) - [ ] Output schemas are explicit and validated - [ ] Negative instructions clarify what NOT to do - [ ] No contradictory instructions - [ ] Few-shot examples included for ambiguous tasks - [ ] Chain-of-thought used for multi-step reasoning tasks **Tool Descriptions** - [ ] Every tool has a multi-line description: what, when to use, when NOT to use, returns - [ ] Input parameters have descriptions and types - [ ] Error responses are documented - [ ] At least one example input/output in the description **Error Messages** - [ ] Error messages are specific (not "an error occurred") - [ ] Error messages suggest corrective action - [ ] Errors include context (what was being attempted) - [ ] Errors are structured (code + message + details) **Logging** - [ ] Every model call is logged (input tokens, output tokens, latency, cost) - [ ] Tool calls are logged with inputs and outputs - [ ] Errors are logged with full context - [ ] PII is redacted from logs - [ ] Workflow ID traces through all log entries **Configuration** - [ ] All magic numbers are named constants - [ ] Environment-specific values are in config, not code - [ ] Defaults are sensible — config is for overrides - [ ] Cost ceilings are set - [ ] Timeout values are set for all external calls ### Output For each checklist item that fails, provide: 1. What's wrong (specific finding) 2. Where it is (file, line, or component) 3. How to fix it (concrete suggestion) 4. Priority (critical / important / nice-to-have) ### Priority Matrix | Priority | Criteria | Maestro Action | |----------|---------|----------------| | Critical | Affects correctness or safety | `/fortify` or `/guard` before shipping | | Important | Affects quality or maintainability | `/calibrate` in current cycle | | Nice-to-have | Cosmetic or minor inconsistency | Note for next `/refine` pass | ### Recommended Next Step After refinement is complete, run `/evaluate` to verify the polished workflow against realistic scenarios. **NEVER**: - Skip the checklist — go through every item - Mark items as passing without checking - Suggest changes that alter behavior (this is polish, not redesign) - Refine before the workflow is functionally correct (fix first, refine last)
Excerpt, first 2,922 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
- ✓SAFE 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 Refine
What does the Refine skill do?
Is Refine safe to install?
What can Refine access on my machine?
How current is this page?
Sources
- github.com/sharpdeveye/maestro/tree/main/source/skills/refine — 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 Refine skill do?
- Is Refine safe to install?
- What can Refine access on my machine?