[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6VC6P68MDPVC7KPQEHM4BNP":3,"skill-same:01M6VC6P68MDPVC7KPQEHM4BNP":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":66},"01M6VC6P68MDPVC7KPQEHM4BNP","springboot-verification",null,"Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.","sakamoto-family-smile\u002Fagent_monorepo","sakamoto-family-smile","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F132812403?v=4","01M6RTAT3H8PMWX5SJ65KP3VYF","01M6RTAV321WB5RAHCWTZMX5CV",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fspringboot-verification\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"verification","springboot verification","projects","static","for","with","diff review","tests","build","diff","coverage","spring","review","verification loop","loop","analysis","spring boot","release","boot","pr","2026-11-10 10:12:30",false,"---\nname: hp-plan\ndescription: \"Interactively define pages and sections for a homepage project, then generate page plans.\"\nargument-hint: \"[page-name]\"\nuser-invocable: true\nallowed-tools: Read, Write, Edit, Glob, Grep, Bash, Agent\n---\n\n# Page Planning Skill (Interactive Definition)\n\nInteractively gathers page and section definitions from the user, then launches the page-planner agent to produce structured plans.\n\nPages and sections are NOT predefined — this skill collects definitions through conversation.\n\n## Instructions\n\n### Step 0: Read Configuration\n\nRead `.claude\u002Fhomepage-plugin.json`. If not found, instruct the user to run `\u002Fhomepage-plugin:hp-init` first and exit.\n\nRead `defaultLocale` — all user-facing output must be in this language.\n\n### Step 1: Check Existing Plans\n\nScan `docs\u002Fpages\u002F*\u002Fpage-plan.json` for existing page plans. If plans exist, show the current page list and ask if the user wants to:\n- **Add a new page** — continue to Step 2 with the new page only\n- **Replace all** — clear existing plans and start fresh\n- **Edit a specific page** — re-plan one page\n\nIf the user provides a `[page-name]` argument, plan only that page (skip to Step 4 for that page).\n\n### Step 2: Site Purpose\n\nAsk: \"What kind of site is this?\"\n\nSuggestions:\n- Company homepage\n- Product\u002Fservice landing page\n- Portfolio\u002Fshowcase\n- Corporate\u002Fenterprise site\n- Startup landing page\n\nThe answer influences default page suggestions in Step 3.\n\n### Step 3: Page Definition\n\nAsk: \"What pages do you need?\"\n\nSuggest defaults based on site purpose:\n- **Company homepage**: Home, About, Services, Contact, Blog\n- **Product landing**: Home, Features, Pricing, FAQ, Contact\n- **Portfolio**: Home, Work, About, Contact\n- **Corporate**: Home, About, Services, Team, Careers, Contact, Blog\n\nThe user can add, remove, or rename pages. Confirm the final page list.\n\n### Step 4: Per-Page Section Definition\n\nFor each page, ask: \"What content should this page show?\"\n\nThe user describes content in natural language. Examples:\n- \"메인 슬로건과 CTA 버튼, 핵심 서비스 3개, 고객 후기, 상담 신청 유도\"\n- \"Hero with company vision, timeline of our history, team member cards, partner logos\"\n\nMatch descriptions to the section catalog (15 canonical types from `templates\u002Fsection-catalog.md`):\n\n| User Description | Matched Section |\n|---|---|\n| 메인 슬로건, hero, banner | HeroSection |\n| 서비스 소개, features, 핵심 기능 | FeaturesSection |\n| 고객 후기, testimonials, 리뷰 | TestimonialsSection |\n| CTA, 상담 신청, 문의 유도 | CTASection |\n| 가격, pricing, 요금제 | PricingSection |\n| FAQ, 자주 묻는 질문 | FAQSection |\n| 실적, 수치, stats | StatsSection |\n| 파트너, 로고, clients | LogoCloudSection |\n| 뉴스레터, 구독 | NewsletterSection |\n| 문의 폼, contact form | ContactSection |\n| 팀 소개, team | TeamSection |\n| 연혁, timeline, history | TimelineSection |\n| 갤러리, gallery, 포트폴리오 | GallerySection |\n\nPropose the matched sections with order. The user can:\n- Confirm the composition\n- Reorder sections\n- Add custom sections (describe what they need)\n- Remove sections\n\nDisplay the proposed composition:\n```\n┌─ Home Page ──────────────────────────────────┐\n│  1. HeroSection      — Main slogan + CTA     │\n│  2. FeaturesSection   — 3 core services       │\n│  3. StatsSection      — Performance metrics   │\n│  4. TestimonialsSection — Customer reviews     │\n│  5. CTASection        — Consultation CTA      │\n└──────────────────────────────────────────────┘\n```\n\n### Step 5: Shared Layout Definition\n\n#### 5.1 Check for Figma-Extracted Layout\n\nRead `docs\u002Fpages\u002F_shared\u002Flayout-plan.json` if it exists.\n\nIf the file exists and contains `_figmaSource.populated === true`, the layout was pre-populated from Figma by `hp-design-sync`. Display the pre-populated layout to the user:\n\n```\nLayout pre-populated from Figma design:\n\nHeader:\n  Logo: [extracted from Figma] ✓\n  Nav items: Home, About, Services, Contact\n  CTA: \"Get Started\"\n\nFooter:\n  Description: \"Company tagline\"\n  Link groups: Product (4 links), Company (3 links)\n  Social: Twitter, LinkedIn, GitHub\n  Copyright: 2026\n```\n\nAsk the user to choose:\n1. **Use as-is** — keep the Figma-extracted layout without changes\n2. **Modify** — edit specific parts (nav items, links, social media URLs, etc.) while keeping the overall structure\n3. **Start fresh** — discard the Figma-extracted layout and define from scratch\n\n- If **Use as-is**: skip to Step 6 (no further layout questions)\n- If **Modify**: present each section (header, footer) for editing. Pre-fill all fields with the Figma-extracted values. The user can:\n  - Change nav item labels and add real href values (Figma-extracted hrefs are placeholders)\n  - Add or remove nav items\n  - Edit footer link groups, add\u002Fremove links\n  - Add real social media URLs (Figma-extracted are `\"#\"` placeholders)\n  - Change company name and description\n  - Write the modified layout plan back to `docs\u002Fpages\u002F_shared\u002Flayout-plan.json`, preserving `_figmaSource` metadata\n- If **Start fresh**: proceed to Step 5.2\n\n#### 5.2 Manual Layout Definition\n\nIf no Figma-extracted layout exists, or the user chose \"Start fresh\":\n\nAsk: \"How should the header and footer be structured?\"\n\nGather:\n- **Header**: logo, navigation menu items, optional CTA button, mobile nav toggle\n- **Footer**: column structure, links, social media icons, copyright text\n\nWrite the layout plan to `docs\u002Fpages\u002F_shared\u002Flayout-plan.json`.\n\n### Step 6: Figma Reference (Optional)\n\nAsk: \"Do you have a Figma design for reference? (screenshot path or URL — optional)\"\n\n- If provided as a file path: the page-planner agent will analyze the image\n- If provided as a URL: note for reference (no auto-fetch)\n- If skipped: proceed with description-based planning\n\n### Step 7: Launch Page Planner\n\nFor each page defined, launch the `page-planner` agent with:\n- `pageName` — page identifier\n- `pageDescription` — user's description\n- `sections` — matched section list with descriptions\n- `figmaRef` — Figma reference (if provided)\n- `layoutPlan` — path to layout plan\n- `projectRoot` — project root\n- `outputFile` — `docs\u002Fpages\u002F{page-name}\u002Fpage-plan.json`\n- `config` — homepage-plugin configuration\n\nCreate progress file at `docs\u002Fpages\u002F{page-name}\u002F.progress\u002F{page-name}.json`:\n```json\n{\n  \"page\": \"{page-name}\",\n  \"implementation\": {\n    \"status\": \"planned\",\n    \"plannedAt\": \"{ISO timestamp}\"\n  }\n}\n```\n\n### Step 8: Display Summary\n\nShow:\n- Total pages planned\n- Sections per page\n- Shared sections (reused across pages)\n- Interactive islands identified\n- Next step: \"Run `\u002Fhomepage-plugin:hp-gen` to generate code.\"\n\nIf planning a single page: \"Run `\u002Fhomepage-plugin:hp-gen {page-name}` to generate this page.\"\n\n## Communication Language\n\nRead `defaultLocale` from `.claude\u002Fhomepage-plugin.json`:\n- `ko` → All questions, suggestions, and summaries in Korean\n- `en` → All in English\n- `vi` → All in Vietnamese\n","# Page Planning Skill (Interactive Definition)\n\nInteractively gathers page and section definitions from the user, then launches the page-planner agent to produce structured plans.\n\nPages and sections are NOT predefined — this skill collects definitions through conversation.\n\n## Instructions\n\n### Step 0: Read Configuration\n\nRead `.claude\u002Fhomepage-plugin.json`. If not found, instruct the user to run `\u002Fhomepage-plugin:hp-init` first and exit.\n\nRead `defaultLocale` — all user-facing output must be in this language.\n\n### Step 1: Check Existing Plans\n\nScan `docs\u002Fpages\u002F*\u002Fpage-plan.json` for existing page plans. If plans exist, show the current page list and ask if the user wants to:\n- **Add a new page** — continue to Step 2 with the new page only\n- **Replace all** — clear existing plans and start fresh\n- **Edit a specific page** — re-plan one page\n\nIf the user provides a `[page-name]` argument, plan only that page (skip to Step 4 for that page).\n\n### Step 2: Site Purpose\n\nAsk: \"What kind of site is this?\"\n\nSuggestions:\n- Company homepage\n- Product\u002Fservice landing page\n- Portfolio\u002Fshowcase\n- Corporate\u002Fenterprise site\n- Startup landing page\n\nThe answer influences default page suggestions in Step 3.\n\n### Step 3: Page Definition\n\nAsk: \"What pages do you need?\"\n\nSuggest defaults based on site purpose:\n- **Company homepage**: Home, About, Services, Contact, Blog\n- **Product landing**: Home, Features, Pricing, FAQ, Contact\n- **Portfolio**: Home, Work, About, Contact\n- **Corporate**: Home, About, Services, Team, Careers, Contact, Blog\n\nThe user can add, remove, or rename pages. Confirm the final page list.\n\n### Step 4: Per-Page Section Definition\n\nFor each page, ask: \"What content should this page show?\"\n\nThe user describes content in natural language. Examples:\n- \"메인 슬로건과 CTA 버튼, 핵심 서비스 3개, 고객 후기, 상담 신청 유도\"\n- \"Hero with company vision, timeline of our history, team member cards, partner logos\"\n\nMatch descriptions to the section catalog (15 canonical types from `templates\u002Fsection-catalog.md`):\n\n| User Description | Matched Section |\n|---|---|\n| 메인 슬로건, hero, banner | HeroSection |\n| 서비스 소개, features, 핵심 기능 | FeaturesSection |\n| 고객 후기, testimonials, 리뷰 | TestimonialsSection |\n| CTA, 상담 신청, 문의 유도 | CTASection |\n| 가격, pricing, 요금제 | PricingSection |\n| FAQ, 자주 묻는 질문 | FAQSection |\n| 실적, 수치, stats | StatsSection |\n| 파트너, 로고, clients | LogoCloudSection |\n| 뉴스레터, 구독 | NewsletterSection |\n| 문의 폼, contact form | ContactSection |\n| 팀 소개, team | TeamSection |\n| 연혁, timeline, history | TimelineSection |\n| 갤러리, gallery, 포트폴리오 | GallerySection |\n\nPropose the matched sections with order. The user can:\n- Confirm the composition\n- Reorder sections\n- Add custom sections (describe what they need)\n- Remove sections\n\nDisplay the proposed composition:\n```\n┌─ Home Page ──────────────────────────────────┐\n│  1. HeroSection      — Main slogan + CTA     │\n│  2. FeaturesSection   — 3 core services       │\n│  3. StatsSection      — Performance metrics   │\n│  4. TestimonialsSection — Customer reviews     │\n│  5. CTASection        — Consultation CTA      │\n└──────────────────────────────────────────────┘\n```\n\n### Step 5: Shared Layout Definition\n\n#### 5.1 Check for Figma-Extracted Layout\n\nRead `docs\u002Fpages\u002F_shared\u002Flayout-plan.json` if it exists.\n\nIf the file exists and contains `_figmaSource.populated === true`, the layout was pre-populated from Figma by `hp-design-sync`. Display the pre-populated layout to the user:\n\n```\nLayout pre-populated from Figma design:\n\nHeader:\n  Logo: [extracted from Figma] ✓\n  Nav items: Home, About, Services, Contact\n  CTA: \"Get Started\"\n\nFooter:\n  Description: \"Company tagline\"\n  Link groups: Product (4 links), Company (3 links)\n  Social: Twitter, LinkedIn, GitHub\n  Copyright: 2026\n```\n\nAsk the user to choose:\n1. **Use as-is** — keep the Figma-extracted layout without changes\n2. **Modify** — edit specific parts (nav items, links, social media URLs, etc.) while keeping the overall structure\n3. **Start fresh** — discard the Figma-extracted layout and define from scratch\n\n- If **Use as-is**: skip to Step 6 (no further layout questions)\n- If **Modify**: present each section (header, footer) for editing. Pre-fill all fields with the Figma-extracted values. The user can:\n  - Change nav item labels and add real href values (Figma-extracted hrefs are placeholders)\n  - Add or remove nav items\n  - Edit footer link groups, add\u002Fremove links\n  - Add real social media URLs (Figma-extracted are `\"#\"` placeholders)\n  - Change company name and description\n  - Write the modified layout plan back to `docs\u002Fpages\u002F_shared\u002Flayout-plan.json`, preserving `_figmaSource` metadata\n- If **Start fresh**: proceed to Step 5.2\n\n#### 5.2 Manual Layout Definition\n\nIf no Figma-extracted layout exists, or the user chose \"Start fresh\":\n\nAsk: \"How should the header and footer be structured?\"\n\nGather:\n- **Header**: logo, navigation menu items, optional CTA button, mobile nav toggle\n- **Footer**: column structure, links, social media icons, copyright text\n\nWrite the layout plan to `docs\u002Fpages\u002F_shared\u002Flayout-plan.json`.\n\n### Step 6: Figma Reference (Optional)\n\nAsk: \"Do you have a Figma design for reference? (screenshot path or URL — optional)\"\n\n- If provided as a file path: the page-planner agent will analyze the image\n- If provided as a URL: note for reference (no auto-fetch)\n- If skipped: proceed with description-based planning\n\n### Step 7: Launch Page Planner\n\nFor each page defined, launch the `page-planner` agent with:\n- `pageName` — page identifier\n- `pageDescription` — user's description\n- `sections` — matched section list with descriptions\n- `figmaRef` — Figma reference (if provided)\n- `layoutPlan` — path to layout plan\n- `projectRoot` — project root\n- `outputFile` — `docs\u002Fpages\u002F{page-name}\u002Fpage-plan.json`\n- `config` — homepage-plugin configuration\n\nCreate progress file at `docs\u002Fpages\u002F{page-name}\u002F.progress\u002F{page-name}.json`:\n```json\n{\n  \"page\": \"{page-name}\",\n  \"implementation\": {\n    \"status\": \"planned\",\n    \"plannedAt\": \"{ISO timestamp}\"\n  }\n}\n```\n\n### Step 8: Display Summary\n\nShow:\n- Total pages planned\n- Sections per page\n- Shared sections (reused across pages)\n- Interactive islands identified\n- Next step: \"Run `\u002Fhomepage-plugin:hp-gen` to generate code.\"\n\nIf planning a single page: \"Run `\u002Fhomepage-plugin:hp-gen {page-name}` to generate this page.\"\n\n## Communication Language\n\nRead `defaultLocale` from `.claude\u002Fhomepage-plugin.json`:\n- `ko` → All questions, suggestions, and summaries in Korean\n- `en` → All in English\n- `vi` → All in Vietnamese\n",{"name":43,"description":44,"allowed-tools":45,"argument-hint":46,"user-invocable":47},"hp-plan","Interactively define pages and sections for a homepage project, then generate page plans.","Read, Write, Edit, Glob, Grep, Bash, Agent","[page-name]",true,"main","99f07e592261c66756a2927d0440fc5fef950507",".claude\u002Fskills\u002Fecc\u002Fspringboot-verification","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile","2026-11-08 20:29:14",{"source":8,"skillName":43,"commands":55,"prompt":65,"zipAvailable":47},[56,59,62],{"tool":57,"command":58},"npx","npx skills add sakamoto-family-smile\u002Fagent_monorepo --skill hp-plan",{"tool":60,"command":61},"bunx","bunx skills add sakamoto-family-smile\u002Fagent_monorepo --skill hp-plan",{"tool":63,"command":64},"pnpm","pnpm dlx skills add sakamoto-family-smile\u002Fagent_monorepo --skill hp-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fspringboot-verification\u002FSKILL.md",[],[68,102,110,129,152,180],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":82,"publishedAt":38},"01M6RW50THEFSKK42YNR8XFZA1","remotion-video-creation","Best practices for Remotion - Video creation in React. 29 domain-specific rules covering 3D, animations, audio, captions, charts, transitions, and more.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fremotion-video-creation\u002FSKILL.md",[74,79],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":80,"categoryName":81,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000016","图像与多媒体",[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,22],"Video","remotion video","remotion video creation","creation","Remotion","Charts","Captions","Audio","3D","Composition","Animation","best practices","more","animations","domain-specific","domain","three","Rules","Lottie",{"skillNo":103,"name":104,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":38},"01M6VCJ23NPECPSZJKGY691F75","hotcook-recipes","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fhotcook-agent\u002Fdata\u002Fskills\u002Fhotcook-recipes\u002FSKILL.md",[],[108,109],"hotcook recipes","recipes",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":124,"publishedAt":38},"01M6VCHHE00X5XHSDRD1KH1BW2","code-helper","Code review and assistance skill","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-2\u002Fskills\u002Fcode-helper\u002Fskill.md",[116,119],{"categoryNo":117,"categoryName":118,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[125,126,127,128,30],"code helper","helper","code","code review",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":141,"publishedAt":38},"01M6VCH3Q31A20H6SQ1H0J7JB2","research-assistant","Web research assistant skill using Brave Search MCP","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fagent-system-1\u002Fskills\u002Fresearch-assistant\u002Fskill.md",[135,138],{"categoryNo":136,"categoryName":137,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":139,"categoryName":140,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发",[142,143,144,145,146,147,148,149,150,151],"research assistant","research","assistant","MCP","web","search","brave search","web research","brave","web research assistant",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":162,"publishedAt":38},"01M6VCGZZGPNVJSCZ1JTMNZAHY","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fx-api\u002FSKILL.md",[158,161],{"categoryNo":159,"categoryName":160,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},[163,164,23,165,166,167,22,168,169,170,171,172,173,174,175,176,177,178,147,179],"x api","api","when","limits","rate","threads","reading","native","posting","platform","patterns","api integration","twitter","use","auth","analytics","OAuth",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":187,"publishedAt":38},"01M6VCGVX6DGB1FKTA53QBBCQB","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Fworkspace-surface-audit\u002FSKILL.md",[186],{"categoryNo":139,"categoryName":140,"taxonomyType":77,"taxonomyTypeDesc":78},[188,189,190,191,145,192,193,127,194,195,196,197,176,198,199,200,201,170,202,165],"workspace surface audit","workspace","audit","hooks","workflows","connectors","capabilities","harness","repo","environment","up","harness setup","active","env","value"]