[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RTHGY75KXAXHWJ7BR8RX31":3,"skill-same:01M6RTHGY75KXAXHWJ7BR8RX31":75},{"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":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":13,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6RTHGY75KXAXHWJ7BR8RX31","article-writing",null,"Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.","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\u002Farticle-writing\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"article writing","writing","article","structure","when","credibility","long-form","consistency","posts","form","guides","long","newsletter","guidance","use","write","brand","blog","examples","issues","2026-11-10 10:12:30",false,"---\nname: experiment-design-kit\ndescription: Toolkit for structuring hypotheses, variants, guardrails, and measurement\n  plans.\n---\n\n# Experiment Design Kit Skill\n\n## When to Use\n- Translating raw ideas into testable hypotheses with clear success metrics.\n- Ensuring experiment briefs include guardrails, instrumentation, and rollout details.\n- Coaching pods on best practices for multi-variant or multi-surface tests.\n\n## Framework\n1. **Problem Framing** – define user problem, business impact, and north-star metric.\n2. **Hypothesis Structure** – \"If we do X for Y persona, we expect Z change\" with assumptions.\n3. **Measurement Plan** – primary metric, guardrails, min detectable effect, power calc.\n4. **Variant Strategy** – control definition, variant catalog, targeting, and exclusion rules.\n5. **Operational Plan** – owners, timeline, dependencies, QA\u002Frollback steps.\n\n## Templates\n- Experiment brief (context, hypothesis, design, metrics, launch checklist).\n- Guardrail register with thresholds + alerting rules.\n- Variant matrix for surfaces, messaging, and states.\n- **GTM Agents Growth Backlog Board** – capture idea → sizing → prioritization scoring (ICE\u002FRICE) @puerto\u002FREADME.md#183-212.\n- **Weekly Experiment Packet** – includes KPI guardrails, qualitative notes, and next bets for Marketing Director + Sales Director.\n- **Rollback Playbook** – pre-built checklist tied to lifecycle-mapping rip-cord procedures.\n\n## Tips\n- Pressure-test hypotheses with counter-metrics to avoid local optima.\n- Document data constraints early to avoid rework during build.\n- Pair with `guardrail-scorecard` to ensure sign-off before launch.\n- Apply GTM Agents cadence: Monday backlog groom, Wednesday build review, Friday learnings sync.\n- Require KPI guardrails per stage (activation, engagement, monetization) before authorizing build.\n- If a test risks Sales velocity, include Sales Director in approval routing per GTM Agents governance.\n\n## GTM Agents Experiment Operating Model\n1. **Backlog Intake** – ideas flow from GTM pods; Growth Marketer tags theme, objective, expected impact.\n2. **Prioritization** – score with RICE + qualitative \"strategic fit\" modifier; surface top 3 bets weekly.\n3. **Design & Instrumentation** – reference Serena\u002FContext7 to patch code + confirm documentation.\n4. **Launch & Monitor** – use guardrail-scorecard to watch leading indicators (churn, complaints, latency).\n5. **Learning Loop** – run Sequential Thinking retro; document hypothesis, result, decision, follow-up in backlog card.\n\n## KPI Guardrails (GTM Agents Reference)\n- Activation rate change must stay within ±3% of baseline for Tier-1 segments.\n- Revenue per visitor cannot drop more than 2% for more than 48h.\n- Support tickets tied to experiment variant must remain \u003C5% of total volume.\n\n## Weekly Experiment Packet Outline\n```\nWeek Ending: \u003CDate>\n\n1. Portfolio Snapshot – tests live, status, KPI trend (guardrail vs actual)\n2. Key Wins – hypothesis, uplift, next action (ship, iterate, expand)\n3. Guardrail Alerts – what tripped, mitigation taken (rollback? scope adjust?)\n4. Pipeline Impact – SQLs, ARR influenced, notable customer anecdotes\n5. Upcoming Launches – dependencies, owners, open questions\n```\n\nShare packet with Growth, Marketing Director, Sales Director, and RevOps to mirror GTM Agents's cross-functional communication rhythm.\n\n---\n","# Experiment Design Kit Skill\n\n## When to Use\n- Translating raw ideas into testable hypotheses with clear success metrics.\n- Ensuring experiment briefs include guardrails, instrumentation, and rollout details.\n- Coaching pods on best practices for multi-variant or multi-surface tests.\n\n## Framework\n1. **Problem Framing** – define user problem, business impact, and north-star metric.\n2. **Hypothesis Structure** – \"If we do X for Y persona, we expect Z change\" with assumptions.\n3. **Measurement Plan** – primary metric, guardrails, min detectable effect, power calc.\n4. **Variant Strategy** – control definition, variant catalog, targeting, and exclusion rules.\n5. **Operational Plan** – owners, timeline, dependencies, QA\u002Frollback steps.\n\n## Templates\n- Experiment brief (context, hypothesis, design, metrics, launch checklist).\n- Guardrail register with thresholds + alerting rules.\n- Variant matrix for surfaces, messaging, and states.\n- **GTM Agents Growth Backlog Board** – capture idea → sizing → prioritization scoring (ICE\u002FRICE) @puerto\u002FREADME.md#183-212.\n- **Weekly Experiment Packet** – includes KPI guardrails, qualitative notes, and next bets for Marketing Director + Sales Director.\n- **Rollback Playbook** – pre-built checklist tied to lifecycle-mapping rip-cord procedures.\n\n## Tips\n- Pressure-test hypotheses with counter-metrics to avoid local optima.\n- Document data constraints early to avoid rework during build.\n- Pair with `guardrail-scorecard` to ensure sign-off before launch.\n- Apply GTM Agents cadence: Monday backlog groom, Wednesday build review, Friday learnings sync.\n- Require KPI guardrails per stage (activation, engagement, monetization) before authorizing build.\n- If a test risks Sales velocity, include Sales Director in approval routing per GTM Agents governance.\n\n## GTM Agents Experiment Operating Model\n1. **Backlog Intake** – ideas flow from GTM pods; Growth Marketer tags theme, objective, expected impact.\n2. **Prioritization** – score with RICE + qualitative \"strategic fit\" modifier; surface top 3 bets weekly.\n3. **Design & Instrumentation** – reference Serena\u002FContext7 to patch code + confirm documentation.\n4. **Launch & Monitor** – use guardrail-scorecard to watch leading indicators (churn, complaints, latency).\n5. **Learning Loop** – run Sequential Thinking retro; document hypothesis, result, decision, follow-up in backlog card.\n\n## KPI Guardrails (GTM Agents Reference)\n- Activation rate change must stay within ±3% of baseline for Tier-1 segments.\n- Revenue per visitor cannot drop more than 2% for more than 48h.\n- Support tickets tied to experiment variant must remain \u003C5% of total volume.\n\n## Weekly Experiment Packet Outline\n```\nWeek Ending: \u003CDate>\n\n1. Portfolio Snapshot – tests live, status, KPI trend (guardrail vs actual)\n2. Key Wins – hypothesis, uplift, next action (ship, iterate, expand)\n3. Guardrail Alerts – what tripped, mitigation taken (rollback? scope adjust?)\n4. Pipeline Impact – SQLs, ARR influenced, notable customer anecdotes\n5. Upcoming Launches – dependencies, owners, open questions\n```\n\nShare packet with Growth, Marketing Director, Sales Director, and RevOps to mirror GTM Agents's cross-functional communication rhythm.\n\n---\n",{"name":53,"description":54},"experiment-design-kit","Toolkit for structuring hypotheses, variants, guardrails, and measurement plans.","main","e76badf17e06864dd1f99dfd25e14335f1cfeea2",".claude\u002Fskills\u002Fecc\u002Farticle-writing","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":53,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add sakamoto-family-smile\u002Fagent_monorepo --skill experiment-design-kit",{"tool":67,"command":68},"bunx","bunx skills add sakamoto-family-smile\u002Fagent_monorepo --skill experiment-design-kit",{"tool":70,"command":71},"pnpm","pnpm dlx skills add sakamoto-family-smile\u002Fagent_monorepo --skill experiment-design-kit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fecc\u002Farticle-writing\u002FSKILL.md",true,[],[76,109,117,135,158,185],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":88,"publishedAt":48},"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",[82,85],{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"Video","remotion video","remotion video creation","creation","Remotion","Charts","Captions","Audio","3D","Composition","Animation","best practices","more","animations","domain-specific","domain","three","Rules","Lottie","for",{"skillNo":110,"name":111,"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":112,"categories":113,"keywords":114,"publishedAt":48},"01M6VCJ23NPECPSZJKGY691F75","hotcook-recipes","https:\u002F\u002Fgithub.com\u002Fsakamoto-family-smile\u002Fagent_monorepo\u002Fblob\u002Fmain\u002Fhotcook-agent\u002Fdata\u002Fskills\u002Fhotcook-recipes\u002FSKILL.md",[],[115,116],"hotcook recipes","recipes",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":129,"publishedAt":48},"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",[123,126],{"categoryNo":124,"categoryName":125,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":127,"categoryName":128,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师",[130,131,132,133,134],"code helper","helper","code","code review","review",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":147,"publishedAt":48},"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",[141,144],{"categoryNo":142,"categoryName":143,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[148,149,150,151,152,153,154,155,156,157],"research assistant","research","assistant","MCP","web","search","brave search","web research","brave","web research assistant",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":168,"publishedAt":48},"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",[164,167],{"categoryNo":165,"categoryName":166,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":127,"categoryName":128,"taxonomyType":25,"taxonomyTypeDesc":26},[169,170,171,32,172,173,108,174,175,176,177,178,179,180,181,42,182,183,153,184],"x api","api","with","limits","rate","threads","reading","native","posting","platform","patterns","api integration","twitter","auth","analytics","OAuth",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":48},"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",[191],{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},[193,194,195,196,151,197,198,132,199,200,201,202,42,203,204,205,206,176,207,32],"workspace surface audit","workspace","audit","hooks","workflows","connectors","capabilities","harness","repo","environment","up","harness setup","active","env","value"]