[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EZMAMTSE7VGF26952F2YTT":3,"skill-same:01M6EZMAMTSE7VGF26952F2YTT":99},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":77,"commitSha":78,"skillDirectory":79,"forksCount":80,"repositoryHtmlUrl":81,"repositoryHomepageUrl":6,"ownerHtmlUrl":82,"ownerBlogUrl":6,"ownerDescription":83,"updatedAt":84,"install":85,"resources":98},"01M6EZMAMTSE7VGF26952F2YTT","technical-analytical-writing",null,"Write clear technical analysis, system architecture documents, decision records, and research synthesis. Covers argument structure, evidence-based reasoning, and technical communication patterns. Triggers on technical writing, architecture documentation, ADR creation, or analytical essay requests.","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\u002Fdocumentation\u002Ftechnical-analytical-writing\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"technical analytical writing","analytical","technical","writing","write","architecture-docs","stranger-test","technical analysis","evidence-based reasoning","technical-writing","creation","structure","decision","analysis","doc","communication","documents","documentation","architecture","workflow","2026-11-10 10:12:30",false,"---\nname: technical-analytical-writing\ndescription: Write clear technical analysis, system architecture documents, decision records, and research synthesis. Covers argument structure, evidence-based reasoning, and technical communication patterns. Triggers on technical writing, architecture documentation, ADR creation, or analytical essay requests.\nlicense: MIT\ncomplexity: intermediate\ntime_to_learn: 30min\ntags:\n  - technical-writing\n  - architecture-docs\n  - adr\n  - analysis\n  - documentation\ngovernance_phases: [shape, prove]\ngovernance_norm_group: documentation-standard\norgan_affinity: [organ-v]\ntriggers: [user-asks-about-technical-writing, context:architecture-docs, context:adr, context:technical-analysis, context:decision-record]\ncomplements: [doc-coauthoring, stranger-test-protocol, research-synthesis-workflow]\n---\n\n# Technical Analytical Writing\n\nCommunicate complex technical ideas clearly through structured analysis and evidence-based reasoning.\n\n## Document Types\n\n### Architecture Decision Record (ADR)\n\n```markdown\n# ADR-{NNN}: {Decision Title}\n\n**Status:** Proposed | Accepted | Deprecated | Superseded by ADR-{NNN}\n**Date:** YYYY-MM-DD\n**Deciders:** {names\u002Froles}\n\n## Context\n\nWhat is the issue that motivates this decision? What forces are at play?\n\n## Decision\n\nWhat is the change being proposed or decided?\n\n## Consequences\n\n### Positive\n- {benefit}\n\n### Negative\n- {tradeoff}\n\n### Neutral\n- {observation}\n\n## Alternatives Considered\n\n### {Alternative A}\n- Pros: {list}\n- Cons: {list}\n- Why rejected: {reason}\n```\n\n### System Analysis Document\n\n```markdown\n# {System\u002FComponent} Analysis\n\n## Executive Summary\n{2-3 sentences: what, why, recommendation}\n\n## Current State\n{What exists today, with evidence}\n\n## Problem Statement\n{Specific, measurable issue being addressed}\n\n## Analysis\n{Evidence-based investigation}\n\n## Recommendations\n{Ordered by priority, with effort estimates}\n\n## Appendix\n{Raw data, detailed metrics, supplementary evidence}\n```\n\n### Technical RFC\n\n```markdown\n# RFC: {Title}\n\n**Author:** {name}\n**Status:** Draft | Review | Accepted | Rejected\n**Created:** YYYY-MM-DD\n**Review deadline:** YYYY-MM-DD\n\n## Summary\n{One paragraph: what this proposes}\n\n## Motivation\n{Why this is needed, with concrete examples}\n\n## Detailed Design\n{How it works, with diagrams and code examples}\n\n## Drawbacks\n{Honest assessment of downsides}\n\n## Alternatives\n{What else was considered and why this approach wins}\n\n## Unresolved Questions\n{Open items for discussion}\n```\n\n## Writing Principles\n\n### Argument Structure\n\nEvery analytical section follows:\n\n1. **Claim** — What you're asserting\n2. **Evidence** — Data, metrics, code examples supporting the claim\n3. **Reasoning** — Why the evidence supports the claim\n4. **Implication** — What follows from this being true\n\n### Evidence Hierarchy\n\n| Strength | Evidence Type | Example |\n|----------|--------------|---------|\n| Strongest | Production metrics | \"P99 latency increased 3x after migration\" |\n| Strong | Reproducible test | \"Benchmark shows 40ms vs 120ms\" |\n| Moderate | Code analysis | \"This pattern creates N+1 queries\" |\n| Weak | Expert opinion | \"The team believes this will scale\" |\n| Weakest | Analogy | \"Netflix does it this way\" |\n\n### The Pyramid Principle\n\nLead with the conclusion, then support:\n\n**Bad:**\n> We analyzed the database, then the cache layer, then the API, and found that response times are slow because the cache hit rate is only 23%.\n\n**Good:**\n> Cache hit rate is 23%, causing slow response times. The database query layer generates cache keys inconsistently, leading to unnecessary misses. Standardizing key generation would bring hit rate to ~85%.\n\n## Structural Patterns\n\n### Problem-Solution-Evidence\n\n```markdown\n## {Problem Name}\n\n**Problem:** {specific, measurable issue}\n\n**Solution:** {proposed change}\n\n**Evidence:** {why this solution addresses the problem}\n\n**Effort:** {T-shirt size + key dependencies}\n```\n\n### Compare-Contrast Table\n\n```markdown\n| Criterion | Option A | Option B | Option C |\n|-----------|----------|----------|----------|\n| Performance | ★★★ | ★★ | ★★★ |\n| Complexity | Low | Medium | High |\n| Team familiarity | High | Low | Medium |\n| Maintenance cost | Low | High | Medium |\n| **Recommendation** | **✓** | | |\n```\n\n### Risk Matrix\n\n```markdown\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| API rate limiting | High | Medium | Client-side rate limiter + cache |\n| Data migration failure | Low | Critical | Rollback plan + dry-run first |\n| Team bandwidth | Medium | High | Phased rollout |\n```\n\n## Style Guidelines\n\n### Clarity\n\n- **Active voice:** \"The scheduler triggers the job\" not \"The job is triggered by the scheduler\"\n- **Concrete nouns:** \"The API returns a 429 status\" not \"There are issues with the API\"\n- **Specific numbers:** \"P99 latency is 230ms\" not \"Latency is high\"\n\n### Conciseness\n\n- Lead with the point, not the preamble\n- One idea per paragraph\n- Cut \"In order to\" → \"To\"\n- Cut \"It is important to note that\" → (just state it)\n- Cut \"As mentioned previously\" → (don't mention it)\n\n### Technical Accuracy\n\n- Verify all metrics and measurements\n- Include measurement methodology\n- Distinguish between observations and interpretations\n- Cite sources for external claims\n- Date all data (\"as of March 2026\")\n\n## Diagrams\n\n### When to Use Diagrams\n\n| Situation | Diagram Type |\n|-----------|-------------|\n| System components | Architecture diagram (boxes + arrows) |\n| Process flow | Flowchart or sequence diagram |\n| Data relationships | ER diagram |\n| Timeline | Gantt or timeline |\n| Hierarchy | Tree diagram |\n| Comparison | Table (not a diagram) |\n\n### Mermaid for Inline Diagrams\n\n````markdown\n```mermaid\ngraph LR\n    A[Client] --> B[API Gateway]\n    B --> C[Auth Service]\n    B --> D[Skills Service]\n    D --> E[(Database)]\n```\n````\n\n## Review Checklist\n\n- [ ] Executive summary is self-contained (reader gets the point without reading further)\n- [ ] Every claim has supporting evidence\n- [ ] Alternatives are fairly presented (not strawmen)\n- [ ] Risks and tradeoffs acknowledged honestly\n- [ ] Audience-appropriate level of detail\n- [ ] Diagrams have legends and labels\n- [ ] All acronyms defined on first use\n- [ ] Stranger test: a new team member can follow the argument\n\n## Anti-Patterns\n\n- **Burying the lead** — Put conclusions first, evidence after\n- **Appeal to authority** — \"Google does it\" is not an argument; explain why it works\n- **False precision** — \"This will improve performance by 47.3%\" without measurement methodology\n- **Missing alternatives** — Always compare at least 2-3 options\n- **Scope creep** — Stay focused on the stated question; flag tangents for separate docs\n- **No expiration date** — All analysis should include \"valid as of\" and conditions for revisiting\n","# Technical Analytical Writing\n\nCommunicate complex technical ideas clearly through structured analysis and evidence-based reasoning.\n\n## Document Types\n\n### Architecture Decision Record (ADR)\n\n```markdown\n# ADR-{NNN}: {Decision Title}\n\n**Status:** Proposed | Accepted | Deprecated | Superseded by ADR-{NNN}\n**Date:** YYYY-MM-DD\n**Deciders:** {names\u002Froles}\n\n## Context\n\nWhat is the issue that motivates this decision? What forces are at play?\n\n## Decision\n\nWhat is the change being proposed or decided?\n\n## Consequences\n\n### Positive\n- {benefit}\n\n### Negative\n- {tradeoff}\n\n### Neutral\n- {observation}\n\n## Alternatives Considered\n\n### {Alternative A}\n- Pros: {list}\n- Cons: {list}\n- Why rejected: {reason}\n```\n\n### System Analysis Document\n\n```markdown\n# {System\u002FComponent} Analysis\n\n## Executive Summary\n{2-3 sentences: what, why, recommendation}\n\n## Current State\n{What exists today, with evidence}\n\n## Problem Statement\n{Specific, measurable issue being addressed}\n\n## Analysis\n{Evidence-based investigation}\n\n## Recommendations\n{Ordered by priority, with effort estimates}\n\n## Appendix\n{Raw data, detailed metrics, supplementary evidence}\n```\n\n### Technical RFC\n\n```markdown\n# RFC: {Title}\n\n**Author:** {name}\n**Status:** Draft | Review | Accepted | Rejected\n**Created:** YYYY-MM-DD\n**Review deadline:** YYYY-MM-DD\n\n## Summary\n{One paragraph: what this proposes}\n\n## Motivation\n{Why this is needed, with concrete examples}\n\n## Detailed Design\n{How it works, with diagrams and code examples}\n\n## Drawbacks\n{Honest assessment of downsides}\n\n## Alternatives\n{What else was considered and why this approach wins}\n\n## Unresolved Questions\n{Open items for discussion}\n```\n\n## Writing Principles\n\n### Argument Structure\n\nEvery analytical section follows:\n\n1. **Claim** — What you're asserting\n2. **Evidence** — Data, metrics, code examples supporting the claim\n3. **Reasoning** — Why the evidence supports the claim\n4. **Implication** — What follows from this being true\n\n### Evidence Hierarchy\n\n| Strength | Evidence Type | Example |\n|----------|--------------|---------|\n| Strongest | Production metrics | \"P99 latency increased 3x after migration\" |\n| Strong | Reproducible test | \"Benchmark shows 40ms vs 120ms\" |\n| Moderate | Code analysis | \"This pattern creates N+1 queries\" |\n| Weak | Expert opinion | \"The team believes this will scale\" |\n| Weakest | Analogy | \"Netflix does it this way\" |\n\n### The Pyramid Principle\n\nLead with the conclusion, then support:\n\n**Bad:**\n> We analyzed the database, then the cache layer, then the API, and found that response times are slow because the cache hit rate is only 23%.\n\n**Good:**\n> Cache hit rate is 23%, causing slow response times. The database query layer generates cache keys inconsistently, leading to unnecessary misses. Standardizing key generation would bring hit rate to ~85%.\n\n## Structural Patterns\n\n### Problem-Solution-Evidence\n\n```markdown\n## {Problem Name}\n\n**Problem:** {specific, measurable issue}\n\n**Solution:** {proposed change}\n\n**Evidence:** {why this solution addresses the problem}\n\n**Effort:** {T-shirt size + key dependencies}\n```\n\n### Compare-Contrast Table\n\n```markdown\n| Criterion | Option A | Option B | Option C |\n|-----------|----------|----------|----------|\n| Performance | ★★★ | ★★ | ★★★ |\n| Complexity | Low | Medium | High |\n| Team familiarity | High | Low | Medium |\n| Maintenance cost | Low | High | Medium |\n| **Recommendation** | **✓** | | |\n```\n\n### Risk Matrix\n\n```markdown\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| API rate limiting | High | Medium | Client-side rate limiter + cache |\n| Data migration failure | Low | Critical | Rollback plan + dry-run first |\n| Team bandwidth | Medium | High | Phased rollout |\n```\n\n## Style Guidelines\n\n### Clarity\n\n- **Active voice:** \"The scheduler triggers the job\" not \"The job is triggered by the scheduler\"\n- **Concrete nouns:** \"The API returns a 429 status\" not \"There are issues with the API\"\n- **Specific numbers:** \"P99 latency is 230ms\" not \"Latency is high\"\n\n### Conciseness\n\n- Lead with the point, not the preamble\n- One idea per paragraph\n- Cut \"In order to\" → \"To\"\n- Cut \"It is important to note that\" → (just state it)\n- Cut \"As mentioned previously\" → (don't mention it)\n\n### Technical Accuracy\n\n- Verify all metrics and measurements\n- Include measurement methodology\n- Distinguish between observations and interpretations\n- Cite sources for external claims\n- Date all data (\"as of March 2026\")\n\n## Diagrams\n\n### When to Use Diagrams\n\n| Situation | Diagram Type |\n|-----------|-------------|\n| System components | Architecture diagram (boxes + arrows) |\n| Process flow | Flowchart or sequence diagram |\n| Data relationships | ER diagram |\n| Timeline | Gantt or timeline |\n| Hierarchy | Tree diagram |\n| Comparison | Table (not a diagram) |\n\n### Mermaid for Inline Diagrams\n\n````markdown\n```mermaid\ngraph LR\n    A[Client] --> B[API Gateway]\n    B --> C[Auth Service]\n    B --> D[Skills Service]\n    D --> E[(Database)]\n```\n````\n\n## Review Checklist\n\n- [ ] Executive summary is self-contained (reader gets the point without reading further)\n- [ ] Every claim has supporting evidence\n- [ ] Alternatives are fairly presented (not strawmen)\n- [ ] Risks and tradeoffs acknowledged honestly\n- [ ] Audience-appropriate level of detail\n- [ ] Diagrams have legends and labels\n- [ ] All acronyms defined on first use\n- [ ] Stranger test: a new team member can follow the argument\n\n## Anti-Patterns\n\n- **Burying the lead** — Put conclusions first, evidence after\n- **Appeal to authority** — \"Google does it\" is not an argument; explain why it works\n- **False precision** — \"This will improve performance by 47.3%\" without measurement methodology\n- **Missing alternatives** — Always compare at least 2-3 options\n- **Scope creep** — Stay focused on the stated question; flag tangents for separate docs\n- **No expiration date** — All analysis should include \"valid as of\" and conditions for revisiting\n",{"name":5,"tags":57,"license":15,"triggers":59,"complexity":65,"complements":66,"description":7,"time_to_learn":70,"organ_affinity":71,"governance_phases":73,"governance_norm_group":76},[41,37,58,45,49],"adr",[60,61,62,63,64],"user-asks-about-technical-writing","context:architecture-docs","context:adr","context:technical-analysis","context:decision-record","intermediate",[67,68,69],"doc-coauthoring","stranger-test-protocol","research-synthesis-workflow","30min",[72],"organ-v",[74,75],"shape","prove","documentation-standard","main","4d2fb89cdfb75f3f6fd3c6c5ec9ad90ea129eb3c","ai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Fdocumentation\u002Ftechnical-analytical-writing",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":86,"prompt":96,"zipAvailable":97},[87,90,93],{"tool":88,"command":89},"npx","npx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill technical-analytical-writing",{"tool":91,"command":92},"bunx","bunx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill technical-analytical-writing",{"tool":94,"command":95},"pnpm","pnpm dlx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill technical-analytical-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Fdocumentation\u002Ftechnical-analytical-writing\u002FSKILL.md",true,[],[100,124,141,168,201,236],{"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":52},"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",[],[36,107,108,109,110,111,112,113,114,44,115,116,117,118,43,119,120,121,122,123],"contracts","write contracts","storage","secure","create","generate","collection","model","ask","smart-contracts","selection","objects","nft","token","aptos","critical","move",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":52},"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",[],[131,132,133,134,135,136,137,138,139,140],"web","search","web search","搜索","baidu","bing","duckduckgo","百度","多引擎","internet",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":52},"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",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[151,152,153,154,51,155,156,157,132,158,159,160,36,161,162,163,164,165,166,167],"build","solo","solo build","MCP","commit","tasks","code","Bash","plan","read","auto","references","context7","query","scaffolding","ship it","project",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":180,"publishedAt":52},"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",[174,177],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":178,"categoryName":179,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200],"react","email","react email","github","editor","components","react components","component","welcome","https","notifications","password","node","use","html","resend","visual","emails","rendering","with",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":217,"publishedAt":52},"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",[207,210,213,214],{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":211,"categoryName":212,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":215,"categoryName":216,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师",[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":52},"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",[],[159,243,244,245,246,247,248,112,249,250,251,252,253,194,254,255,200,256],"implementation","hubspot","hubspot implementation plan","automation","feasibility","cleanup","planning","report","audit","audit report","phased implementation","dependencies","processes","hubspot audit"]