[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78B4D4G1FDVF8K2Y4GTS09J":3,"skill-same:01M78B4D4G1FDVF8K2Y4GTS09J":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M78B4D4G1FDVF8K2Y4GTS09J","c4-context",null,"Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fc4-context\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: c4-context\ndescription: Expert C4 Context-level documentation specialist. Creates high-level system context diagrams, documents personas, user journeys, system features, and external dependencies.\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n# C4 Context Level: System Context\n\n## Use this skill when\n\n- Working on c4 context level: system context tasks or workflows\n- Needing guidance, best practices, or checklists for c4 context level: system context\n\n## Do not use this skill when\n\n- The task is unrelated to c4 context level: system context\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## System Overview\n\n### Short Description\n\n[One-sentence description of what the system does]\n\n### Long Description\n\n[Detailed description of the system's purpose, capabilities, and the problems it solves]\n\n## Personas\n\n### [Persona Name]\n\n- **Type**: [Human User \u002F Programmatic User \u002F External System]\n- **Description**: [Who this persona is and what they need]\n- **Goals**: [What this persona wants to achieve]\n- **Key Features Used**: [List of features this persona uses]\n\n## System Features\n\n### [Feature Name]\n\n- **Description**: [What this feature does]\n- **Users**: [Which personas use this feature]\n- **User Journey**: [Link to user journey map]\n\n## User Journeys\n\n### [Feature Name] - [Persona Name] Journey\n\n1. [Step 1]: [Description]\n2. [Step 2]: [Description]\n3. [Step 3]: [Description]\n   ...\n\n### [External System] Integration Journey\n\n1. [Step 1]: [Description]\n2. [Step 2]: [Description]\n   ...\n\n## External Systems and Dependencies\n\n### [External System Name]\n\n- **Type**: [Database, API, Service, Message Queue, etc.]\n- **Description**: [What this external system provides]\n- **Integration Type**: [API, Events, File Transfer, etc.]\n- **Purpose**: [Why the system depends on this]\n\n## System Context Diagram\n\n[Mermaid diagram showing system, users, and external systems]\n\n## Related Documentation\n\n- Container Documentation\n- Component Documentation\n```\n\n## Context Diagram Template\n\nAccording to the [C4 model](https:\u002F\u002Fc4model.com\u002Fdiagrams\u002Fsystem-context), a System Context diagram shows the system as a box in the center, surrounded by its users and the other systems that it interacts with. The focus is on **people (actors, roles, personas) and software systems** rather than technologies, protocols, and other low-level details.\n\nUse proper Mermaid C4 syntax:\n\n```mermaid\nC4Context\n    title System Context Diagram\n\n    Person(user, \"User\", \"Uses the system to accomplish their goals\")\n    System(system, \"System Name\", \"Provides features X, Y, and Z\")\n    System_Ext(external1, \"External System 1\", \"Provides service A\")\n    System_Ext(external2, \"External System 2\", \"Provides service B\")\n    SystemDb(externalDb, \"External Database\", \"Stores data\")\n\n    Rel(user, system, \"Uses\")\n    Rel(system, external1, \"Uses\", \"API\")\n    Rel(system, external2, \"Sends events to\")\n    Rel(system, externalDb, \"Reads from and writes to\")\n```\n\n**Key Principles** (from [c4model.com](https:\u002F\u002Fc4model.com\u002Fdiagrams\u002Fsystem-context)):\n\n- Focus on **people and software systems**, not technologies\n- Show the **system boundary** clearly\n- Include all **users** (human and programmatic)\n- Include all **external systems** the system interacts with\n- Keep it **stakeholder-friendly** - understandable by non-technical audiences\n- Avoid showing technologies, protocols, or low-level details\n\n## Example Interactions\n\n- \"Create C4 Context-level documentation for the system\"\n- \"Identify all personas and create user journey maps for key features\"\n- \"Document external systems and create a system context diagram\"\n- \"Analyze system documentation and create comprehensive context documentation\"\n- \"Map user journeys for all key features including programmatic users\"\n\n## Key Distinctions\n\n- **vs C4-Container agent**: Provides high-level system view; Container agent focuses on deployment architecture\n- **vs C4-Component agent**: Focuses on system context; Component agent focuses on logical component structure\n- **vs C4-Code agent**: Provides stakeholder-friendly overview; Code agent provides technical code details\n\n## Output Examples\n\nWhen creating context documentation, provide:\n\n- Clear system descriptions (short and long)\n- Comprehensive persona documentation (human and programmatic)\n- Complete feature lists with descriptions\n- Detailed user journey maps for all key features\n- Complete external system and dependency documentation\n- Mermaid context diagram showing system, users, and external systems\n- Links to container and component documentation\n- Stakeholder-friendly documentation understandable by non-technical audiences\n- Consistent documentation format\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# C4 Context Level: System Context\n\n## Use this skill when\n\n- Working on c4 context level: system context tasks or workflows\n- Needing guidance, best practices, or checklists for c4 context level: system context\n\n## Do not use this skill when\n\n- The task is unrelated to c4 context level: system context\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## System Overview\n\n### Short Description\n\n[One-sentence description of what the system does]\n\n### Long Description\n\n[Detailed description of the system's purpose, capabilities, and the problems it solves]\n\n## Personas\n\n### [Persona Name]\n\n- **Type**: [Human User \u002F Programmatic User \u002F External System]\n- **Description**: [Who this persona is and what they need]\n- **Goals**: [What this persona wants to achieve]\n- **Key Features Used**: [List of features this persona uses]\n\n## System Features\n\n### [Feature Name]\n\n- **Description**: [What this feature does]\n- **Users**: [Which personas use this feature]\n- **User Journey**: [Link to user journey map]\n\n## User Journeys\n\n### [Feature Name] - [Persona Name] Journey\n\n1. [Step 1]: [Description]\n2. [Step 2]: [Description]\n3. [Step 3]: [Description]\n   ...\n\n### [External System] Integration Journey\n\n1. [Step 1]: [Description]\n2. [Step 2]: [Description]\n   ...\n\n## External Systems and Dependencies\n\n### [External System Name]\n\n- **Type**: [Database, API, Service, Message Queue, etc.]\n- **Description**: [What this external system provides]\n- **Integration Type**: [API, Events, File Transfer, etc.]\n- **Purpose**: [Why the system depends on this]\n\n## System Context Diagram\n\n[Mermaid diagram showing system, users, and external systems]\n\n## Related Documentation\n\n- Container Documentation\n- Component Documentation\n```\n\n## Context Diagram Template\n\nAccording to the [C4 model](https:\u002F\u002Fc4model.com\u002Fdiagrams\u002Fsystem-context), a System Context diagram shows the system as a box in the center, surrounded by its users and the other systems that it interacts with. The focus is on **people (actors, roles, personas) and software systems** rather than technologies, protocols, and other low-level details.\n\nUse proper Mermaid C4 syntax:\n\n```mermaid\nC4Context\n    title System Context Diagram\n\n    Person(user, \"User\", \"Uses the system to accomplish their goals\")\n    System(system, \"System Name\", \"Provides features X, Y, and Z\")\n    System_Ext(external1, \"External System 1\", \"Provides service A\")\n    System_Ext(external2, \"External System 2\", \"Provides service B\")\n    SystemDb(externalDb, \"External Database\", \"Stores data\")\n\n    Rel(user, system, \"Uses\")\n    Rel(system, external1, \"Uses\", \"API\")\n    Rel(system, external2, \"Sends events to\")\n    Rel(system, externalDb, \"Reads from and writes to\")\n```\n\n**Key Principles** (from [c4model.com](https:\u002F\u002Fc4model.com\u002Fdiagrams\u002Fsystem-context)):\n\n- Focus on **people and software systems**, not technologies\n- Show the **system boundary** clearly\n- Include all **users** (human and programmatic)\n- Include all **external systems** the system interacts with\n- Keep it **stakeholder-friendly** - understandable by non-technical audiences\n- Avoid showing technologies, protocols, or low-level details\n\n## Example Interactions\n\n- \"Create C4 Context-level documentation for the system\"\n- \"Identify all personas and create user journey maps for key features\"\n- \"Document external systems and create a system context diagram\"\n- \"Analyze system documentation and create comprehensive context documentation\"\n- \"Map user journeys for all key features including programmatic users\"\n\n## Key Distinctions\n\n- **vs C4-Container agent**: Provides high-level system view; Container agent focuses on deployment architecture\n- **vs C4-Component agent**: Focuses on system context; Component agent focuses on logical component structure\n- **vs C4-Code agent**: Provides stakeholder-friendly overview; Code agent provides technical code details\n\n## Output Examples\n\nWhen creating context documentation, provide:\n\n- Clear system descriptions (short and long)\n- Comprehensive persona documentation (human and programmatic)\n- Complete feature lists with descriptions\n- Detailed user journey maps for all key features\n- Complete external system and dependency documentation\n- Mermaid context diagram showing system, users, and external systems\n- Links to container and component documentation\n- Stakeholder-friendly documentation understandable by non-technical audiences\n- Consistent documentation format\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"unknown","community","2026-02-27","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fc4-context","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill c4-context",{"tool":40,"command":41},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill c4-context",{"tool":43,"command":44},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill c4-context","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fc4-context\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]