[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XF63CFQTATKCHWGJB6BC0H":3,"skill-same:01M6XF63CFQTATKCHWGJB6BC0H":65},{"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":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6XF63CFQTATKCHWGJB6BC0H","c4-code",null,"Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.","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\u002Fcopilot\u002Fc4-code\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"code","c4 code","documentation","create","expert","community","signatures","dependencies","structure","directories","unknown","documentation specialist","code structure","specialist","2026","2026-11-10 10:12:30",false,"---\nname: c4-code\ndescription: Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n# C4 Code Level: [Directory Name]\n\n## Use this skill when\n\n- Working on c4 code level: [directory name] tasks or workflows\n- Needing guidance, best practices, or checklists for c4 code level: [directory name]\n\n## Do not use this skill when\n\n- The task is unrelated to c4 code level: [directory name]\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Overview\n\n- **Name**: [Descriptive name for this code directory]\n- **Description**: [Short description of what this code does]\n- **Location**: [Link to actual directory path]\n- **Language**: [Primary programming language(s)]\n- **Purpose**: [What this code accomplishes]\n\n## Code Elements\n\n### Functions\u002FMethods\n\n- `functionName(param1: Type, param2: Type): ReturnType`\n  - Description: [What this function does]\n  - Location: [file path:line number]\n  - Dependencies: [what this function depends on]\n\n### Classes\u002FModules\n\n- `ClassName`\n  - Description: [What this class does]\n  - Location: [file path]\n  - Methods: [list of methods]\n  - Dependencies: [what this class depends on]\n\n## Dependencies\n\n### Internal Dependencies\n\n- [List of internal code dependencies]\n\n### External Dependencies\n\n- [List of external libraries, frameworks, services]\n\n## Relationships\n\nOptional Mermaid diagrams for complex code structures. Choose the diagram type based on the programming paradigm. Code diagrams show the **internal structure of a single component**.\n\n### Object-Oriented Code (Classes, Interfaces)\n\nUse `classDiagram` for OOP code with classes, interfaces, and inheritance:\n\n```mermaid\n---\ntitle: Code Diagram for [Component Name]\n---\nclassDiagram\n    namespace ComponentName {\n        class Class1 {\n            +attribute1 Type\n            +method1() ReturnType\n        }\n        class Class2 {\n            -privateAttr Type\n            +publicMethod() void\n        }\n        class Interface1 {\n            \u003C\u003Cinterface>>\n            +requiredMethod() ReturnType\n        }\n    }\n\n    Class1 ..|> Interface1 : implements\n    Class1 --> Class2 : uses\n```\n````\n\n### Functional\u002FProcedural Code (Modules, Functions)\n\nFor functional or procedural code, you have two options:\n\n**Option A: Module Structure Diagram** - Use `classDiagram` to show modules and their exported functions:\n\n```mermaid\n---\ntitle: Module Structure for [Component Name]\n---\nclassDiagram\n    namespace DataProcessing {\n        class validators {\n            \u003C\u003Cmodule>>\n            +validateInput(data) Result~Data, Error~\n            +validateSchema(schema, data) bool\n            +sanitize(input) string\n        }\n        class transformers {\n            \u003C\u003Cmodule>>\n            +parseJSON(raw) Record\n            +normalize(data) NormalizedData\n            +aggregate(items) Summary\n        }\n        class io {\n            \u003C\u003Cmodule>>\n            +readFile(path) string\n            +writeFile(path, content) void\n        }\n    }\n\n    transformers --> validators : uses\n    transformers --> io : reads from\n```\n\n**Option B: Data Flow Diagram** - Use `flowchart` to show function pipelines and data transformations:\n\n```mermaid\n---\ntitle: Data Pipeline for [Component Name]\n---\nflowchart LR\n    subgraph Input\n        A[readFile]\n    end\n    subgraph Transform\n        B[parseJSON]\n        C[validateInput]\n        D[normalize]\n        E[aggregate]\n    end\n    subgraph Output\n        F[writeFile]\n    end\n\n    A -->|raw string| B\n    B -->|parsed data| C\n    C -->|valid data| D\n    D -->|normalized| E\n    E -->|summary| F\n```\n\n**Option C: Function Dependency Graph** - Use `flowchart` to show which functions call which:\n\n```mermaid\n---\ntitle: Function Dependencies for [Component Name]\n---\nflowchart TB\n    subgraph Public API\n        processData[processData]\n        exportReport[exportReport]\n    end\n    subgraph Internal Functions\n        validate[validate]\n        transform[transform]\n        format[format]\n        cache[memoize]\n    end\n    subgraph Pure Utilities\n        compose[compose]\n        pipe[pipe]\n        curry[curry]\n    end\n\n    processData --> validate\n    processData --> transform\n    processData --> cache\n    transform --> compose\n    transform --> pipe\n    exportReport --> format\n    exportReport --> processData\n```\n\n### Choosing the Right Diagram\n\n| Code Style                       | Primary Diagram                  | When to Use                                             |\n| -------------------------------- | -------------------------------- | ------------------------------------------------------- |\n| OOP (classes, interfaces)        | `classDiagram`                   | Show inheritance, composition, interface implementation |\n| FP (pure functions, pipelines)   | `flowchart`                      | Show data transformations and function composition      |\n| FP (modules with exports)        | `classDiagram` with `\u003C\u003Cmodule>>` | Show module structure and dependencies                  |\n| Procedural (structs + functions) | `classDiagram`                   | Show data structures and associated functions           |\n| Mixed                            | Combination                      | Use multiple diagrams if needed                         |\n\n**Note**: According to the [C4 model](https:\u002F\u002Fc4model.com\u002Fdiagrams), code diagrams are typically only created when needed for complex components. Most teams find system context and container diagrams sufficient. Choose the diagram type that best communicates the code structure regardless of paradigm.\n\n## Notes\n\n[Any additional context or important information]\n\n```\n\n## Example Interactions\n\n### Object-Oriented Codebases\n- \"Analyze the src\u002Fapi directory and create C4 Code-level documentation\"\n- \"Document the service layer code with complete class hierarchies and dependencies\"\n- \"Create C4 Code documentation showing interface implementations in the repository layer\"\n\n### Functional\u002FProcedural Codebases\n- \"Document all functions in the authentication module with their signatures and data flow\"\n- \"Create a data pipeline diagram for the ETL transformers in src\u002Fpipeline\"\n- \"Analyze the utils directory and document all pure functions and their composition patterns\"\n- \"Document the Rust modules in src\u002Fhandlers showing function dependencies\"\n- \"Create C4 Code documentation for the Elixir GenServer modules\"\n\n### Mixed Paradigm\n- \"Document the Go handlers package showing structs and their associated functions\"\n- \"Analyze the TypeScript codebase that mixes classes with functional utilities\"\n\n## Key Distinctions\n- **vs C4-Component agent**: Focuses on individual code elements; Component agent synthesizes multiple code files into components\n- **vs C4-Container agent**: Documents code structure; Container agent maps components to deployment units\n- **vs C4-Context agent**: Provides code-level detail; Context agent creates high-level system diagrams\n\n## Output Examples\nWhen analyzing code, provide:\n- Complete function\u002Fmethod signatures with all parameters and return types\n- Clear descriptions of what each code element does\n- Links to actual source code locations\n- Complete dependency lists (internal and external)\n- Structured documentation following C4 Code-level template\n- Mermaid diagrams for complex code relationships when needed\n- Consistent naming and formatting across all code documentation\n\n```\n","# C4 Code Level: [Directory Name]\n\n## Use this skill when\n\n- Working on c4 code level: [directory name] tasks or workflows\n- Needing guidance, best practices, or checklists for c4 code level: [directory name]\n\n## Do not use this skill when\n\n- The task is unrelated to c4 code level: [directory name]\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\n## Overview\n\n- **Name**: [Descriptive name for this code directory]\n- **Description**: [Short description of what this code does]\n- **Location**: [Link to actual directory path]\n- **Language**: [Primary programming language(s)]\n- **Purpose**: [What this code accomplishes]\n\n## Code Elements\n\n### Functions\u002FMethods\n\n- `functionName(param1: Type, param2: Type): ReturnType`\n  - Description: [What this function does]\n  - Location: [file path:line number]\n  - Dependencies: [what this function depends on]\n\n### Classes\u002FModules\n\n- `ClassName`\n  - Description: [What this class does]\n  - Location: [file path]\n  - Methods: [list of methods]\n  - Dependencies: [what this class depends on]\n\n## Dependencies\n\n### Internal Dependencies\n\n- [List of internal code dependencies]\n\n### External Dependencies\n\n- [List of external libraries, frameworks, services]\n\n## Relationships\n\nOptional Mermaid diagrams for complex code structures. Choose the diagram type based on the programming paradigm. Code diagrams show the **internal structure of a single component**.\n\n### Object-Oriented Code (Classes, Interfaces)\n\nUse `classDiagram` for OOP code with classes, interfaces, and inheritance:\n\n```mermaid\n---\ntitle: Code Diagram for [Component Name]\n---\nclassDiagram\n    namespace ComponentName {\n        class Class1 {\n            +attribute1 Type\n            +method1() ReturnType\n        }\n        class Class2 {\n            -privateAttr Type\n            +publicMethod() void\n        }\n        class Interface1 {\n            \u003C\u003Cinterface>>\n            +requiredMethod() ReturnType\n        }\n    }\n\n    Class1 ..|> Interface1 : implements\n    Class1 --> Class2 : uses\n```\n````\n\n### Functional\u002FProcedural Code (Modules, Functions)\n\nFor functional or procedural code, you have two options:\n\n**Option A: Module Structure Diagram** - Use `classDiagram` to show modules and their exported functions:\n\n```mermaid\n---\ntitle: Module Structure for [Component Name]\n---\nclassDiagram\n    namespace DataProcessing {\n        class validators {\n            \u003C\u003Cmodule>>\n            +validateInput(data) Result~Data, Error~\n            +validateSchema(schema, data) bool\n            +sanitize(input) string\n        }\n        class transformers {\n            \u003C\u003Cmodule>>\n            +parseJSON(raw) Record\n            +normalize(data) NormalizedData\n            +aggregate(items) Summary\n        }\n        class io {\n            \u003C\u003Cmodule>>\n            +readFile(path) string\n            +writeFile(path, content) void\n        }\n    }\n\n    transformers --> validators : uses\n    transformers --> io : reads from\n```\n\n**Option B: Data Flow Diagram** - Use `flowchart` to show function pipelines and data transformations:\n\n```mermaid\n---\ntitle: Data Pipeline for [Component Name]\n---\nflowchart LR\n    subgraph Input\n        A[readFile]\n    end\n    subgraph Transform\n        B[parseJSON]\n        C[validateInput]\n        D[normalize]\n        E[aggregate]\n    end\n    subgraph Output\n        F[writeFile]\n    end\n\n    A -->|raw string| B\n    B -->|parsed data| C\n    C -->|valid data| D\n    D -->|normalized| E\n    E -->|summary| F\n```\n\n**Option C: Function Dependency Graph** - Use `flowchart` to show which functions call which:\n\n```mermaid\n---\ntitle: Function Dependencies for [Component Name]\n---\nflowchart TB\n    subgraph Public API\n        processData[processData]\n        exportReport[exportReport]\n    end\n    subgraph Internal Functions\n        validate[validate]\n        transform[transform]\n        format[format]\n        cache[memoize]\n    end\n    subgraph Pure Utilities\n        compose[compose]\n        pipe[pipe]\n        curry[curry]\n    end\n\n    processData --> validate\n    processData --> transform\n    processData --> cache\n    transform --> compose\n    transform --> pipe\n    exportReport --> format\n    exportReport --> processData\n```\n\n### Choosing the Right Diagram\n\n| Code Style                       | Primary Diagram                  | When to Use                                             |\n| -------------------------------- | -------------------------------- | ------------------------------------------------------- |\n| OOP (classes, interfaces)        | `classDiagram`                   | Show inheritance, composition, interface implementation |\n| FP (pure functions, pipelines)   | `flowchart`                      | Show data transformations and function composition      |\n| FP (modules with exports)        | `classDiagram` with `\u003C\u003Cmodule>>` | Show module structure and dependencies                  |\n| Procedural (structs + functions) | `classDiagram`                   | Show data structures and associated functions           |\n| Mixed                            | Combination                      | Use multiple diagrams if needed                         |\n\n**Note**: According to the [C4 model](https:\u002F\u002Fc4model.com\u002Fdiagrams), code diagrams are typically only created when needed for complex components. Most teams find system context and container diagrams sufficient. Choose the diagram type that best communicates the code structure regardless of paradigm.\n\n## Notes\n\n[Any additional context or important information]\n\n```\n\n## Example Interactions\n\n### Object-Oriented Codebases\n- \"Analyze the src\u002Fapi directory and create C4 Code-level documentation\"\n- \"Document the service layer code with complete class hierarchies and dependencies\"\n- \"Create C4 Code documentation showing interface implementations in the repository layer\"\n\n### Functional\u002FProcedural Codebases\n- \"Document all functions in the authentication module with their signatures and data flow\"\n- \"Create a data pipeline diagram for the ETL transformers in src\u002Fpipeline\"\n- \"Analyze the utils directory and document all pure functions and their composition patterns\"\n- \"Document the Rust modules in src\u002Fhandlers showing function dependencies\"\n- \"Create C4 Code documentation for the Elixir GenServer modules\"\n\n### Mixed Paradigm\n- \"Document the Go handlers package showing structs and their associated functions\"\n- \"Analyze the TypeScript codebase that mixes classes with functional utilities\"\n\n## Key Distinctions\n- **vs C4-Component agent**: Focuses on individual code elements; Component agent synthesizes multiple code files into components\n- **vs C4-Container agent**: Documents code structure; Container agent maps components to deployment units\n- **vs C4-Context agent**: Provides code-level detail; Context agent creates high-level system diagrams\n\n## Output Examples\nWhen analyzing code, provide:\n- Complete function\u002Fmethod signatures with all parameters and return types\n- Clear descriptions of what each code element does\n- Links to actual source code locations\n- Complete dependency lists (internal and external)\n- Structured documentation following C4 Code-level template\n- Mermaid diagrams for complex code relationships when needed\n- Consistent naming and formatting across all code documentation\n\n```\n",{"name":5,"risk":34,"source":29,"date_added":44,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcopilot\u002Fc4-code","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill c4-code",{"tool":57,"command":58},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill c4-code",{"tool":60,"command":61},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill c4-code","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fc4-code\u002FSKILL.md",true,[],[66,88,114,124,137,156],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":75,"publishedAt":39},"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",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[76,77,78,79,80,81,82,83,84,85,86,87],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":39},"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",[],[95,96,97,98,99,100,78,101,102,103,104,105,106,107,108,109,110,111,112,113],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":39},"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",[],[121,122,95,106,107,108,109,99,78,111,123,112,113,105,103,102,101,110,100,98],"trend radar","radar","pulse",{"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":39},"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",[],[131,132,133,134,135,136],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":148,"publishedAt":39},"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",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[139,84,149,150,151,87,106,152,153,154,97,155,110],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":39},"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",[],[158,163,164,165,110,166,153,167,168,169,170,171],"status","play","go","latest","github","discover","control","cmd","volume"]