[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EZPAMV6W2K3TAPHJJY8MBW":3,"skill-same:01M6EZPAMV6W2K3TAPHJJY8MBW":92},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6EZPAMV6W2K3TAPHJJY8MBW","specstory-session-summary",null,"Summarize recent SpecStory AI coding sessions in standup format. Use when the user wants to review sessions from .specstory\u002Fhistory, prepare for standups, track work progress, or understand what was accomplished.","luokai0\u002Fai-agent-skills-by-luo-kai","luokai0","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266954973?v=4","01M6E16VNT42JB8B3X3254QWJ7","luo kai","01M6E16VTFVP6S5XJF1V1MPV90",14,"MIT","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Fintegrations\u002Fspecstory-session-summary\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"specstory session summary","session summary","summary","session","command","about","understand","progress","ai coding","use","user","review","work","history","coding","format","standup","prepare","sessions","summarize","2026-11-10 10:12:30",false,"---\nname: specstory-session-summary\ndescription: Summarize recent SpecStory AI coding sessions in standup format. Use when the user wants to review sessions from .specstory\u002Fhistory, prepare for standups, track work progress, or understand what was accomplished.\nlicense: MIT\nmetadata:\n  author: SpecStory\n  version: \"1.0\"\ngovernance_phases: [prove]\norgan_affinity: [organ-iv]\ntriggers: [command:session-summary, user-asks-about-sessions]\n---\n\n## Context\n\nYou will analyze recent SpecStory session history files to provide a standup-style summary.\n\nArgument provided: `$ARGUMENTS` (default: 5 sessions, or \"today\" for today's sessions only)\n\n## Your Task\n\n### Step 1: Find Recent Sessions\n\nFirst, check if the SpecStory history folder exists and list recent session files:\n\n```zsh\nls -t .specstory\u002Fhistory\u002F*.md 2>\u002Fdev\u002Fnull | head -20\n```\n\n**If no `.specstory\u002Fhistory` folder exists or it's empty**, respond with:\n\n> No SpecStory session history found in this directory.\n>\n> SpecStory automatically saves your AI coding sessions for later reference. To start recording your sessions, install SpecStory from https:\u002F\u002Fspecstory.com\n\nThen stop - do not proceed with the remaining steps.\n\n**If sessions are found**, continue with the analysis. If the argument is \"today\", filter to today's date. Otherwise use the number provided (default 5).\n\n### Step 2: Read and Analyze Each Session\n\nSession files can be very large and may contain multiple user requests. Use this chunked reading strategy:\n\n**Step 2a: Understand the session structure**\n\nFirst, grep for all user message markers to see the session's scope:\n```\ngrep -n \"_\\*\\*User\\*\\*_\" \u003Cfile> | head -10\n```\n\nThis shows line numbers of user messages, helping you understand:\n- How many distinct requests were made\n- Where to read for each request's context\n\n**Step 2b: Read strategically based on structure**\n\n1. **Beginning (first 500 lines)** - Read with `offset=0, limit=500`\n   - Captures the initial request even if it includes pasted code\u002Flogs\n   - May include early assistant responses showing the approach taken\n\n2. **End (last 300 lines)** - Use `tail -300 \u003Cfile>` via Bash\n   - Contains the final outcome and conclusion\n   - Shows whether tasks were completed or left pending\n\n3. **File operations** - Grep for modifications:\n   ```\n   grep -E \"(Edit|Write)\\(\" \u003Cfile>\n   ```\n\n**Step 2c: For multi-request sessions**\n\nIf the grep in 2a shows multiple user messages at distant line numbers (e.g., lines 50, 800, 1500), this indicates multiple distinct tasks. For these sessions:\n- Read around each user message line number (e.g., `offset=795, limit=100`)\n- Summarize the 2-3 main tasks rather than just the first one\n\n**Extract this information:**\n\n1. **Goal(s)**: The user's request(s) from `_**User**_` blocks\n   - For single-task sessions: one main goal\n   - For multi-task sessions: list the 2-3 primary tasks\n2. **Outcome**: Determine from the end of the conversation:\n   - ✅ Completed - task was finished successfully\n   - ? Research - information gathering, no code changes\n   - ? In Progress - work started but session ended mid-task\n   - ❌ Abandoned - user changed direction or gave up\n   - ? Blocked - ended with unresolved error or blocker\n3. **Files**: Modified files from Edit\u002FWrite tool uses (extract filenames only)\n4. **Key decisions**: Look in the conversation for:\n   - Explicit choices (\"decided to\", \"chose\", \"instead of\")\n   - Trade-off discussions\n   - Architecture or design conclusions\n\n### Step 3: Format Output\n\nPresent each session as:\n\n```\n### {YYYY-MM-DD HH:MM} - {Brief Title from Main Goal}\n**Goal**: {1 sentence summarizing what user wanted}\n**Outcome**: {emoji} {Brief result description}\n**Files**: {comma-separated list, or \"None\" if research only}\n**Key insight**: {Notable decision or learning, if any}\n```\n\nFor multi-task sessions, adjust the format:\n\n```\n### {YYYY-MM-DD HH:MM} - {Overall Theme or Primary Task}\n**Tasks**:\n  1. {First task} - {outcome emoji}\n  2. {Second task} - {outcome emoji}\n**Files**: {comma-separated list}\n**Key insight**: {Notable decision or learning, if any}\n```\n\n### Step 4: Summary Section\n\nAfter all sessions, add:\n\n```\n---\n**Patterns**: {Note any recurring themes, files touched multiple times, ongoing work}\n**Unfinished**: {Any sessions that ended with TODOs, blockers, or incomplete work}\n```\n\n## Guidelines\n\n- Keep each session summary to 5-6 lines maximum (slightly more for multi-task sessions)\n- Infer the title from the user's goal, not the filename\n- For files, prefer showing just the filename, not full paths\n- Skip sessions that are just quick questions with no real work\n- For multi-task sessions, summarize up to 3 main tasks; group minor tasks as \"various small fixes\"\n- Be concise - this is for quick daily review, not detailed documentation\n- If a file read fails or is too large, work with what you can extract; don't skip the session entirely\n\n## Example Output\n\n```\n## Session Summary (Last 3 Sessions)\n\n### 2025-10-18 11:42 - Investigate Chat CRDT Storage\n**Goal**: Understand why chat index CRDT doesn't contain the thread\n**Outcome**: ? Explained dual storage design for offline\u002Fonline sync\n**Files**: threads.json, crdt-debug\u002F4X\u002F, crdt-debug\u002FaT\u002F\n**Key insight**: Two storage layers (CRDT + JSON) serve different sync scenarios\n\n### 2025-10-18 11:09 - Address Code Review Comments\n**Goal**: Fix clarity issues from code review\n**Outcome**: ✅ Refactored normalizeChatIndexDoc function\n**Files**: chat.go, automerge-bridge.js\n**Key insight**: Replaced complex normalization with toPlainString helper\n\n### 2025-10-11 14:30 - Automerge Architecture Deep Dive\n**Goal**: Document how Automerge docs are constructed temporally\n**Outcome**: ? Research complete, walkthrough provided\n**Files**: automerge-bridge.js, document.go (read only)\n\n---\n**Patterns**: 3 sessions focused on CRDT\u002Fchat subsystem; automerge-bridge.js touched repeatedly\n**Unfinished**: None detected\n```\n","## Context\n\nYou will analyze recent SpecStory session history files to provide a standup-style summary.\n\nArgument provided: `$ARGUMENTS` (default: 5 sessions, or \"today\" for today's sessions only)\n\n## Your Task\n\n### Step 1: Find Recent Sessions\n\nFirst, check if the SpecStory history folder exists and list recent session files:\n\n```zsh\nls -t .specstory\u002Fhistory\u002F*.md 2>\u002Fdev\u002Fnull | head -20\n```\n\n**If no `.specstory\u002Fhistory` folder exists or it's empty**, respond with:\n\n> No SpecStory session history found in this directory.\n>\n> SpecStory automatically saves your AI coding sessions for later reference. To start recording your sessions, install SpecStory from https:\u002F\u002Fspecstory.com\n\nThen stop - do not proceed with the remaining steps.\n\n**If sessions are found**, continue with the analysis. If the argument is \"today\", filter to today's date. Otherwise use the number provided (default 5).\n\n### Step 2: Read and Analyze Each Session\n\nSession files can be very large and may contain multiple user requests. Use this chunked reading strategy:\n\n**Step 2a: Understand the session structure**\n\nFirst, grep for all user message markers to see the session's scope:\n```\ngrep -n \"_\\*\\*User\\*\\*_\" \u003Cfile> | head -10\n```\n\nThis shows line numbers of user messages, helping you understand:\n- How many distinct requests were made\n- Where to read for each request's context\n\n**Step 2b: Read strategically based on structure**\n\n1. **Beginning (first 500 lines)** - Read with `offset=0, limit=500`\n   - Captures the initial request even if it includes pasted code\u002Flogs\n   - May include early assistant responses showing the approach taken\n\n2. **End (last 300 lines)** - Use `tail -300 \u003Cfile>` via Bash\n   - Contains the final outcome and conclusion\n   - Shows whether tasks were completed or left pending\n\n3. **File operations** - Grep for modifications:\n   ```\n   grep -E \"(Edit|Write)\\(\" \u003Cfile>\n   ```\n\n**Step 2c: For multi-request sessions**\n\nIf the grep in 2a shows multiple user messages at distant line numbers (e.g., lines 50, 800, 1500), this indicates multiple distinct tasks. For these sessions:\n- Read around each user message line number (e.g., `offset=795, limit=100`)\n- Summarize the 2-3 main tasks rather than just the first one\n\n**Extract this information:**\n\n1. **Goal(s)**: The user's request(s) from `_**User**_` blocks\n   - For single-task sessions: one main goal\n   - For multi-task sessions: list the 2-3 primary tasks\n2. **Outcome**: Determine from the end of the conversation:\n   - ✅ Completed - task was finished successfully\n   - ? Research - information gathering, no code changes\n   - ? In Progress - work started but session ended mid-task\n   - ❌ Abandoned - user changed direction or gave up\n   - ? Blocked - ended with unresolved error or blocker\n3. **Files**: Modified files from Edit\u002FWrite tool uses (extract filenames only)\n4. **Key decisions**: Look in the conversation for:\n   - Explicit choices (\"decided to\", \"chose\", \"instead of\")\n   - Trade-off discussions\n   - Architecture or design conclusions\n\n### Step 3: Format Output\n\nPresent each session as:\n\n```\n### {YYYY-MM-DD HH:MM} - {Brief Title from Main Goal}\n**Goal**: {1 sentence summarizing what user wanted}\n**Outcome**: {emoji} {Brief result description}\n**Files**: {comma-separated list, or \"None\" if research only}\n**Key insight**: {Notable decision or learning, if any}\n```\n\nFor multi-task sessions, adjust the format:\n\n```\n### {YYYY-MM-DD HH:MM} - {Overall Theme or Primary Task}\n**Tasks**:\n  1. {First task} - {outcome emoji}\n  2. {Second task} - {outcome emoji}\n**Files**: {comma-separated list}\n**Key insight**: {Notable decision or learning, if any}\n```\n\n### Step 4: Summary Section\n\nAfter all sessions, add:\n\n```\n---\n**Patterns**: {Note any recurring themes, files touched multiple times, ongoing work}\n**Unfinished**: {Any sessions that ended with TODOs, blockers, or incomplete work}\n```\n\n## Guidelines\n\n- Keep each session summary to 5-6 lines maximum (slightly more for multi-task sessions)\n- Infer the title from the user's goal, not the filename\n- For files, prefer showing just the filename, not full paths\n- Skip sessions that are just quick questions with no real work\n- For multi-task sessions, summarize up to 3 main tasks; group minor tasks as \"various small fixes\"\n- Be concise - this is for quick daily review, not detailed documentation\n- If a file read fails or is too large, work with what you can extract; don't skip the session entirely\n\n## Example Output\n\n```\n## Session Summary (Last 3 Sessions)\n\n### 2025-10-18 11:42 - Investigate Chat CRDT Storage\n**Goal**: Understand why chat index CRDT doesn't contain the thread\n**Outcome**: ? Explained dual storage design for offline\u002Fonline sync\n**Files**: threads.json, crdt-debug\u002F4X\u002F, crdt-debug\u002FaT\u002F\n**Key insight**: Two storage layers (CRDT + JSON) serve different sync scenarios\n\n### 2025-10-18 11:09 - Address Code Review Comments\n**Goal**: Fix clarity issues from code review\n**Outcome**: ✅ Refactored normalizeChatIndexDoc function\n**Files**: chat.go, automerge-bridge.js\n**Key insight**: Replaced complex normalization with toPlainString helper\n\n### 2025-10-11 14:30 - Automerge Architecture Deep Dive\n**Goal**: Document how Automerge docs are constructed temporally\n**Outcome**: ? Research complete, walkthrough provided\n**Files**: automerge-bridge.js, document.go (read only)\n\n---\n**Patterns**: 3 sessions focused on CRDT\u002Fchat subsystem; automerge-bridge.js touched repeatedly\n**Unfinished**: None detected\n```\n",{"name":5,"license":15,"metadata":44,"triggers":47,"description":7,"organ_affinity":50,"governance_phases":52},{"author":45,"version":46},"SpecStory","1.0",[48,49],"command:session-summary","user-asks-about-sessions",[51],"organ-iv",[53],"prove","main","4d2fb89cdfb75f3f6fd3c6c5ec9ad90ea129eb3c","ai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Fintegrations\u002Fspecstory-session-summary",1,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai","https:\u002F\u002Fgithub.com\u002Fluokai0","a solo builder.","2026-05-06 04:29:04",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill specstory-session-summary",{"tool":68,"command":69},"bunx","bunx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill specstory-session-summary",{"tool":71,"command":72},"pnpm","pnpm dlx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill specstory-session-summary","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Fintegrations\u002Fspecstory-session-summary\u002FSKILL.md",true,[76,82,88],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"LICENSE.txt","LICENSE","许可证",11356,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Fintegrations\u002Fspecstory-session-summary\u002FLICENSE.txt",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fsession-parsing.md","REFERENCE","参考文档",10009,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Fintegrations\u002Fspecstory-session-summary\u002Freferences\u002Fsession-parsing.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fstandup-formats.md",7162,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Fintegrations\u002Fspecstory-session-summary\u002Freferences\u002Fstandup-formats.md",[93,120,137,167,199,236],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":39},"01M6F2SKTE208174C7S7JJCZC7","write-contracts","Generates secure Aptos Move V2 smart contracts with Object model, Digital Asset integration, security patterns, and storage type guidance. Includes comprehensive storage decision framework for optimal data structure selection. Triggers on: 'write contract', 'create NFT collection', 'build marketplace', 'implement minting', 'generate Move module', 'create token contract', 'build DAO', 'implement staking'. Ask storage questions when: 'store', 'track', 'registry', 'mapping', 'list', 'collection'.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fwrite-contracts\u002FSKILL.md",[],[100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119],"write","contracts","write contracts","storage","secure","create","generate","collection","model","decision","ask","smart-contracts","selection","objects","structure","nft","token","aptos","critical","move",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":39},"01M6F2RFXJ6T9MKW0A7N7GM45B","web-search","通用网络搜索技能，支持多引擎搜索（百度、必应、DuckDuckGo），无需API密钥即可获取实时信息","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fweb-search-ex-skill\u002FSKILL.md",[],[127,128,129,130,131,132,133,134,135,136],"web","search","web search","搜索","baidu","bing","duckduckgo","百度","多引擎","internet",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":148,"publishedAt":39},"01M6F2K968G1FZEZFPW2E6B222","solo-build","Execute implementation plan tasks with TDD workflow, auto-commit, and phase gates. Use when user says \"build it\", \"start building\", \"execute plan\", \"implement tasks\", \"ship it\", or references a track ID. Do NOT use for planning (use \u002Fplan) or scaffolding (use \u002Fscaffold).","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fsolo-build\u002FSKILL.md",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[149,150,151,152,153,154,155,156,128,157,158,159,100,160,161,162,163,164,165,166],"build","solo","solo build","MCP","workflow","commit","tasks","code","Bash","plan","read","auto","references","context7","query","scaffolding","ship it","project",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":179,"publishedAt":39},"01M6F2GKN39SGHSPWYB3662YC8","react-email","Use when building HTML email templates with React components, adding a visual email editor to an application using the React Email visual editor, rendering emails to HTML, or sending emails with Resend. Covers welcome emails, password resets, notifications, order confirmations, newsletters, transactional emails, and the embeddable email editor component.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Freact-email-skills\u002FSKILL.md",[173,176],{"categoryNo":174,"categoryName":175,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":177,"categoryName":178,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000009","前端开发",[180,181,182,183,184,185,186,187,188,189,190,191,192,28,193,194,195,196,197,198],"react","email","react email","github","editor","components","react components","component","welcome","https","notifications","password","node","html","resend","visual","emails","rendering","with",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":217,"publishedAt":39},"01M6F2FBVGVDFSG8SSFJGXA40C","APITester Agent-Driven API Testing","Test API endpoints and document responses. Define tests in plain English, run them, get formatted results. Agent-driven Postman alternative.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fopenclaw-api-tester\u002FSKILL.md",[205,208,211,212],{"categoryNo":206,"categoryName":207,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":209,"categoryName":210,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},{"categoryNo":213,"categoryName":214,"taxonomyType":215,"taxonomyTypeDesc":216},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234,235],"testing","api","api testing","driven","APITester Agent Driven API Testing","test","run","postman","results","plain english","tester","endpoints","document","get","define","tests","english","api-tester",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":242,"publishedAt":39},"01M6F273Y3NGAPVJZ608BC0G9G","hubspot-implementation-plan","Generate a phased implementation plan from a HubSpot audit report. Creates prioritized, sequenced cleanup processes with effort estimates, dependencies, and automation feasibility. Use after running \u002Fhubspot-audit.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fhubspot-implementation-plan\u002FSKILL.md",[],[158,243,244,245,246,247,248,106,249,250,251,252,253,28,254,255,198,256],"implementation","hubspot","hubspot implementation plan","automation","feasibility","cleanup","planning","report","audit","audit report","phased implementation","dependencies","processes","hubspot audit"]