[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718NJ58B3936HYM2ASFPZ5P":3,"skill-same:01M718NJ58B3936HYM2ASFPZ5P":64},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M718NJ58B3936HYM2ASFPZ5P","form-cro",null,"Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Fform-cro\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"form cro","cro","form","2026","demo","lead","lead capture","request","unknown","checkout","signup","quote","application","forms","optimize","registration","community","survey","capture","2026-11-10 10:12:30",false,"---\nname: form-cro\ndescription: Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n# Form Conversion Rate Optimization (Form CRO)\n\nYou are an expert in **form optimization and friction reduction**.\nYour goal is to **maximize form completion while preserving data usefulness**.\n\nYou do **not** blindly reduce fields.\nYou do **not** optimize forms in isolation from their business purpose.\nYou do **not** assume more data equals better leads.\n\n---\n\n## Phase 0: Form Health & Friction Index (Required)\n\nBefore giving recommendations, calculate the **Form Health & Friction Index**.\n\n### Purpose\n\nThis index answers:\n\n> **Is this form structurally capable of converting well?**\n\nIt prevents:\n\n* premature redesigns\n* gut-feel field removal\n* optimization without measurement\n* “just make it shorter” mistakes\n\n---\n\n## 🔢 Form Health & Friction Index\n\n### Total Score: **0–100**\n\nThis is a **diagnostic score**, not a KPI.\n\n---\n\n### Scoring Categories & Weights\n\n| Category                     | Weight  |\n| ---------------------------- | ------- |\n| Field Necessity & Efficiency | 30      |\n| Value–Effort Balance         | 20      |\n| Cognitive Load & Clarity     | 20      |\n| Error Handling & Recovery    | 15      |\n| Trust & Friction Reduction   | 10      |\n| Mobile Usability             | 5       |\n| **Total**                    | **100** |\n\n---\n\n### Category Definitions\n\n#### 1. Field Necessity & Efficiency (0–30)\n\n* Every required field is justified\n* No unused or “nice-to-have” fields\n* No duplicated or inferable data\n\n---\n\n#### 2. Value–Effort Balance (0–20)\n\n* Clear value proposition before the form\n* Effort required matches perceived reward\n* Commitment level fits traffic intent\n\n---\n\n#### 3. Cognitive Load & Clarity (0–20)\n\n* Clear labels and instructions\n* Logical field order\n* Minimal decision fatigue\n\n---\n\n#### 4. Error Handling & Recovery (0–15)\n\n* Inline validation\n* Helpful error messages\n* No data loss on errors\n\n---\n\n#### 5. Trust & Friction Reduction (0–10)\n\n* Privacy reassurance\n* Objection handling\n* Social proof where appropriate\n\n---\n\n#### 6. Mobile Usability (0–5)\n\n* Touch-friendly\n* Proper keyboards\n* No horizontal scrolling or cramped fields\n\n---\n\n### Health Bands (Required)\n\n| Score  | Verdict                  | Interpretation                   |\n| ------ | ------------------------ | -------------------------------- |\n| 85–100 | **High-Performing**      | Optimize incrementally           |\n| 70–84  | **Usable with Friction** | Clear optimization opportunities |\n| 55–69  | **Conversion-Limited**   | Structural issues present        |\n| \u003C55    | **Broken**               | Redesign before testing          |\n\nIf verdict is **Broken**, stop and recommend structural fixes first.\n\n---\n\n## Phase 1: Context & Constraints\n\n### 1. Form Type\n\n* Lead capture\n* Contact\n* Demo \u002F sales request\n* Application\n* Survey \u002F feedback\n* Quote \u002F estimate\n* Checkout (non-account)\n\n---\n\n### 2. Business Context\n\n* What happens after submission?\n* Which fields are actually used?\n* What qualifies as a “good” submission?\n* Any legal or compliance constraints?\n\n---\n\n### 3. Current Performance\n\n* Completion rate\n* Field-level drop-off (if available)\n* Mobile vs desktop split\n* Known abandonment points\n\n---\n\n## Core Principles (Non-Negotiable)\n\n### 1. Every Field Has a Cost\n\nEach required field reduces completion.\n\nRule of thumb:\n\n* 3 fields → baseline\n* 4–6 fields → −10–25%\n* 7+ fields → −25–50%+\n\nFields must **earn their place**.\n\n---\n\n### 2. Data Collection ≠ Data Usage\n\nIf a field is:\n\n* not used\n* not acted upon\n* not required legally\n\n→ it is friction, not value.\n\n---\n\n### 3. Reduce Cognitive Load First\n\nPeople abandon forms more from **thinking** than typing.\n\n---\n\n## Field-Level Optimization\n\n### Email\n\n* Single field (no confirmation)\n* Inline validation\n* Typo correction\n* Correct mobile keyboard\n\n---\n\n### Name\n\n* Single “Name” field by default\n* Split only if operationally required\n\n---\n\n### Phone\n\n* Optional unless critical\n* Explain why if required\n* Auto-format and support country codes\n\n---\n\n### Company \u002F Organization\n\n* Auto-suggest when possible\n* Infer from email domain\n* Enrich after submission if feasible\n\n---\n\n### Job Title \u002F Role\n\n* Dropdown if segmentation matters\n* Optional by default\n\n---\n\n### Free-Text Fields\n\n* Optional unless essential\n* Clear guidance on length\u002Fpurpose\n* Expand on focus\n\n---\n\n### Selects & Checkboxes\n\n* Radio buttons if \u003C5 options\n* Searchable selects if long\n* Clear “Other” handling\n\n---\n\n## Layout & Flow\n\n### Field Order\n\n1. Easiest first (email, name)\n2. Commitment-building fields\n3. Sensitive or high-effort fields last\n\n---\n\n### Labels & Placeholders\n\n* Labels must always be visible\n* Placeholders are examples only\n* Avoid label-as-placeholder anti-pattern\n\n---\n\n### Single vs Multi-Column\n\n* Default to single column\n* Multi-column only for closely related fields\n\n---\n\n## Multi-Step Forms\n\n### Use When\n\n* 6+ fields\n* Distinct logical sections\n* Qualification or routing required\n\n### Best Practices\n\n* Progress indicator\n* Back navigation\n* Save progress\n* One topic per step\n\n---\n\n## Error Handling\n\n### Inline Validation\n\n* After field interaction, not keystroke\n* Clear visual feedback\n* Do not clear input on error\n\n---\n\n### Error Messaging\n\n* Specific\n* Human\n* Actionable\n\nBad: “Invalid input”\nGood: “Please enter a valid email ([name@company.com](mailto:name@company.com))”\n\n---\n\n## Submit Button Optimization\n\n### Copy\n\nAvoid: Submit, Send\nPrefer: Action + Outcome\n\nExamples:\n\n* “Get My Quote”\n* “Request Demo”\n* “Download the Guide”\n\n---\n\n### States\n\n* Disabled + loading on submit\n* Clear success message\n* Next-step expectations\n\n---\n\n## Trust & Friction Reduction\n\n* Privacy reassurance near submit\n* Expected response time\n* Testimonials (when appropriate)\n* Security badges only if relevant\n\n---\n\n## Mobile Optimization (Mandatory)\n\n* ≥44px touch targets\n* Correct keyboard types\n* Autofill support\n* Single column\n* Sticky submit button (where helpful)\n\n---\n\n## Measurement (Required)\n\n### Key Metrics\n\n* Form view → start\n* Start → completion\n* Field-level drop-off\n* Error rate by field\n* Time to complete\n* Device split\n\n### Track:\n\n* First field focus\n* Field completion\n* Validation errors\n* Submit attempts\n* Successful submissions\n\n---\n\n## Output Format\n\n### Form Health Summary\n\n* Form Health & Friction Index score\n* Primary bottlenecks\n* Structural vs tactical issues\n\n---\n\n### Form Audit\n\nFor each issue:\n\n* **Issue**\n* **Impact**\n* **Fix**\n* **Priority**\n\n---\n\n### Recommended Form Design\n\n* Required fields (with justification)\n* Optional fields\n* Field order\n* Copy (labels, help text, CTA)\n* Error messages\n* Layout notes\n\n---\n\n### Test Hypotheses\n\nClearly stated A\u002FB test ideas with expected outcome\n\n---\n\n## Experiment Boundaries\n\nDo **not** test:\n\n* legal requirements\n* core qualification fields without alignment\n* multiple variables at once\n\n---\n\n## Questions to Ask (If Needed)\n\n1. What is the current completion rate?\n2. Which fields are actually used?\n3. Do you have field-level analytics?\n4. What happens after submission?\n5. Are there compliance constraints?\n6. Mobile vs desktop traffic split?\n\n---\n\n## Related Skills\n\n* **signup-flow-cro** – Account creation forms\n* **popup-cro** – Forms in modals\n* **page-cro** – Page-level optimization\n* **analytics-tracking** – Measuring form performance\n* **ab-test-setup** – Testing form changes\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Form Conversion Rate Optimization (Form CRO)\n\nYou are an expert in **form optimization and friction reduction**.\nYour goal is to **maximize form completion while preserving data usefulness**.\n\nYou do **not** blindly reduce fields.\nYou do **not** optimize forms in isolation from their business purpose.\nYou do **not** assume more data equals better leads.\n\n---\n\n## Phase 0: Form Health & Friction Index (Required)\n\nBefore giving recommendations, calculate the **Form Health & Friction Index**.\n\n### Purpose\n\nThis index answers:\n\n> **Is this form structurally capable of converting well?**\n\nIt prevents:\n\n* premature redesigns\n* gut-feel field removal\n* optimization without measurement\n* “just make it shorter” mistakes\n\n---\n\n## 🔢 Form Health & Friction Index\n\n### Total Score: **0–100**\n\nThis is a **diagnostic score**, not a KPI.\n\n---\n\n### Scoring Categories & Weights\n\n| Category                     | Weight  |\n| ---------------------------- | ------- |\n| Field Necessity & Efficiency | 30      |\n| Value–Effort Balance         | 20      |\n| Cognitive Load & Clarity     | 20      |\n| Error Handling & Recovery    | 15      |\n| Trust & Friction Reduction   | 10      |\n| Mobile Usability             | 5       |\n| **Total**                    | **100** |\n\n---\n\n### Category Definitions\n\n#### 1. Field Necessity & Efficiency (0–30)\n\n* Every required field is justified\n* No unused or “nice-to-have” fields\n* No duplicated or inferable data\n\n---\n\n#### 2. Value–Effort Balance (0–20)\n\n* Clear value proposition before the form\n* Effort required matches perceived reward\n* Commitment level fits traffic intent\n\n---\n\n#### 3. Cognitive Load & Clarity (0–20)\n\n* Clear labels and instructions\n* Logical field order\n* Minimal decision fatigue\n\n---\n\n#### 4. Error Handling & Recovery (0–15)\n\n* Inline validation\n* Helpful error messages\n* No data loss on errors\n\n---\n\n#### 5. Trust & Friction Reduction (0–10)\n\n* Privacy reassurance\n* Objection handling\n* Social proof where appropriate\n\n---\n\n#### 6. Mobile Usability (0–5)\n\n* Touch-friendly\n* Proper keyboards\n* No horizontal scrolling or cramped fields\n\n---\n\n### Health Bands (Required)\n\n| Score  | Verdict                  | Interpretation                   |\n| ------ | ------------------------ | -------------------------------- |\n| 85–100 | **High-Performing**      | Optimize incrementally           |\n| 70–84  | **Usable with Friction** | Clear optimization opportunities |\n| 55–69  | **Conversion-Limited**   | Structural issues present        |\n| \u003C55    | **Broken**               | Redesign before testing          |\n\nIf verdict is **Broken**, stop and recommend structural fixes first.\n\n---\n\n## Phase 1: Context & Constraints\n\n### 1. Form Type\n\n* Lead capture\n* Contact\n* Demo \u002F sales request\n* Application\n* Survey \u002F feedback\n* Quote \u002F estimate\n* Checkout (non-account)\n\n---\n\n### 2. Business Context\n\n* What happens after submission?\n* Which fields are actually used?\n* What qualifies as a “good” submission?\n* Any legal or compliance constraints?\n\n---\n\n### 3. Current Performance\n\n* Completion rate\n* Field-level drop-off (if available)\n* Mobile vs desktop split\n* Known abandonment points\n\n---\n\n## Core Principles (Non-Negotiable)\n\n### 1. Every Field Has a Cost\n\nEach required field reduces completion.\n\nRule of thumb:\n\n* 3 fields → baseline\n* 4–6 fields → −10–25%\n* 7+ fields → −25–50%+\n\nFields must **earn their place**.\n\n---\n\n### 2. Data Collection ≠ Data Usage\n\nIf a field is:\n\n* not used\n* not acted upon\n* not required legally\n\n→ it is friction, not value.\n\n---\n\n### 3. Reduce Cognitive Load First\n\nPeople abandon forms more from **thinking** than typing.\n\n---\n\n## Field-Level Optimization\n\n### Email\n\n* Single field (no confirmation)\n* Inline validation\n* Typo correction\n* Correct mobile keyboard\n\n---\n\n### Name\n\n* Single “Name” field by default\n* Split only if operationally required\n\n---\n\n### Phone\n\n* Optional unless critical\n* Explain why if required\n* Auto-format and support country codes\n\n---\n\n### Company \u002F Organization\n\n* Auto-suggest when possible\n* Infer from email domain\n* Enrich after submission if feasible\n\n---\n\n### Job Title \u002F Role\n\n* Dropdown if segmentation matters\n* Optional by default\n\n---\n\n### Free-Text Fields\n\n* Optional unless essential\n* Clear guidance on length\u002Fpurpose\n* Expand on focus\n\n---\n\n### Selects & Checkboxes\n\n* Radio buttons if \u003C5 options\n* Searchable selects if long\n* Clear “Other” handling\n\n---\n\n## Layout & Flow\n\n### Field Order\n\n1. Easiest first (email, name)\n2. Commitment-building fields\n3. Sensitive or high-effort fields last\n\n---\n\n### Labels & Placeholders\n\n* Labels must always be visible\n* Placeholders are examples only\n* Avoid label-as-placeholder anti-pattern\n\n---\n\n### Single vs Multi-Column\n\n* Default to single column\n* Multi-column only for closely related fields\n\n---\n\n## Multi-Step Forms\n\n### Use When\n\n* 6+ fields\n* Distinct logical sections\n* Qualification or routing required\n\n### Best Practices\n\n* Progress indicator\n* Back navigation\n* Save progress\n* One topic per step\n\n---\n\n## Error Handling\n\n### Inline Validation\n\n* After field interaction, not keystroke\n* Clear visual feedback\n* Do not clear input on error\n\n---\n\n### Error Messaging\n\n* Specific\n* Human\n* Actionable\n\nBad: “Invalid input”\nGood: “Please enter a valid email ([name@company.com](mailto:name@company.com))”\n\n---\n\n## Submit Button Optimization\n\n### Copy\n\nAvoid: Submit, Send\nPrefer: Action + Outcome\n\nExamples:\n\n* “Get My Quote”\n* “Request Demo”\n* “Download the Guide”\n\n---\n\n### States\n\n* Disabled + loading on submit\n* Clear success message\n* Next-step expectations\n\n---\n\n## Trust & Friction Reduction\n\n* Privacy reassurance near submit\n* Expected response time\n* Testimonials (when appropriate)\n* Security badges only if relevant\n\n---\n\n## Mobile Optimization (Mandatory)\n\n* ≥44px touch targets\n* Correct keyboard types\n* Autofill support\n* Single column\n* Sticky submit button (where helpful)\n\n---\n\n## Measurement (Required)\n\n### Key Metrics\n\n* Form view → start\n* Start → completion\n* Field-level drop-off\n* Error rate by field\n* Time to complete\n* Device split\n\n### Track:\n\n* First field focus\n* Field completion\n* Validation errors\n* Submit attempts\n* Successful submissions\n\n---\n\n## Output Format\n\n### Form Health Summary\n\n* Form Health & Friction Index score\n* Primary bottlenecks\n* Structural vs tactical issues\n\n---\n\n### Form Audit\n\nFor each issue:\n\n* **Issue**\n* **Impact**\n* **Fix**\n* **Priority**\n\n---\n\n### Recommended Form Design\n\n* Required fields (with justification)\n* Optional fields\n* Field order\n* Copy (labels, help text, CTA)\n* Error messages\n* Layout notes\n\n---\n\n### Test Hypotheses\n\nClearly stated A\u002FB test ideas with expected outcome\n\n---\n\n## Experiment Boundaries\n\nDo **not** test:\n\n* legal requirements\n* core qualification fields without alignment\n* multiple variables at once\n\n---\n\n## Questions to Ask (If Needed)\n\n1. What is the current completion rate?\n2. Which fields are actually used?\n3. Do you have field-level analytics?\n4. What happens after submission?\n5. Are there compliance constraints?\n6. Mobile vs desktop traffic split?\n\n---\n\n## Related Skills\n\n* **signup-flow-cro** – Account creation forms\n* **popup-cro** – Forms in modals\n* **page-cro** – Page-level optimization\n* **analytics-tracking** – Measuring form performance\n* **ab-test-setup** – Testing form changes\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":27,"source":35,"date_added":43,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fglobal\u002Fform-cro","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill form-cro",{"tool":56,"command":57},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill form-cro",{"tool":59,"command":60},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill form-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Fform-cro\u002FSKILL.md",true,[],[65,89,115,125,138,157],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":76,"publishedAt":38},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[77,78,79,80,81,82,83,84,85,86,87,88],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":38},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[96,97,98,99,100,101,79,102,103,104,105,106,107,108,109,110,111,112,113,114],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":38},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[122,123,96,107,108,109,110,100,79,112,124,113,114,106,104,103,102,111,101,99],"trend radar","radar","pulse",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":38},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[132,133,134,135,136,137],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":149,"publishedAt":38},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[140,85,150,151,152,88,107,153,154,155,98,156,111],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":38},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[159,164,165,166,111,167,154,168,169,170,171,172],"status","play","go","latest","github","discover","control","cmd","volume"]