Growth Log Pattern Extraction
Turn completed work into compounding learning with Muse: extract the reusable pattern (root cause, transferable rule, recognizable signal) instead of diary-style event narration. 4-8 sentence template.
- What
- Turn completed work into compounding learning with Muse: extract the reusable pattern (root cause, transferable rule, recognizable signal) instead of diary-style event narration. 4-8 sentence template.
- Cost
- Free
- Needs
- Use "Growth Log Pattern Extraction" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a methodology that fixes the most common learning-log failure, writing "fixed a bug in X" and calling it growth. A real growth log extracts the pattern so you recognize it next time. Three rules govern every entry. Rule 1, failures beat achievements: one two-hour bug teaches more than three features that worked first try, so write the pattern (session cookie SameSite defaulting to Lax in Chrome 128+, pattern: always set SameSite=None; Secure explicitly) not the event. Rule 2, the Bole Principle: before writing, search existing entries for the same root cause; same root cause with different symptoms gets merged, never duplicated. Rule 3, every entry must be transferable: if you cannot write "next time I see [signal], I will [action]", you have not extracted the pattern yet. The template runs 4-8 sentences across Context, Root Cause, The Pattern, and Related sections, with four entry types (Failure, Methodology, Pattern Discovery, Capability Change) and a quality checklist covering title discipline, the transferable sentence, signal specificity, and duplicate search. It pairs with the delivery-gate Stop hook: the hook enforces that a learning file was touched today, this skill ensures the content inside is worth keeping. Works with any note system: Markdown files, Notion, Obsidian, plain text. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: only log when a pattern emerges (debugging, redo, rollback, non-obvious decision); writing an entry for every trivial commit produces noise, and skipping the transferable sentence produces a diary. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Growth Log Pattern Extraction" with your Muse. Prerequisites: none to install. Pure guidance; any note-taking system works (Markdown, Notion, Obsidian, plain text). 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/growth-log/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Help me write a growth log entry for [task/debugging session]" or "Review my last week and extract the patterns worth keeping." 3. Work through the template with Muse: context, root cause, transferable pattern with a recognizable signal. Search your existing entries first (Bole Principle) to merge duplicates. Tip: if it takes more than 2 minutes to write, you are narrating events; if under 30 seconds, you have not gone deep enough. Safety: a skill is plain-text instructions; it runs nothing by itself. Keep private project details out of entries you share publicly.
Saved to your recent installs. Find it anytime on /connect.
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.