Muse Skills — Review Loops
Adversarial review skills that catch what two reviewers missed
- What
- Adversarial review skills that catch what two reviewers missed
- Cost
- Free
- Needs
- None — no account, no API key.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Adversarial-review and fix-verification skills for Muse sessions, built after an independent review caught 13 real issues two reviewers missed.
Curated by Skill Harbor — free community build by @seb-patron. No license file in the repo — review the code before use.
Version:
Quick answer
Muse Skills Review Loops is a free Muse skill offering adversarial review skills that catch what two reviewers missed. It adds a structured, challenging review loop on top of normal review, questioning assumptions and probing weak points. Teams get a second, deliberately sceptical pass before code or decisions go forward.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 937f204Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: None — no account, no API key. No GitHub account needed unless listed here. Install "Muse Skills — Review Loops" for me. Two code-review skills — verify a fix batch against review findings, and run an adversarial pre-verdict probe on a diff. Repository: https://github.com/seb-patron/muse-skills Pinned version: install the code at commit 937f2041cded9ae422c1ec0bbebbbab144a40504 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone the repo into a temporary folder (public HTTPS clone — no account needed) and look inside. 2. Safety check: briefly review any scripts for anything suspicious (network calls to unexpected hosts, shell commands, credential harvesting). The evals/ and scripts/ folders are the creator's dev tooling — don't install or run them. If you see a red flag, stop and tell me before going further. 3. Install the skills: create one folder per skill in my agent's skills directory and copy each skill's own folder there (SKILL.md plus its files). 'Install both skills (fix-verification and adversarial-review).' 4. Verify without network calls: each installed SKILL.md has valid frontmatter (name + description). 5. Report: what you installed, where, and anything still left for me to do myself (or confirm there's nothing left). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it (e.g. authenticated clone); otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 937f204 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.