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
- 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.
Curated by Skill Harbor — @marimo-team's session-retrospective skill for the marimo-pair pairing workflow. After a pairing session, the skill helps a marimo team member review the conversation for friction — user frustration, inefficiency, errors, workarounds, context loss — present the friction points and let the user choose which to dig into. Root-cause discussion runs through seven lenses (skill structure, skill gap, misleading docs, API ergonomics, missing API, API bug, context window) and converges on a diagnosis; the default outcome is to capture it as an issue or discussion for the team to triage — never edit the skill or the underlying `marimo._code_mode` API without explicit user approval, and never auto-file. Honest caveats: written for the marimo team itself — the guardrails assume you're contributing to marimo-pair, so it's most useful to marimo contributors or anyone iterating on their own agent skills; strictly diagnosis, never authoring fixes. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
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://github.com/marimo-team/marimo-pair/blob/main/skills/retro-marimo-pair/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.