[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DJVCF6XSZF3F4C4B0HT4XN":3,"skill-same:01M6DJVCF6XSZF3F4C4B0HT4XN":77},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6DJVCF6XSZF3F4C4B0HT4XN","gstack-openclaw-retro",null,"Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.","garrytan\u002Fgstack","garrytan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F19957?v=4","01M6DJCCDDG53MTYYRTXAXFG17","Garry Tan","01M6DJCCKGZB08AY82GDQXVJ8G",141234,"MIT","https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fopenclaw\u002Fskills\u002Fgstack-openclaw-retro\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"retro","gstack openclaw retro","gstack","openclaw","tracking","when","weekly","for","with","trend","code quality metrics","patterns","use","growth","work","history","quality","team","engineering","metrics","code","retrospective","code quality","commit","2026-11-10 10:12:30",false,"---\nname: gstack-openclaw-retro\ndescription: \"Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.\"\n---\n\n# Weekly Engineering Retrospective\n\nGenerates a comprehensive engineering retrospective analyzing commit history, work patterns, and code quality metrics. Team-aware: identifies the user running the command, then analyzes every contributor with per-person praise and growth opportunities.\n\n## Arguments\n\n- Default: last 7 days\n- `24h`: last 24 hours\n- `14d`: last 14 days\n- `30d`: last 30 days\n- `compare`: compare current window vs prior same-length window\n\n## Instructions\n\nParse the argument to determine the time window. Default to 7 days. All times should be reported in the user's **local timezone**.\n\n**Midnight-aligned windows:** For day units, compute an absolute start date at local midnight. For example, if today is 2026-03-18 and the window is 7 days, the start date is 2026-03-11. Use `--since=\"2026-03-11T00:00:00\"` for git log queries. For hour units, use `--since=\"N hours ago\"`.\n\n---\n\n### Step 1: Gather Raw Data\n\nFirst, fetch origin and identify the current user:\n\n```bash\ngit fetch origin main --quiet\ngit config user.name\ngit config user.email\n```\n\nThe name returned by `git config user.name` is **\"you\"** ... the person reading this retro. All other authors are teammates.\n\nRun ALL of these git commands (they are independent):\n\n```bash\n# All commits with timestamps, subject, hash, author, files changed\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"%H|%aN|%ae|%ai|%s\" --shortstat\n\n# Per-commit test vs total LOC breakdown with author\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"COMMIT:%H|%aN\" --numstat\n\n# Commit timestamps for session detection and hourly distribution\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"%at|%aN|%ai|%s\" | sort -n\n\n# Files most frequently changed (hotspot analysis)\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"\" --name-only | grep -v '^$' | sort | uniq -c | sort -rn\n\n# PR numbers from commit messages\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"%s\" | grep -oE '[#!][0-9]+' | sort -t'#' -k1 | uniq\n\n# Per-author file hotspots\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"AUTHOR:%aN\" --name-only\n\n# Per-author commit counts\ngit shortlog origin\u002Fmain --since=\"\u003Cwindow>\" -sn --no-merges\n\n# Test file count\ngit ls-files 2>\u002Fdev\u002Fnull | grep -E '(\\.test\\.|\\.spec\\.|_test\\.|_spec\\.)' | wc -l\n\n# Test files changed in window\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"\" --name-only | grep -E '\\.(test|spec)\\.' | sort -u | wc -l\n```\n\n---\n\n### Step 2: Compute Metrics\n\nCalculate and present these metrics in a summary:\n\n- **Commits to main:** N\n- **Contributors:** N\n- **PRs merged:** N\n- **Total insertions:** N\n- **Total deletions:** N\n- **Net LOC added:** N\n- **Test LOC (insertions):** N\n- **Test LOC ratio:** N%\n- **Version range:** vX.Y.Z → vX.Y.Z\n- **Active days:** N\n- **Detected sessions:** N\n- **Avg LOC\u002Fsession-hour:** N\n\nThen show a **per-author leaderboard** immediately below:\n\n```\nContributor         Commits   +\u002F-          Top area\nYou (garry)              32   +2400\u002F-300   browse\u002F\nalice                    12   +800\u002F-150    app\u002Fservices\u002F\nbob                       3   +120\u002F-40     tests\u002F\n```\n\nSort by commits descending. The current user always appears first, labeled \"You (name)\".\n\n---\n\n### Step 3: Commit Time Distribution\n\nShow hourly histogram in local time:\n\n```\nHour  Commits  ████████████████\n 00:    4      ████\n 07:    5      █████\n ...\n```\n\nIdentify:\n- Peak hours\n- Dead zones\n- Bimodal pattern (morning\u002Fevening) vs continuous\n- Late-night coding clusters (after 10pm)\n\n---\n\n### Step 4: Work Session Detection\n\nDetect sessions using **45-minute gap** threshold between consecutive commits.\n\nClassify sessions:\n- **Deep sessions** (50+ min)\n- **Medium sessions** (20-50 min)\n- **Micro sessions** (\u003C20 min, single-commit)\n\nCalculate:\n- Total active coding time\n- Average session length\n- LOC per hour of active time\n\n---\n\n### Step 5: Commit Type Breakdown\n\nCategorize by conventional commit prefix (feat\u002Ffix\u002Frefactor\u002Ftest\u002Fchore\u002Fdocs). Show as percentage bar:\n\n```\nfeat:     20  (40%)  ████████████████████\nfix:      27  (54%)  ███████████████████████████\nrefactor:  2  ( 4%)  ██\n```\n\nFlag if fix ratio exceeds 50% ... signals a \"ship fast, fix fast\" pattern that may indicate review gaps.\n\n---\n\n### Step 6: Hotspot Analysis\n\nShow top 10 most-changed files. Flag:\n- Files changed 5+ times (churn hotspots)\n- Test files vs production files in the hotspot list\n- VERSION\u002FCHANGELOG frequency\n\n---\n\n### Step 7: PR Size Distribution\n\nEstimate PR sizes and bucket them:\n- **Small** (\u003C100 LOC)\n- **Medium** (100-500 LOC)\n- **Large** (500-1500 LOC)\n- **XL** (1500+ LOC)\n\n---\n\n### Step 8: Focus Score + Ship of the Week\n\n**Focus score:** Percentage of commits touching the single most-changed top-level directory. Higher = deeper focused work. Lower = scattered context-switching.\n\n**Ship of the week:** The single highest-LOC PR in the window. Highlight PR number, LOC changed, and why it matters.\n\n---\n\n### Step 9: Team Member Analysis\n\nFor each contributor (including the current user), compute:\n\n1. **Commits and LOC** ... total commits, insertions, deletions, net LOC\n2. **Areas of focus** ... which directories\u002Ffiles they touched most (top 3)\n3. **Commit type mix** ... their personal feat\u002Ffix\u002Frefactor\u002Ftest breakdown\n4. **Session patterns** ... when they code (peak hours), session count\n5. **Test discipline** ... their personal test LOC ratio\n6. **Biggest ship** ... their single highest-impact commit or PR\n\n**For the current user (\"You\"):** Deepest treatment. Include all session analysis, time patterns, focus score. Frame in first person.\n\n**For each teammate:** 2-3 sentences covering what they shipped and their pattern. Then:\n\n- **Praise** (1-2 specific things): Anchor in actual commits. Not \"great work\" ... say exactly what was good.\n- **Opportunity for growth** (1 specific thing): Frame as leveling-up, not criticism. Anchor in actual data.\n\n**If solo repo:** Skip team breakdown.\n\n**AI collaboration:** If commits have `Co-Authored-By` AI trailers, track \"AI-assisted commits\" as a separate metric.\n\n---\n\n### Step 10: Week-over-Week Trends (if window >= 14d)\n\nSplit into weekly buckets and show trends:\n- Commits per week (total and per-author)\n- LOC per week\n- Test ratio per week\n- Fix ratio per week\n- Session count per week\n\n---\n\n### Step 11: Streak Tracking\n\nCount consecutive days with at least 1 commit, going back from today:\n\n```bash\n# Team streak\ngit log origin\u002Fmain --format=\"%ad\" --date=format:\"%Y-%m-%d\" | sort -u\n\n# Personal streak\ngit log origin\u002Fmain --author=\"\u003Cuser_name>\" --format=\"%ad\" --date=format:\"%Y-%m-%d\" | sort -u\n```\n\nDisplay both:\n- \"Team shipping streak: 47 consecutive days\"\n- \"Your shipping streak: 32 consecutive days\"\n\n---\n\n### Step 12: Load History & Compare\n\nCheck for prior retro history in `memory\u002F`:\n\nIf prior retros exist, load the most recent one and calculate deltas:\n\n```\n                    Last        Now         Delta\nTest ratio:         22%    →    41%         ↑19pp\nSessions:           10     →    14          ↑4\nLOC\u002Fhour:           200    →    350         ↑75%\nFix ratio:          54%    →    30%         ↓24pp (improving)\n```\n\nIf no prior retros exist, note \"First retro recorded, run again next week to see trends.\"\n\n---\n\n### Step 13: Save Retro History\n\nSave a JSON snapshot to `memory\u002Fretro-YYYY-MM-DD.json` with metrics, authors, version range, streak, and tweetable summary.\n\n---\n\n### Step 14: Write the Narrative\n\n**Format for Telegram** (bullets, bold, no markdown tables in the final output).\n\nStructure:\n\n**Tweetable summary** (first line):\n> Week of Mar 1: 47 commits (3 contributors), 3.2k LOC, 38% tests, 12 PRs, peak: 10pm | Streak: 47d\n\nThen sections:\n\n- **Summary** ... key metrics\n- **Trends vs Last Retro** ... deltas (skip if first retro)\n- **Time & Session Patterns** ... when the team codes, session lengths, deep vs micro\n- **Shipping Velocity** ... commit types, PR sizes, fix-chain detection\n- **Code Quality Signals** ... test ratio, hotspots, churn\n- **Focus & Highlights** ... focus score, ship of the week\n- **Your Week** ... personal deep-dive for the current user\n- **Team Breakdown** ... per-teammate analysis with praise + growth (skip if solo)\n- **Top 3 Team Wins** ... highest-impact things shipped\n- **3 Things to Improve** ... specific, actionable, anchored in commits\n- **3 Habits for Next Week** ... small, practical, realistic (\u003C5 min to adopt)\n\n---\n\n## Compare Mode\n\nWhen the user says \"compare\":\n- Run the retro for the current window\n- Run the retro for the prior same-length window\n- Present side-by-side metrics with arrows showing improvement\u002Fregression\n- Brief narrative on biggest changes\n\n---\n\n## Important Rules\n\n- **All times in local timezone.** Never set `TZ`.\n- **Format for Telegram.** Use bullets and bold. Avoid markdown tables in the final output.\n- **Praise anchored in commits.** Never say \"great work\" without naming what was good.\n- **Growth areas anchored in data.** Never criticize without evidence.\n- **Save history.** Every retro saves to `memory\u002F` for trend tracking.\n- **Completion status:**\n  - DONE ... retro generated, history saved\n  - DONE_WITH_CONCERNS ... generated but missing data (e.g., no prior retros for comparison)\n  - BLOCKED ... not in a git repo or no commits in window\n","# Weekly Engineering Retrospective\n\nGenerates a comprehensive engineering retrospective analyzing commit history, work patterns, and code quality metrics. Team-aware: identifies the user running the command, then analyzes every contributor with per-person praise and growth opportunities.\n\n## Arguments\n\n- Default: last 7 days\n- `24h`: last 24 hours\n- `14d`: last 14 days\n- `30d`: last 30 days\n- `compare`: compare current window vs prior same-length window\n\n## Instructions\n\nParse the argument to determine the time window. Default to 7 days. All times should be reported in the user's **local timezone**.\n\n**Midnight-aligned windows:** For day units, compute an absolute start date at local midnight. For example, if today is 2026-03-18 and the window is 7 days, the start date is 2026-03-11. Use `--since=\"2026-03-11T00:00:00\"` for git log queries. For hour units, use `--since=\"N hours ago\"`.\n\n---\n\n### Step 1: Gather Raw Data\n\nFirst, fetch origin and identify the current user:\n\n```bash\ngit fetch origin main --quiet\ngit config user.name\ngit config user.email\n```\n\nThe name returned by `git config user.name` is **\"you\"** ... the person reading this retro. All other authors are teammates.\n\nRun ALL of these git commands (they are independent):\n\n```bash\n# All commits with timestamps, subject, hash, author, files changed\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"%H|%aN|%ae|%ai|%s\" --shortstat\n\n# Per-commit test vs total LOC breakdown with author\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"COMMIT:%H|%aN\" --numstat\n\n# Commit timestamps for session detection and hourly distribution\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"%at|%aN|%ai|%s\" | sort -n\n\n# Files most frequently changed (hotspot analysis)\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"\" --name-only | grep -v '^$' | sort | uniq -c | sort -rn\n\n# PR numbers from commit messages\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"%s\" | grep -oE '[#!][0-9]+' | sort -t'#' -k1 | uniq\n\n# Per-author file hotspots\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"AUTHOR:%aN\" --name-only\n\n# Per-author commit counts\ngit shortlog origin\u002Fmain --since=\"\u003Cwindow>\" -sn --no-merges\n\n# Test file count\ngit ls-files 2>\u002Fdev\u002Fnull | grep -E '(\\.test\\.|\\.spec\\.|_test\\.|_spec\\.)' | wc -l\n\n# Test files changed in window\ngit log origin\u002Fmain --since=\"\u003Cwindow>\" --format=\"\" --name-only | grep -E '\\.(test|spec)\\.' | sort -u | wc -l\n```\n\n---\n\n### Step 2: Compute Metrics\n\nCalculate and present these metrics in a summary:\n\n- **Commits to main:** N\n- **Contributors:** N\n- **PRs merged:** N\n- **Total insertions:** N\n- **Total deletions:** N\n- **Net LOC added:** N\n- **Test LOC (insertions):** N\n- **Test LOC ratio:** N%\n- **Version range:** vX.Y.Z → vX.Y.Z\n- **Active days:** N\n- **Detected sessions:** N\n- **Avg LOC\u002Fsession-hour:** N\n\nThen show a **per-author leaderboard** immediately below:\n\n```\nContributor         Commits   +\u002F-          Top area\nYou (garry)              32   +2400\u002F-300   browse\u002F\nalice                    12   +800\u002F-150    app\u002Fservices\u002F\nbob                       3   +120\u002F-40     tests\u002F\n```\n\nSort by commits descending. The current user always appears first, labeled \"You (name)\".\n\n---\n\n### Step 3: Commit Time Distribution\n\nShow hourly histogram in local time:\n\n```\nHour  Commits  ████████████████\n 00:    4      ████\n 07:    5      █████\n ...\n```\n\nIdentify:\n- Peak hours\n- Dead zones\n- Bimodal pattern (morning\u002Fevening) vs continuous\n- Late-night coding clusters (after 10pm)\n\n---\n\n### Step 4: Work Session Detection\n\nDetect sessions using **45-minute gap** threshold between consecutive commits.\n\nClassify sessions:\n- **Deep sessions** (50+ min)\n- **Medium sessions** (20-50 min)\n- **Micro sessions** (\u003C20 min, single-commit)\n\nCalculate:\n- Total active coding time\n- Average session length\n- LOC per hour of active time\n\n---\n\n### Step 5: Commit Type Breakdown\n\nCategorize by conventional commit prefix (feat\u002Ffix\u002Frefactor\u002Ftest\u002Fchore\u002Fdocs). Show as percentage bar:\n\n```\nfeat:     20  (40%)  ████████████████████\nfix:      27  (54%)  ███████████████████████████\nrefactor:  2  ( 4%)  ██\n```\n\nFlag if fix ratio exceeds 50% ... signals a \"ship fast, fix fast\" pattern that may indicate review gaps.\n\n---\n\n### Step 6: Hotspot Analysis\n\nShow top 10 most-changed files. Flag:\n- Files changed 5+ times (churn hotspots)\n- Test files vs production files in the hotspot list\n- VERSION\u002FCHANGELOG frequency\n\n---\n\n### Step 7: PR Size Distribution\n\nEstimate PR sizes and bucket them:\n- **Small** (\u003C100 LOC)\n- **Medium** (100-500 LOC)\n- **Large** (500-1500 LOC)\n- **XL** (1500+ LOC)\n\n---\n\n### Step 8: Focus Score + Ship of the Week\n\n**Focus score:** Percentage of commits touching the single most-changed top-level directory. Higher = deeper focused work. Lower = scattered context-switching.\n\n**Ship of the week:** The single highest-LOC PR in the window. Highlight PR number, LOC changed, and why it matters.\n\n---\n\n### Step 9: Team Member Analysis\n\nFor each contributor (including the current user), compute:\n\n1. **Commits and LOC** ... total commits, insertions, deletions, net LOC\n2. **Areas of focus** ... which directories\u002Ffiles they touched most (top 3)\n3. **Commit type mix** ... their personal feat\u002Ffix\u002Frefactor\u002Ftest breakdown\n4. **Session patterns** ... when they code (peak hours), session count\n5. **Test discipline** ... their personal test LOC ratio\n6. **Biggest ship** ... their single highest-impact commit or PR\n\n**For the current user (\"You\"):** Deepest treatment. Include all session analysis, time patterns, focus score. Frame in first person.\n\n**For each teammate:** 2-3 sentences covering what they shipped and their pattern. Then:\n\n- **Praise** (1-2 specific things): Anchor in actual commits. Not \"great work\" ... say exactly what was good.\n- **Opportunity for growth** (1 specific thing): Frame as leveling-up, not criticism. Anchor in actual data.\n\n**If solo repo:** Skip team breakdown.\n\n**AI collaboration:** If commits have `Co-Authored-By` AI trailers, track \"AI-assisted commits\" as a separate metric.\n\n---\n\n### Step 10: Week-over-Week Trends (if window >= 14d)\n\nSplit into weekly buckets and show trends:\n- Commits per week (total and per-author)\n- LOC per week\n- Test ratio per week\n- Fix ratio per week\n- Session count per week\n\n---\n\n### Step 11: Streak Tracking\n\nCount consecutive days with at least 1 commit, going back from today:\n\n```bash\n# Team streak\ngit log origin\u002Fmain --format=\"%ad\" --date=format:\"%Y-%m-%d\" | sort -u\n\n# Personal streak\ngit log origin\u002Fmain --author=\"\u003Cuser_name>\" --format=\"%ad\" --date=format:\"%Y-%m-%d\" | sort -u\n```\n\nDisplay both:\n- \"Team shipping streak: 47 consecutive days\"\n- \"Your shipping streak: 32 consecutive days\"\n\n---\n\n### Step 12: Load History & Compare\n\nCheck for prior retro history in `memory\u002F`:\n\nIf prior retros exist, load the most recent one and calculate deltas:\n\n```\n                    Last        Now         Delta\nTest ratio:         22%    →    41%         ↑19pp\nSessions:           10     →    14          ↑4\nLOC\u002Fhour:           200    →    350         ↑75%\nFix ratio:          54%    →    30%         ↓24pp (improving)\n```\n\nIf no prior retros exist, note \"First retro recorded, run again next week to see trends.\"\n\n---\n\n### Step 13: Save Retro History\n\nSave a JSON snapshot to `memory\u002Fretro-YYYY-MM-DD.json` with metrics, authors, version range, streak, and tweetable summary.\n\n---\n\n### Step 14: Write the Narrative\n\n**Format for Telegram** (bullets, bold, no markdown tables in the final output).\n\nStructure:\n\n**Tweetable summary** (first line):\n> Week of Mar 1: 47 commits (3 contributors), 3.2k LOC, 38% tests, 12 PRs, peak: 10pm | Streak: 47d\n\nThen sections:\n\n- **Summary** ... key metrics\n- **Trends vs Last Retro** ... deltas (skip if first retro)\n- **Time & Session Patterns** ... when the team codes, session lengths, deep vs micro\n- **Shipping Velocity** ... commit types, PR sizes, fix-chain detection\n- **Code Quality Signals** ... test ratio, hotspots, churn\n- **Focus & Highlights** ... focus score, ship of the week\n- **Your Week** ... personal deep-dive for the current user\n- **Team Breakdown** ... per-teammate analysis with praise + growth (skip if solo)\n- **Top 3 Team Wins** ... highest-impact things shipped\n- **3 Things to Improve** ... specific, actionable, anchored in commits\n- **3 Habits for Next Week** ... small, practical, realistic (\u003C5 min to adopt)\n\n---\n\n## Compare Mode\n\nWhen the user says \"compare\":\n- Run the retro for the current window\n- Run the retro for the prior same-length window\n- Present side-by-side metrics with arrows showing improvement\u002Fregression\n- Brief narrative on biggest changes\n\n---\n\n## Important Rules\n\n- **All times in local timezone.** Never set `TZ`.\n- **Format for Telegram.** Use bullets and bold. Avoid markdown tables in the final output.\n- **Praise anchored in commits.** Never say \"great work\" without naming what was good.\n- **Growth areas anchored in data.** Never criticize without evidence.\n- **Save history.** Every retro saves to `memory\u002F` for trend tracking.\n- **Completion status:**\n  - DONE ... retro generated, history saved\n  - DONE_WITH_CONCERNS ... generated but missing data (e.g., no prior retros for comparison)\n  - BLOCKED ... not in a git repo or no commits in window\n",{"name":5,"description":7},"main","dd9834d44d2650818cb6d8e17c57f795cb56bf98","openclaw\u002Fskills\u002Fgstack-openclaw-retro",20846,"https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack","https:\u002F\u002Fgithub.com\u002Fgarrytan","https:\u002F\u002Fblog.garrytan.com","Writes software, dreams. ","2026-11-12 03:19:55",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add garrytan\u002Fgstack --skill gstack-openclaw-retro",{"tool":63,"command":64},"bunx","bunx skills add garrytan\u002Fgstack --skill gstack-openclaw-retro",{"tool":66,"command":67},"pnpm","pnpm dlx skills add garrytan\u002Fgstack --skill gstack-openclaw-retro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fopenclaw\u002Fskills\u002Fgstack-openclaw-retro\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"SKILL.md.tmpl","OTHER","其他",2724,"https:\u002F\u002Fgithub.com\u002Fchriswestt\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fgstack\u002Fsetup-browser-cookies\u002FSKILL.md.tmpl",[78,109,126,139,158,171],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":89,"publishedAt":43},"01M6DK0K9VCQMFF4BKGT2S57V9","write-skill","Write a new agent skill or improve one without bloat: the edit ladder, levels, drift and size checks, full diets. (gstack)","https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fwrite-skill\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[90,91,92,93,94,95,96,97,98,99,100,101,102,103,21,104,105,106,107,108],"write","write skill","edit","new","bloat","ladder","add","size","diet","full","agent skill","grep","read","write a skill","drift","Bash","improve","new agent","lesson",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":43},"01M6DK0DMV3K47JV0KXTYGZ0F7","verify","Use when coding: run the checks and tests \u002Fship picks until green. (gstack)","https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fverify\u002FSKILL.md",[],[111,116,117,118,31,119,120,101,92,102,121,33,122,21,105,123,124,125,24],"change","it","my","coding","ship","run","check","tests","green","make",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":43},"01M6DK0A63TY611T7G30913VT6","unfreeze","Clear the freeze boundary set by \u002Ffreeze, allowing edits to all directories again. (gstack)","https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Funfreeze\u002FSKILL.md",[],[128,133,102,21,134,135,105,136,137,138,92],"directories","remove","freeze","boundary","clear","SET",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":43},"01M6DK00ACSHDP8X0JE90FNQQJ","ubicloud","Run a heavy suite, build or eval on an ephemeral 16-vCPU Ubicloud VM: TTL-named VMs, a reaper, quota preflight and a hang watchdog. (gstack)","https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Fubicloud\u002FSKILL.md",[],[141,105,146,147,148,21,149,150,151,152,153,99,154,155,102,121,156,157],"vm","quota","eval","ttl","suite","vms","remote","preflight","watchdog","test run","build","test",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":43},"01M6DJZXTBG6SAZKY1RX8BJG55","beta","Clean fixture tool skill with no forced reads and no mode table.","https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fcontext-bill\u002Ftree-a\u002Fbeta\u002FSKILL.md",[],[160,165,166,167,27,168,169,170],"clean","mode","fixture tool","table","tool","fixture",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":43},"01M6DJZTJ0A0D31G2GH9FD3SE1","alpha","Fixture dispatcher with a mode table and forced-read references.","https:\u002F\u002Fgithub.com\u002Fgarrytan\u002Fgstack\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fcontext-bill\u002Ftree-a\u002Falpha\u002FSKILL.md",[],[173,166,27,168,178,102,179,180,170,181],"upstream","dispatcher","references","router"]