Practice Compiler
Turn your work sessions into evidence-backed improvement proposals.
- What
- Turn your work sessions into evidence-backed improvement proposals.
- Cost
- Free
- Needs
- None — no account, no API key. Python 3 is needed only if you run the skill's helper scripts.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that mines a bounded window of your own work sessions (Muse, Codex, or Claude Code exports) for repeated tasks, recurring corrections, missed tools, and failed commands — then stages redacted, evidence-backed improvement proposals for your review. It never scans implicitly and never applies a proposal: approval produces a handoff record only, never a memory write, config edit, publication, or message. Scans need an exact --since/--until window and repeated evidence (min 2 occurrences). No account, no API key needed.
Curated by Skill Harbor — free, open-source build (MIT) by @Israelmusondaayliffe.
Version:
Install
Prerequisites: None — no account, no API key. Python 3 is needed only if you run the skill's helper scripts. No GitHub account needed unless listed here. Install "Practice Compiler" for me. A Muse agent skill that mines your own work sessions for repeated tasks and recurring corrections, then stages evidence-backed improvement proposals for your review. Repository: https://github.com/Israelmusondaayliffe/muse-skills/tree/main/skills/practice-compiler 1. Fetch the SKILL.md file, scripts, and references from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and Python scripts for anything suspicious (unexpected network calls, system commands, credential harvesting). STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md, the scripts, and references into the agent's skills directory, in a folder named "practice-compiler". 4. Verify with no network calls: frontmatter valid, Python scripts compile. 5. Report what was installed, where, and what I still need to do myself. 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 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.