Agent skill · marketing growth · affaan-m
growth-log
Write growth log entries that extract reusable patterns from completed work — root cause, transferable rule, and a recognizable signal — instead of diary-style event narration, with a 4-8 sentence template and merge-duplicates discipline. Use when capturing what was learned after a complex task, debugging session, failure, or rollback, when reviewing progress over a period, or when a delivery gate asks what was learned.
Why this skill is useful
Provides a structured approach to documenting learning experiences that helps identify and extract reusable patterns, which the AI may not generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
Growth Log Skill The problem: Most people write "fixed a bug in X" as a learning log. That's a diary entry, not a learning artifact. A real growth log extracts the pattern so you recognize it next time. This skill teaches: How to write learning entries that compound across sessions. Works with any note-taking system — Markdown files, Notion, Obsidian, plain text. Templates are generic; adapt to your setup. When to Activate After completing a complex task (multi-file, new feature, architecture change) After a failure, mistake, or "that was harder than expected" moment When you want to review what you've learned over a period When NOT to activate: Trivial changes (typo fixes, single-line tweaks, config value changes with no debugging). The threshold: did this task involve debugging, redoing, rollback, or a non-obvious decision? If yes → write an entry. If no → skip. The Three Rules Rule 1: Failures > Achievements A failure is nutritionally denser than a success. One bug that took 2 hours to find teaches more than 3 features that worked first try. Bad: "Successfully implemented the login flow." Good (web dev): "Login flow: session token wasn't persisting because the cookie SameSite defaulted to Lax in Chrome 128+. Pattern: always explicitly set SameSite=None; Secure when cross-origin. Signal to recognize: auth breaks after browser upgrade or when crossing origin boundaries." Good (data pipeline): "CSV import failed silently on empty rows because pandas.readcsv(dropna=False) keeps zero-width rows that len() counts as valid. Pattern: always df.dropna(how='all', inplace=True) before row-count validation." Rule 2: The Bole Principle (伯乐原则) Before writing a new entry, ask: "Is this fundamentally the same as something I already recorded?" Same root cause, different symptom → merge, don't duplicate. New root cause → new entry. How to check: Search existing entries for keywords from your root cause before writing. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/growth-log--f373ac