[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XDWE5PYRF2ZP8KKYRZKBM4":3,"skill-same:01M6XDWE5PYRF2ZP8KKYRZKBM4":49},{"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":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M6XDWE5PYRF2ZP8KKYRZKBM4","security-review",null,"Run a comprehensive security review on code","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\u002Fcodex\u002Fsecurity-review\u002FSKILL.md",[],[19,20,21,22,23],"review","security","security review","run","code","2026-11-10 10:12:30",false,"---\nname: security-review\ndescription: Run a comprehensive security review on code\n---\n\n# Security Review Skill\n\nConduct a thorough security audit checking for OWASP Top 10 vulnerabilities, hardcoded secrets, and unsafe patterns.\n\n## When to Use\n\nThis skill activates when:\n- User requests \"security review\", \"security audit\"\n- After writing code that handles user input\n- After adding new API endpoints\n- After modifying authentication\u002Fauthorization logic\n- Before deploying to production\n- After adding external dependencies\n\n## What It Does\n\n## GPT-5.4 Guidance Alignment\n\n- Default to concise, evidence-dense progress and completion reporting unless the user or risk level requires more detail.\n- Treat newer user task updates as local overrides for the active workflow branch while preserving earlier non-conflicting constraints.\n- If correctness depends on additional inspection, retrieval, execution, or verification, keep using the relevant tools until the security review is grounded.\n- Continue through clear, low-risk, reversible next steps automatically; ask only when the next step is materially branching, destructive, or preference-dependent.\n\nDelegates to the `security-reviewer` agent (THOROUGH tier) for deep security analysis:\n\n1. **OWASP Top 10 Scan**\n   - A01: Broken Access Control\n   - A02: Cryptographic Failures\n   - A03: Injection (SQL, NoSQL, Command, XSS)\n   - A04: Insecure Design\n   - A05: Security Misconfiguration\n   - A06: Vulnerable and Outdated Components\n   - A07: Identification and Authentication Failures\n   - A08: Software and Data Integrity Failures\n   - A09: Security Logging and Monitoring Failures\n   - A10: Server-Side Request Forgery (SSRF)\n\n2. **Secrets Detection**\n   - Hardcoded API keys\n   - Passwords in source code\n   - Private keys in repo\n   - Tokens and credentials\n   - Connection strings with secrets\n\n3. **Input Validation**\n   - All user inputs sanitized\n   - SQL\u002FNoSQL injection prevention\n   - Command injection prevention\n   - XSS prevention (output escaping)\n   - Path traversal prevention\n\n4. **Authentication\u002FAuthorization**\n   - Proper password hashing (bcrypt, argon2)\n   - Session management security\n   - Access control enforcement\n   - JWT implementation security\n\n5. **Dependency Security**\n   - Run `npm audit` for known vulnerabilities\n   - Check for outdated dependencies\n   - Identify high-severity CVEs\n\n## Agent Delegation\n\n```\ndelegate(\n  role=\"security-reviewer\",\n  tier=\"THOROUGH\",\n  prompt=\"SECURITY REVIEW TASK\n\nConduct comprehensive security audit of codebase.\n\nScope: [specific files or entire codebase]\n\nSecurity Checklist:\n1. OWASP Top 10 scan\n2. Hardcoded secrets detection\n3. Input validation review\n4. Authentication\u002Fauthorization review\n5. Dependency vulnerability scan (npm audit)\n\nOutput: Security review report with:\n- Summary of findings by severity (CRITICAL, HIGH, MEDIUM, LOW)\n- Specific file:line locations\n- CVE references where applicable\n- Remediation guidance for each issue\n- Overall security posture assessment\"\n)\n```\n\n## External Model Consultation (Preferred)\n\nThe security-reviewer agent SHOULD consult Codex for cross-validation.\n\n### Protocol\n1. **Form your OWN security analysis FIRST** - Complete the review independently\n2. **Consult for validation** - Cross-check findings with Codex\n3. **Critically evaluate** - Never blindly adopt external findings\n4. **Graceful fallback** - Never block if tools unavailable\n\n### When to Consult\n- Authentication\u002Fauthorization code\n- Cryptographic implementations\n- Input validation for untrusted data\n- High-risk vulnerability patterns\n- Production deployment code\n\n### When to Skip\n- Low-risk utility code\n- Well-audited patterns\n- Time-critical security assessments\n- Code with existing security tests\n\n### Tool Usage\nBefore first MCP tool use, call `ToolSearch(\"mcp\")` to discover deferred MCP tools.\nUse `mcp__x__ask_codex` with `agent_role: \"security-reviewer\"`.\nIf ToolSearch finds no MCP tools, fall back to the `security-reviewer` agent.\n\n**Note:** Security second opinions are high-value. Consider consulting for CRITICAL\u002FHIGH findings.\n\n## Output Format\n\n```\nSECURITY REVIEW REPORT\n======================\n\nScope: Entire codebase (42 files scanned)\nScan Date: 2026-01-24T14:30:00Z\n\nCRITICAL (2)\n------------\n1. src\u002Fapi\u002Fauth.ts:89 - Hardcoded API Key\n   Finding: AWS API key hardcoded in source code\n   Impact: Credential exposure if code is public or leaked\n   Remediation: Move to environment variables, rotate key immediately\n   Reference: OWASP A02:2021 – Cryptographic Failures\n\n2. src\u002Fdb\u002Fquery.ts:45 - SQL Injection Vulnerability\n   Finding: User input concatenated directly into SQL query\n   Impact: Attacker can execute arbitrary SQL commands\n   Remediation: Use parameterized queries or ORM\n   Reference: OWASP A03:2021 – Injection\n\nHIGH (5)\n--------\n3. src\u002Fauth\u002Fpassword.ts:22 - Weak Password Hashing\n   Finding: Passwords hashed with MD5 (cryptographically broken)\n   Impact: Passwords can be reversed via rainbow tables\n   Remediation: Use bcrypt or argon2 with appropriate work factor\n   Reference: OWASP A02:2021 – Cryptographic Failures\n\n4. src\u002Fcomponents\u002FUserInput.tsx:67 - XSS Vulnerability\n   Finding: User input rendered with dangerouslySetInnerHTML\n   Impact: Cross-site scripting attack vector\n   Remediation: Sanitize HTML or use safe rendering\n   Reference: OWASP A03:2021 – Injection (XSS)\n\n5. src\u002Fapi\u002Fupload.ts:34 - Path Traversal Vulnerability\n   Finding: User-controlled filename used without validation\n   Impact: Attacker can read\u002Fwrite arbitrary files\n   Remediation: Validate and sanitize filenames, use allowlist\n   Reference: OWASP A01:2021 – Broken Access Control\n\n...\n\nMEDIUM (8)\n----------\n...\n\nLOW (12)\n--------\n...\n\nDEPENDENCY VULNERABILITIES\n--------------------------\nFound 3 vulnerabilities via npm audit:\n\nCRITICAL: axios@0.21.0 - Server-Side Request Forgery (CVE-2021-3749)\n  Installed: axios@0.21.0\n  Fix: npm install axios@0.21.2\n\nHIGH: lodash@4.17.19 - Prototype Pollution (CVE-2020-8203)\n  Installed: lodash@4.17.19\n  Fix: npm install lodash@4.17.21\n\n...\n\nOVERALL ASSESSMENT\n------------------\nSecurity Posture: POOR (2 CRITICAL, 5 HIGH issues)\n\nImmediate Actions Required:\n1. Rotate exposed AWS API key\n2. Fix SQL injection in db\u002Fquery.ts\n3. Upgrade password hashing to bcrypt\n4. Update vulnerable dependencies\n\nRecommendation: DO NOT DEPLOY until CRITICAL and HIGH issues resolved.\n```\n\n## Security Checklist\n\nThe security-reviewer agent verifies:\n\n### Authentication & Authorization\n- [ ] Passwords hashed with strong algorithm (bcrypt\u002Fargon2)\n- [ ] Session tokens cryptographically random\n- [ ] JWT tokens properly signed and validated\n- [ ] Access control enforced on all protected resources\n- [ ] No authentication bypass vulnerabilities\n\n### Input Validation\n- [ ] All user inputs validated and sanitized\n- [ ] SQL queries use parameterization (no string concatenation)\n- [ ] NoSQL queries prevent injection\n- [ ] File uploads validated (type, size, content)\n- [ ] URLs validated to prevent SSRF\n\n### Output Encoding\n- [ ] HTML output escaped to prevent XSS\n- [ ] JSON responses properly encoded\n- [ ] No user data in error messages\n- [ ] Content-Security-Policy headers set\n\n### Secrets Management\n- [ ] No hardcoded API keys\n- [ ] No passwords in source code\n- [ ] No private keys in repo\n- [ ] Environment variables used for secrets\n- [ ] Secrets not logged or exposed in errors\n\n### Cryptography\n- [ ] Strong algorithms used (AES-256, RSA-2048+)\n- [ ] Proper key management\n- [ ] Random number generation cryptographically secure\n- [ ] TLS\u002FHTTPS enforced for sensitive data\n\n### Dependencies\n- [ ] No known vulnerabilities in dependencies\n- [ ] Dependencies up to date\n- [ ] No CRITICAL or HIGH CVEs\n- [ ] Dependency sources verified\n\n## Severity Definitions\n\n**CRITICAL** - Exploitable vulnerability with severe impact (data breach, RCE, credential theft)\n**HIGH** - Vulnerability requiring specific conditions but serious impact\n**MEDIUM** - Security weakness with limited impact or difficult exploitation\n**LOW** - Best practice violation or minor security concern\n\n## Remediation Priority\n\n1. **Rotate exposed secrets** - Immediate (within 1 hour)\n2. **Fix CRITICAL** - Urgent (within 24 hours)\n3. **Fix HIGH** - Important (within 1 week)\n4. **Fix MEDIUM** - Planned (within 1 month)\n5. **Fix LOW** - Backlog (when convenient)\n\n\n## Scenario Examples\n\n**Good:** The user says `continue` after the workflow already has a clear next step. Continue the current branch of work instead of restarting or re-asking the same question.\n\n**Good:** The user changes only the output shape or downstream delivery step (for example `make a PR`). Preserve earlier non-conflicting workflow constraints and apply the update locally.\n\n**Bad:** The user says `continue`, and the workflow restarts discovery or stops before the missing verification\u002Fevidence is gathered.\n\n## Use with Other Skills\n\n**With Team:**\n```\n\u002Fteam \"run security review on authentication module\"\n```\nUses: explore → security-reviewer → executor → security-reviewer (re-verify)\n\n**With Swarm:**\n```\n\u002Fswarm 4:security-reviewer \"audit all API endpoints\"\n```\nParallel security review across multiple endpoints.\n\n**With Ralph:**\n```\n\u002Fralph security-review then fix all issues\n```\nReview, fix, re-review until all issues resolved.\n\n## Best Practices\n\n- **Review early** - Security by design, not afterthought\n- **Review often** - Every major feature or API change\n- **Automate** - Run security scans in CI\u002FCD pipeline\n- **Fix immediately** - Don't accumulate security debt\n- **Educate** - Learn from findings to prevent future issues\n- **Verify fixes** - Re-run security review after remediation\n","# Security Review Skill\n\nConduct a thorough security audit checking for OWASP Top 10 vulnerabilities, hardcoded secrets, and unsafe patterns.\n\n## When to Use\n\nThis skill activates when:\n- User requests \"security review\", \"security audit\"\n- After writing code that handles user input\n- After adding new API endpoints\n- After modifying authentication\u002Fauthorization logic\n- Before deploying to production\n- After adding external dependencies\n\n## What It Does\n\n## GPT-5.4 Guidance Alignment\n\n- Default to concise, evidence-dense progress and completion reporting unless the user or risk level requires more detail.\n- Treat newer user task updates as local overrides for the active workflow branch while preserving earlier non-conflicting constraints.\n- If correctness depends on additional inspection, retrieval, execution, or verification, keep using the relevant tools until the security review is grounded.\n- Continue through clear, low-risk, reversible next steps automatically; ask only when the next step is materially branching, destructive, or preference-dependent.\n\nDelegates to the `security-reviewer` agent (THOROUGH tier) for deep security analysis:\n\n1. **OWASP Top 10 Scan**\n   - A01: Broken Access Control\n   - A02: Cryptographic Failures\n   - A03: Injection (SQL, NoSQL, Command, XSS)\n   - A04: Insecure Design\n   - A05: Security Misconfiguration\n   - A06: Vulnerable and Outdated Components\n   - A07: Identification and Authentication Failures\n   - A08: Software and Data Integrity Failures\n   - A09: Security Logging and Monitoring Failures\n   - A10: Server-Side Request Forgery (SSRF)\n\n2. **Secrets Detection**\n   - Hardcoded API keys\n   - Passwords in source code\n   - Private keys in repo\n   - Tokens and credentials\n   - Connection strings with secrets\n\n3. **Input Validation**\n   - All user inputs sanitized\n   - SQL\u002FNoSQL injection prevention\n   - Command injection prevention\n   - XSS prevention (output escaping)\n   - Path traversal prevention\n\n4. **Authentication\u002FAuthorization**\n   - Proper password hashing (bcrypt, argon2)\n   - Session management security\n   - Access control enforcement\n   - JWT implementation security\n\n5. **Dependency Security**\n   - Run `npm audit` for known vulnerabilities\n   - Check for outdated dependencies\n   - Identify high-severity CVEs\n\n## Agent Delegation\n\n```\ndelegate(\n  role=\"security-reviewer\",\n  tier=\"THOROUGH\",\n  prompt=\"SECURITY REVIEW TASK\n\nConduct comprehensive security audit of codebase.\n\nScope: [specific files or entire codebase]\n\nSecurity Checklist:\n1. OWASP Top 10 scan\n2. Hardcoded secrets detection\n3. Input validation review\n4. Authentication\u002Fauthorization review\n5. Dependency vulnerability scan (npm audit)\n\nOutput: Security review report with:\n- Summary of findings by severity (CRITICAL, HIGH, MEDIUM, LOW)\n- Specific file:line locations\n- CVE references where applicable\n- Remediation guidance for each issue\n- Overall security posture assessment\"\n)\n```\n\n## External Model Consultation (Preferred)\n\nThe security-reviewer agent SHOULD consult Codex for cross-validation.\n\n### Protocol\n1. **Form your OWN security analysis FIRST** - Complete the review independently\n2. **Consult for validation** - Cross-check findings with Codex\n3. **Critically evaluate** - Never blindly adopt external findings\n4. **Graceful fallback** - Never block if tools unavailable\n\n### When to Consult\n- Authentication\u002Fauthorization code\n- Cryptographic implementations\n- Input validation for untrusted data\n- High-risk vulnerability patterns\n- Production deployment code\n\n### When to Skip\n- Low-risk utility code\n- Well-audited patterns\n- Time-critical security assessments\n- Code with existing security tests\n\n### Tool Usage\nBefore first MCP tool use, call `ToolSearch(\"mcp\")` to discover deferred MCP tools.\nUse `mcp__x__ask_codex` with `agent_role: \"security-reviewer\"`.\nIf ToolSearch finds no MCP tools, fall back to the `security-reviewer` agent.\n\n**Note:** Security second opinions are high-value. Consider consulting for CRITICAL\u002FHIGH findings.\n\n## Output Format\n\n```\nSECURITY REVIEW REPORT\n======================\n\nScope: Entire codebase (42 files scanned)\nScan Date: 2026-01-24T14:30:00Z\n\nCRITICAL (2)\n------------\n1. src\u002Fapi\u002Fauth.ts:89 - Hardcoded API Key\n   Finding: AWS API key hardcoded in source code\n   Impact: Credential exposure if code is public or leaked\n   Remediation: Move to environment variables, rotate key immediately\n   Reference: OWASP A02:2021 – Cryptographic Failures\n\n2. src\u002Fdb\u002Fquery.ts:45 - SQL Injection Vulnerability\n   Finding: User input concatenated directly into SQL query\n   Impact: Attacker can execute arbitrary SQL commands\n   Remediation: Use parameterized queries or ORM\n   Reference: OWASP A03:2021 – Injection\n\nHIGH (5)\n--------\n3. src\u002Fauth\u002Fpassword.ts:22 - Weak Password Hashing\n   Finding: Passwords hashed with MD5 (cryptographically broken)\n   Impact: Passwords can be reversed via rainbow tables\n   Remediation: Use bcrypt or argon2 with appropriate work factor\n   Reference: OWASP A02:2021 – Cryptographic Failures\n\n4. src\u002Fcomponents\u002FUserInput.tsx:67 - XSS Vulnerability\n   Finding: User input rendered with dangerouslySetInnerHTML\n   Impact: Cross-site scripting attack vector\n   Remediation: Sanitize HTML or use safe rendering\n   Reference: OWASP A03:2021 – Injection (XSS)\n\n5. src\u002Fapi\u002Fupload.ts:34 - Path Traversal Vulnerability\n   Finding: User-controlled filename used without validation\n   Impact: Attacker can read\u002Fwrite arbitrary files\n   Remediation: Validate and sanitize filenames, use allowlist\n   Reference: OWASP A01:2021 – Broken Access Control\n\n...\n\nMEDIUM (8)\n----------\n...\n\nLOW (12)\n--------\n...\n\nDEPENDENCY VULNERABILITIES\n--------------------------\nFound 3 vulnerabilities via npm audit:\n\nCRITICAL: axios@0.21.0 - Server-Side Request Forgery (CVE-2021-3749)\n  Installed: axios@0.21.0\n  Fix: npm install axios@0.21.2\n\nHIGH: lodash@4.17.19 - Prototype Pollution (CVE-2020-8203)\n  Installed: lodash@4.17.19\n  Fix: npm install lodash@4.17.21\n\n...\n\nOVERALL ASSESSMENT\n------------------\nSecurity Posture: POOR (2 CRITICAL, 5 HIGH issues)\n\nImmediate Actions Required:\n1. Rotate exposed AWS API key\n2. Fix SQL injection in db\u002Fquery.ts\n3. Upgrade password hashing to bcrypt\n4. Update vulnerable dependencies\n\nRecommendation: DO NOT DEPLOY until CRITICAL and HIGH issues resolved.\n```\n\n## Security Checklist\n\nThe security-reviewer agent verifies:\n\n### Authentication & Authorization\n- [ ] Passwords hashed with strong algorithm (bcrypt\u002Fargon2)\n- [ ] Session tokens cryptographically random\n- [ ] JWT tokens properly signed and validated\n- [ ] Access control enforced on all protected resources\n- [ ] No authentication bypass vulnerabilities\n\n### Input Validation\n- [ ] All user inputs validated and sanitized\n- [ ] SQL queries use parameterization (no string concatenation)\n- [ ] NoSQL queries prevent injection\n- [ ] File uploads validated (type, size, content)\n- [ ] URLs validated to prevent SSRF\n\n### Output Encoding\n- [ ] HTML output escaped to prevent XSS\n- [ ] JSON responses properly encoded\n- [ ] No user data in error messages\n- [ ] Content-Security-Policy headers set\n\n### Secrets Management\n- [ ] No hardcoded API keys\n- [ ] No passwords in source code\n- [ ] No private keys in repo\n- [ ] Environment variables used for secrets\n- [ ] Secrets not logged or exposed in errors\n\n### Cryptography\n- [ ] Strong algorithms used (AES-256, RSA-2048+)\n- [ ] Proper key management\n- [ ] Random number generation cryptographically secure\n- [ ] TLS\u002FHTTPS enforced for sensitive data\n\n### Dependencies\n- [ ] No known vulnerabilities in dependencies\n- [ ] Dependencies up to date\n- [ ] No CRITICAL or HIGH CVEs\n- [ ] Dependency sources verified\n\n## Severity Definitions\n\n**CRITICAL** - Exploitable vulnerability with severe impact (data breach, RCE, credential theft)\n**HIGH** - Vulnerability requiring specific conditions but serious impact\n**MEDIUM** - Security weakness with limited impact or difficult exploitation\n**LOW** - Best practice violation or minor security concern\n\n## Remediation Priority\n\n1. **Rotate exposed secrets** - Immediate (within 1 hour)\n2. **Fix CRITICAL** - Urgent (within 24 hours)\n3. **Fix HIGH** - Important (within 1 week)\n4. **Fix MEDIUM** - Planned (within 1 month)\n5. **Fix LOW** - Backlog (when convenient)\n\n\n## Scenario Examples\n\n**Good:** The user says `continue` after the workflow already has a clear next step. Continue the current branch of work instead of restarting or re-asking the same question.\n\n**Good:** The user changes only the output shape or downstream delivery step (for example `make a PR`). Preserve earlier non-conflicting workflow constraints and apply the update locally.\n\n**Bad:** The user says `continue`, and the workflow restarts discovery or stops before the missing verification\u002Fevidence is gathered.\n\n## Use with Other Skills\n\n**With Team:**\n```\n\u002Fteam \"run security review on authentication module\"\n```\nUses: explore → security-reviewer → executor → security-reviewer (re-verify)\n\n**With Swarm:**\n```\n\u002Fswarm 4:security-reviewer \"audit all API endpoints\"\n```\nParallel security review across multiple endpoints.\n\n**With Ralph:**\n```\n\u002Fralph security-review then fix all issues\n```\nReview, fix, re-review until all issues resolved.\n\n## Best Practices\n\n- **Review early** - Security by design, not afterthought\n- **Review often** - Every major feature or API change\n- **Automate** - Run security scans in CI\u002FCD pipeline\n- **Fix immediately** - Don't accumulate security debt\n- **Educate** - Learn from findings to prevent future issues\n- **Verify fixes** - Re-run security review after remediation\n",{"name":5,"description":7},"main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcodex\u002Fsecurity-review","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill security-review",{"tool":41,"command":42},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill security-review",{"tool":44,"command":45},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill security-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcodex\u002Fsecurity-review\u002FSKILL.md",true,[],[50,74,100,110,123,142],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":61,"publishedAt":24},"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",[56],{"categoryNo":57,"categoryName":58,"taxonomyType":59,"taxonomyTypeDesc":60},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[62,63,64,65,66,67,68,69,70,71,72,73],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":24},"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",[],[81,82,83,84,85,86,64,87,88,89,90,91,92,93,94,95,96,97,98,99],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":24},"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",[],[107,108,81,92,93,94,95,85,64,97,109,98,99,91,89,88,87,96,86,84],"trend radar","radar","pulse",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":24},"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",[],[117,118,119,120,121,122],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":134,"publishedAt":24},"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",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[125,70,135,136,137,73,92,138,139,140,83,141,96],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":24},"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",[],[144,149,150,151,96,152,139,153,154,155,156,157],"status","play","go","latest","github","discover","control","cmd","volume"]