← Search

Session retrospective: turn pairing friction with marimo into improvements
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 2f1d7ff
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: nothing to install…

Session retrospective: turn pairing friction with marimo into improvements

Review a marimo-pair session for friction, discuss root causes through seven lenses, and capture the diagnosis as an issue

At a glance
What
Review a marimo-pair session for friction, discuss root causes through seven lenses, and capture the diagnosis as an issue
Cost
Free
Needs
nothing to install — the skill is a conversational retrospective methodology your agent follows; most useful if you contribute to marimo-pair or iterate on your own agent skills
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Session retrospective is a free Muse skill for reviewing a marimo-pair session for friction, then turning that friction into improvements. It discusses root causes through seven lenses, so problems are understood rather than just listed. The diagnosis is captured as an issue, making the next pairing session smoother and the improvement trackable.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 2f1d7ff

Step 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: nothing to install — the skill is a conversational retrospective methodology your agent follows; most useful if you contribute to marimo-pair or iterate on your own agent skills Install "Session retrospective: turn pairing friction with marimo into improvements" for me. It gives my agent @marimo-team's retrospective workflow: analyze the just-finished pairing session for friction (frustration, inefficiency, errors, workarounds, context loss), present friction points and let me pick which to dig into, discuss root causes through seven lenses (skill structure, skill gap, misleading docs, API ergonomics, missing API, API bug, context window), capture the diagnosis as a draft issue/discussion — with strict guardrails: never edit files or auto-file without explicit approval; diagnosis only, never authoring fixes. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/marimo-team/marimo-pair/2f1d7fffa50607dc9d8660cb931f4470707f8697/skills/retro-marimo-pair/SKILL.md Pinned version: install the code at commit 2f1d7fffa50607dc9d8660cb931f4470707f8697 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "retro-marimo-pair". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — invoke it after a pairing session you want to retrospect on). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 2f1d7ff · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
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
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
2f1d7ff · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
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.