[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APTAYVPE1B8VQPEGX6K8S1":3,"skill-same:01M7APTAYVPE1B8VQPEGX6K8S1":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7APTAYVPE1B8VQPEGX6K8S1","growth-log",null,"Use after a complex task, failure, or when reviewing what was learned. Teaches how to write growth logs that extract reusable patterns — not diary entries.","Cyrilthetecchieee\u002Fcyril-code-","Cyrilthetecchieee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219787998?v=4","01M7AF0MMMKRAA0H61XMJPV92H","Julian Cyril D ","01M7AF0MQ10AVG6QJQ1C2BC0F5",2,"MIT","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fgrowth-log\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: growth-log\ndescription: \"Use after a complex task, failure, or when reviewing what was learned. Teaches how to write growth logs that extract reusable patterns — not diary entries.\"\nmetadata:\n  version: 1.1.0\n  origin: ECC\n---\n\n# Growth Log Skill\n\n> **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.\n>\n> **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.\n\n## When to Activate\n\n- After completing a complex task (multi-file, new feature, architecture change)\n- After a failure, mistake, or \"that was harder than expected\" moment\n- When you want to review what you've learned over a period\n\n**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.\n\n## The Three Rules\n\n### Rule 1: Failures > Achievements\n\nA failure is nutritionally denser than a success. One bug that took 2 hours to find teaches more than 3 features that worked first try.\n\n**Bad:** \"Successfully implemented the login flow.\"\n**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.\"\n**Good (data pipeline):** \"CSV import failed silently on empty rows because `pandas.read_csv(dropna=False)` keeps zero-width rows that `len()` counts as valid. Pattern: always `df.dropna(how='all', inplace=True)` before row-count validation.\"\n\n### Rule 2: The Bole Principle (伯乐原则)\n\nBefore writing a new entry, ask: *\"Is this fundamentally the same as something I already recorded?\"*\n\nSame root cause, different symptom → **merge**, don't duplicate. New root cause → new entry.\n\n**How to check:** Search existing entries for keywords from your root cause before writing. If you find a match, add your new symptom as an additional example under the existing entry rather than creating a duplicate.\n\n**Example:** \"Forgot to update the output index after creating a file\" and \"Forgot to update skill ratings after a task\" — same root cause (no automatic capture trigger). Merge into one entry about \"post-task capture gaps.\"\n\n### Rule 3: Must Be Transferable\n\nEvery entry must answer: *\"Next time I face a similar situation, what do I do differently?\"*\n\nIf you can't write that sentence, you haven't extracted the pattern yet.\n\n**How to extract a pattern from a concrete event:**\n1. State what happened in one sentence\n2. Ask \"why?\" iteratively until you reach root cause (usually 3-5 whys)\n3. Generalize: \"What class of problem is this?\" (not \"Chrome 128 bug\" but \"browser default change breaking existing behavior\")\n4. Formulate as: \"Next time I see [signal], I will [action].\"\n5. Name the signal: what specific observable tells you this pattern is active?\n\n## Entry Template\n\n**Scope:** One entry per distinct root cause. Typical length: 4-8 sentences. If it takes >2 minutes to write, you're narrating events. If \u003C30 seconds, you haven't gone deep enough.\n\n```markdown\n## [Title: the pattern, not the event]\n\n### Context\n- What was I trying to do?\n- What went wrong \u002F what worked surprisingly well?\n\n### Root Cause \u002F Core Insight\n- The underlying mechanism, not just the symptom\n\n### The Pattern (transferable)\n- Next time [similar situation], I will [specific action].\n- Signal to recognize: [what observable tells me this pattern is active?]\n\n### Related\n- [entry-name](..\u002Fpath\u002Fto\u002Frelated-entry.md)\n```\n\n## Entry Types\n\nAll four types use the template above. The type determines which sections carry the most weight:\n\n| Type | When to Use | Emphasis | Example Title |\n|------|------------|----------|---------------|\n| **Failure** | Something broke, needed debugging, or required rework | Root Cause | \"Config inheritance ≠ behavior inheritance across sessions\" |\n| **Methodology** | A repeatable process emerged from the work | Context \u002F Pattern | \"PPT → open-book exam study guide: three-layer structure\" |\n| **Pattern Discovery** | A reusable insight about tools, systems, or thinking | Pattern section | \"PR description template: describe the gap, not the feature\" |\n| **Capability Change** | A measurable skill improvement | Context (before vs after) | \"Git: from clone\u002Fpush to independent PR with 12 commits\" |\n\n## Quality Checklist\n\nBefore finalizing a growth log entry:\n\n- [ ] Does the title name the *pattern*, not the event?\n- [ ] Is there a \"Next time I will...\" sentence?\n- [ ] Is the \"Signal to recognize\" specific enough to trigger the pattern next time?\n- [ ] Did I search existing entries for duplicates before writing? (Bole Principle)\n- [ ] Is the root cause distinguished from the symptom?\n- [ ] Are related memories cross-linked?\n- [ ] Is the entry 4-8 sentences? Shorter = too shallow; longer = narrating events.\n\n## Anti-Patterns\n\n- Avoid: \"Fixed bug in payment module\" (event, not pattern)\n- Avoid: Copying the git commit message verbatim (commits describe what changed; logs extract why it matters)\n- Avoid: Writing an entry for every commit (only when a pattern emerges)\n- Avoid: Skipping the transferable sentence (without it, it's just a diary — this is non-negotiable)\n- Avoid: Duplicating the same pattern under different titles (violates Bole Principle — search before writing)\n\n## Storage\n\nStore entries wherever you keep notes. Common patterns:\n- Markdown files in a `growth-log\u002F` directory (one file per day: `YYYY-MM-DD.md`)\n- A dedicated section in Notion, Obsidian, or your note-taking app\n- Plain text files with a consistent naming convention\n\nPick one convention and stick to it. Searchability matters more than format.\n\n## If You Use Delivery Gate\n\nThe `delivery-gate` Stop hook checks that learning files were modified today via filesystem timestamps. This skill teaches *what to write* — so the file that delivery-gate checks actually contains useful patterns, not empty timestamps.\n\n```\nTask completes → delivery-gate checks: was the learning file touched today?\n  → Stale (no file modified): block — \"what did you learn?\"\n  → Fresh (file touched): pass — this skill ensures the content is useful\n```\n\nHaving enforcement without methodology → empty entries. Having methodology without enforcement → forgotten captures. Each is independently useful; together they close the loop.\n","# Growth Log Skill\n\n> **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.\n>\n> **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.\n\n## When to Activate\n\n- After completing a complex task (multi-file, new feature, architecture change)\n- After a failure, mistake, or \"that was harder than expected\" moment\n- When you want to review what you've learned over a period\n\n**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.\n\n## The Three Rules\n\n### Rule 1: Failures > Achievements\n\nA failure is nutritionally denser than a success. One bug that took 2 hours to find teaches more than 3 features that worked first try.\n\n**Bad:** \"Successfully implemented the login flow.\"\n**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.\"\n**Good (data pipeline):** \"CSV import failed silently on empty rows because `pandas.read_csv(dropna=False)` keeps zero-width rows that `len()` counts as valid. Pattern: always `df.dropna(how='all', inplace=True)` before row-count validation.\"\n\n### Rule 2: The Bole Principle (伯乐原则)\n\nBefore writing a new entry, ask: *\"Is this fundamentally the same as something I already recorded?\"*\n\nSame root cause, different symptom → **merge**, don't duplicate. New root cause → new entry.\n\n**How to check:** Search existing entries for keywords from your root cause before writing. If you find a match, add your new symptom as an additional example under the existing entry rather than creating a duplicate.\n\n**Example:** \"Forgot to update the output index after creating a file\" and \"Forgot to update skill ratings after a task\" — same root cause (no automatic capture trigger). Merge into one entry about \"post-task capture gaps.\"\n\n### Rule 3: Must Be Transferable\n\nEvery entry must answer: *\"Next time I face a similar situation, what do I do differently?\"*\n\nIf you can't write that sentence, you haven't extracted the pattern yet.\n\n**How to extract a pattern from a concrete event:**\n1. State what happened in one sentence\n2. Ask \"why?\" iteratively until you reach root cause (usually 3-5 whys)\n3. Generalize: \"What class of problem is this?\" (not \"Chrome 128 bug\" but \"browser default change breaking existing behavior\")\n4. Formulate as: \"Next time I see [signal], I will [action].\"\n5. Name the signal: what specific observable tells you this pattern is active?\n\n## Entry Template\n\n**Scope:** One entry per distinct root cause. Typical length: 4-8 sentences. If it takes >2 minutes to write, you're narrating events. If \u003C30 seconds, you haven't gone deep enough.\n\n```markdown\n## [Title: the pattern, not the event]\n\n### Context\n- What was I trying to do?\n- What went wrong \u002F what worked surprisingly well?\n\n### Root Cause \u002F Core Insight\n- The underlying mechanism, not just the symptom\n\n### The Pattern (transferable)\n- Next time [similar situation], I will [specific action].\n- Signal to recognize: [what observable tells me this pattern is active?]\n\n### Related\n- [entry-name](..\u002Fpath\u002Fto\u002Frelated-entry.md)\n```\n\n## Entry Types\n\nAll four types use the template above. The type determines which sections carry the most weight:\n\n| Type | When to Use | Emphasis | Example Title |\n|------|------------|----------|---------------|\n| **Failure** | Something broke, needed debugging, or required rework | Root Cause | \"Config inheritance ≠ behavior inheritance across sessions\" |\n| **Methodology** | A repeatable process emerged from the work | Context \u002F Pattern | \"PPT → open-book exam study guide: three-layer structure\" |\n| **Pattern Discovery** | A reusable insight about tools, systems, or thinking | Pattern section | \"PR description template: describe the gap, not the feature\" |\n| **Capability Change** | A measurable skill improvement | Context (before vs after) | \"Git: from clone\u002Fpush to independent PR with 12 commits\" |\n\n## Quality Checklist\n\nBefore finalizing a growth log entry:\n\n- [ ] Does the title name the *pattern*, not the event?\n- [ ] Is there a \"Next time I will...\" sentence?\n- [ ] Is the \"Signal to recognize\" specific enough to trigger the pattern next time?\n- [ ] Did I search existing entries for duplicates before writing? (Bole Principle)\n- [ ] Is the root cause distinguished from the symptom?\n- [ ] Are related memories cross-linked?\n- [ ] Is the entry 4-8 sentences? Shorter = too shallow; longer = narrating events.\n\n## Anti-Patterns\n\n- Avoid: \"Fixed bug in payment module\" (event, not pattern)\n- Avoid: Copying the git commit message verbatim (commits describe what changed; logs extract why it matters)\n- Avoid: Writing an entry for every commit (only when a pattern emerges)\n- Avoid: Skipping the transferable sentence (without it, it's just a diary — this is non-negotiable)\n- Avoid: Duplicating the same pattern under different titles (violates Bole Principle — search before writing)\n\n## Storage\n\nStore entries wherever you keep notes. Common patterns:\n- Markdown files in a `growth-log\u002F` directory (one file per day: `YYYY-MM-DD.md`)\n- A dedicated section in Notion, Obsidian, or your note-taking app\n- Plain text files with a consistent naming convention\n\nPick one convention and stick to it. Searchability matters more than format.\n\n## If You Use Delivery Gate\n\nThe `delivery-gate` Stop hook checks that learning files were modified today via filesystem timestamps. This skill teaches *what to write* — so the file that delivery-gate checks actually contains useful patterns, not empty timestamps.\n\n```\nTask completes → delivery-gate checks: was the learning file touched today?\n  → Stale (no file modified): block — \"what did you learn?\"\n  → Fresh (file touched): pass — this skill ensures the content is useful\n```\n\nHaving enforcement without methodology → empty entries. Having methodology without enforcement → forgotten captures. Each is independently useful; together they close the loop.\n",{"name":5,"metadata":24,"description":7},{"origin":25,"version":26},"ECC","1.1.0","main","57e7aa6b6e03bce1a7d7862ba9c2ec312f7f19b5","src\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fgrowth-log",0,"https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee","https:\u002F\u002Fwithcyril.me\u002F","Hi, I’m Julian Cyril D, a Computer Science and Business Systems student at PSNACET.\r\nI’m passionate about full-stack development, UI\u002FUX design, and building sma","2026-11-04 23:28:50",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Cyrilthetecchieee\u002Fcyril-code- --skill growth-log",{"tool":42,"command":43},"bunx","bunx skills add Cyrilthetecchieee\u002Fcyril-code- --skill growth-log",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Cyrilthetecchieee\u002Fcyril-code- --skill growth-log","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fskills\u002Fgrowth-log\u002FSKILL.md",true,[],[51,60,67,75,82,89],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":56,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7AQV6CYX8RMC78420V9WZ62","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AQV2895N3S1MEX6K76G6G2","youtube-downloader","Download YouTube videos with customizable quality and format options. Use this skill when the user asks to download, save, or grab YouTube videos. Supports various quality settings (best, 1080p, 720p, 480p, 360p), multiple formats (mp4, webm, mkv), and audio-only downloads as MP3.","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fvideo-downloader\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AQTRNX62DNKVZ5GXEHRBKB","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AQTNNVHAAN9H6DA8T6ZVE0","template-skill","Replace with description of the skill and when Claude should use it.","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftemplate-skill\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AQTJ3MQ6AKX152MEX2MYCC","tailored-resume-generator","Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Ftailored-resume-generator\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":55,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7AQTD7D5MYET2YWG7HG9WM3","slack-gif-creator","Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like \"make me a GIF for Slack of X doing Y\".","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCyrilthetecchieee\u002Fcyril-code-\u002Fblob\u002Fmain\u002Fsrc\u002Fcyril_code\u002Fassets\u002F.skills_repo\u002Fslack-gif-creator\u002FSKILL.md",[],[]]