[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DDWFVD778YFZ97MN7E5CYP":3,"skill-same:01M6DDWFVD778YFZ97MN7E5CYP":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6DDWFVD778YFZ97MN7E5CYP","c4-architecture",null,"Use when asked to create architecture diagrams, document system architecture, visualize software structure, or generate context\u002Fcontainer\u002Fcomponent\u002Fdeployment diagrams — produces C4 model Mermaid diagrams written to docs\u002Farchitecture\u002F.","Prekzursil\u002Fagent-skills-toolchain","Prekzursil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54636077?v=4","01M6DACZ1PCQHD99SCR1YXG28B","Andrei Mihai Visalon","01M6DACZ670WZF535V3WYYSS4Z",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Fskills\u002Fc4-architecture\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"architecture","c4 architecture","generate","software","structure","c4 model","document","diagrams","container","use","model","system","mermaid diagrams","create","deployment","architecture diagrams","mermaid","component","visualize","docs","2026-11-10 10:12:30",false,"---\nname: c4-architecture\ndescription: Use when asked to create architecture diagrams, document system architecture, visualize software structure, or generate context\u002Fcontainer\u002Fcomponent\u002Fdeployment diagrams — produces C4 model Mermaid diagrams written to docs\u002Farchitecture\u002F.\n---\n\n\u003C!-- Source: cherry-picked from https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco (skills\u002Fc4-architecture) on 27.08.2026 per grill decision G-11\u002F11B. Adapted to house format; coco reference files not ported. -->\n\n# C4 Architecture Documentation\n\nGenerate architecture documentation using C4 model Mermaid diagrams. Triggers include \"architecture diagram\", \"C4 diagram\", \"system context\", \"container diagram\", \"component diagram\", \"deployment diagram\", \"document architecture\", \"visualize architecture\".\n\n## Workflow\n\n1. **Understand scope** — Determine which C4 level(s) are needed based on audience\n2. **Analyze codebase** — Explore the system to identify components, containers, and relationships\n3. **Generate diagrams** — Create Mermaid C4 diagrams at appropriate abstraction levels\n4. **Document** — Write diagrams to markdown files with explanatory context\n\n## C4 Diagram Levels\n\n| Level | Diagram Type | Audience | Shows | When to Create |\n|-------|-------------|----------|-------|----------------|\n| 1 | **C4Context** | Everyone | System + external actors | Always (required) |\n| 2 | **C4Container** | Technical | Apps, databases, services | Always (required) |\n| 3 | **C4Component** | Developers | Internal components | Only if adds value |\n| 4 | **C4Deployment** | DevOps | Infrastructure nodes | For production systems |\n| - | **C4Dynamic** | Technical | Request flows (numbered) | For complex workflows |\n\n**Key insight:** Context + Container diagrams are sufficient for most software development teams. Only create Component\u002FCode diagrams when they genuinely add value.\n\n## Quick Start Examples\n\n### System Context (Level 1)\n\n```mermaid\nC4Context\n  title System Context - Workout Tracker\n\n  Person(user, \"User\", \"Tracks workouts and exercises\")\n  System(app, \"Workout Tracker\", \"Vue PWA for tracking strength and CrossFit workouts\")\n  System_Ext(browser, \"Web Browser\", \"Stores data in IndexedDB\")\n\n  Rel(user, app, \"Uses\")\n  Rel(app, browser, \"Persists data to\", \"IndexedDB\")\n```\n\n### Container Diagram (Level 2)\n\n```mermaid\nC4Container\n  title Container Diagram - Workout Tracker\n\n  Person(user, \"User\", \"Tracks workouts\")\n\n  Container_Boundary(app, \"Workout Tracker PWA\") {\n    Container(spa, \"SPA\", \"Vue 3, TypeScript\", \"Single-page application\")\n    Container(pinia, \"State Management\", \"Pinia\", \"Manages application state\")\n    ContainerDb(indexeddb, \"IndexedDB\", \"Dexie\", \"Local workout storage\")\n  }\n\n  Rel(user, spa, \"Uses\")\n  Rel(spa, pinia, \"Reads\u002Fwrites state\")\n  Rel(pinia, indexeddb, \"Persists\", \"Dexie ORM\")\n```\n\n### Dynamic Diagram (Request Flow)\n\n```mermaid\nC4Dynamic\n  title Dynamic Diagram - User Sign In Flow\n\n  ContainerDb(db, \"Database\", \"PostgreSQL\", \"User credentials\")\n  Container(spa, \"Single-Page App\", \"React\", \"Banking UI\")\n\n  Container_Boundary(api, \"API Application\") {\n    Component(signIn, \"Sign In Controller\", \"Express\", \"Auth endpoint\")\n    Component(security, \"Security Service\", \"JWT\", \"Validates credentials\")\n  }\n\n  Rel(spa, signIn, \"1. Submit credentials\", \"JSON\u002FHTTPS\")\n  Rel(signIn, security, \"2. Validate\")\n  Rel(security, db, \"3. Query user\", \"SQL\")\n\n  UpdateRelStyle(spa, signIn, $textColor=\"blue\", $offsetY=\"-30\")\n```\n\n### Deployment Diagram\n\n```mermaid\nC4Deployment\n  title Deployment Diagram - Production\n\n  Deployment_Node(browser, \"Customer Browser\", \"Chrome\u002FFirefox\") {\n    Container(spa, \"SPA\", \"React\", \"Web application\")\n  }\n\n  Deployment_Node(aws, \"AWS Cloud\", \"us-east-1\") {\n    Deployment_Node(ecs, \"ECS Cluster\", \"Fargate\") {\n      Container(api, \"API Service\", \"Node.js\", \"REST API\")\n    }\n    Deployment_Node(rds, \"RDS\", \"db.r5.large\") {\n      ContainerDb(db, \"Database\", \"PostgreSQL\", \"Application data\")\n    }\n  }\n\n  Rel(spa, api, \"API calls\", \"HTTPS\")\n  Rel(api, db, \"Reads\u002Fwrites\", \"JDBC\")\n```\n\n## Element Syntax\n\n### People and Systems\n\n```\nPerson(alias, \"Label\", \"Description\")\nPerson_Ext(alias, \"Label\", \"Description\")       # External person\nSystem(alias, \"Label\", \"Description\")\nSystem_Ext(alias, \"Label\", \"Description\")       # External system\nSystemDb(alias, \"Label\", \"Description\")         # Database system\nSystemQueue(alias, \"Label\", \"Description\")      # Queue system\n```\n\n### Containers and Components\n\n```\nContainer(alias, \"Label\", \"Technology\", \"Description\")\nContainer_Ext(alias, \"Label\", \"Technology\", \"Description\")\nContainerDb(alias, \"Label\", \"Technology\", \"Description\")\nContainerQueue(alias, \"Label\", \"Technology\", \"Description\")\nComponent(alias, \"Label\", \"Technology\", \"Description\")\nComponent_Ext(alias, \"Label\", \"Technology\", \"Description\")\nComponentDb(alias, \"Label\", \"Technology\", \"Description\")\n```\n\n### Boundaries\n\n```\nEnterprise_Boundary(alias, \"Label\") { ... }\nSystem_Boundary(alias, \"Label\") { ... }\nContainer_Boundary(alias, \"Label\") { ... }\nBoundary(alias, \"Label\", \"type\") { ... }\n```\n\n### Relationships\n\n```\nRel(from, to, \"Label\")\nRel(from, to, \"Label\", \"Technology\")\nBiRel(from, to, \"Label\")                        # Bidirectional (avoid; prefer unidirectional)\nRel_U \u002F Rel_D \u002F Rel_L \u002F Rel_R(from, to, \"Label\") # Direction hints\n```\n\n### Deployment Nodes\n\n```\nDeployment_Node(alias, \"Label\", \"Type\", \"Description\") { ... }\nNode(alias, \"Label\", \"Type\", \"Description\") { ... }  # Shorthand\n```\n\n## Styling and Layout\n\n```\nUpdateLayoutConfig($c4ShapeInRow=\"3\", $c4BoundaryInRow=\"1\")\nUpdateElementStyle(alias, $fontColor=\"red\", $bgColor=\"grey\", $borderColor=\"red\")\nUpdateRelStyle(from, to, $textColor=\"blue\", $lineColor=\"blue\", $offsetX=\"5\", $offsetY=\"-10\")\n```\n\nUse `$offsetX`\u002F`$offsetY` to fix overlapping relationship labels.\n\n## Best Practices\n\n1. **Every element must have**: Name, Type, Technology (where applicable), and Description\n2. **Use unidirectional arrows only** — bidirectional arrows create ambiguity\n3. **Label arrows with action verbs** — \"Sends email using\", \"Reads from\", not just \"uses\"\n4. **Include technology labels** — \"JSON\u002FHTTPS\", \"JDBC\", \"gRPC\"\n5. **Stay under 20 elements per diagram** — split complex systems into multiple diagrams\n6. **Start at Level 1**; one diagram per file; meaningful aliases (`orderService` not `s1`); concise descriptions; always include a title\n\n### What to Avoid\n\n- Confusing containers (deployable) vs components (non-deployable)\n- Modeling shared libraries as containers\n- Showing message brokers as a single container instead of individual topics\u002Fqueues\n- Adding undefined abstraction levels like \"subcomponents\"\n- Removing type labels to \"simplify\" diagrams\n\n## Microservices Guidelines\n\n- **Single team ownership:** model each microservice as a **container** (or container group) inside one `System_Boundary`.\n- **Multi-team ownership:** promote microservices to **software systems** in a Context diagram.\n- **Event-driven:** show individual topics\u002Fqueues as `ContainerQueue` elements (e.g. `order.created`), NOT a single \"Kafka\" box.\n\n## Output Location\n\nWrite architecture documentation to `docs\u002Farchitecture\u002F`:\n\n- `c4-context.md` — System context diagram\n- `c4-containers.md` — Container diagram\n- `c4-components-{feature}.md` — Component diagrams per feature\n- `c4-deployment.md` — Deployment diagram\n- `c4-dynamic-{flow}.md` — Dynamic diagrams for specific flows\n\n## Audience-Appropriate Detail\n\n| Audience | Recommended Diagrams |\n|----------|---------------------|\n| Executives | System Context only |\n| Product Managers | Context + Container |\n| Architects | Context + Container + key Components |\n| Developers | All levels as needed |\n| DevOps | Container + Deployment |\n","\u003C!-- Source: cherry-picked from https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco (skills\u002Fc4-architecture) on 27.08.2026 per grill decision G-11\u002F11B. Adapted to house format; coco reference files not ported. -->\n\n# C4 Architecture Documentation\n\nGenerate architecture documentation using C4 model Mermaid diagrams. Triggers include \"architecture diagram\", \"C4 diagram\", \"system context\", \"container diagram\", \"component diagram\", \"deployment diagram\", \"document architecture\", \"visualize architecture\".\n\n## Workflow\n\n1. **Understand scope** — Determine which C4 level(s) are needed based on audience\n2. **Analyze codebase** — Explore the system to identify components, containers, and relationships\n3. **Generate diagrams** — Create Mermaid C4 diagrams at appropriate abstraction levels\n4. **Document** — Write diagrams to markdown files with explanatory context\n\n## C4 Diagram Levels\n\n| Level | Diagram Type | Audience | Shows | When to Create |\n|-------|-------------|----------|-------|----------------|\n| 1 | **C4Context** | Everyone | System + external actors | Always (required) |\n| 2 | **C4Container** | Technical | Apps, databases, services | Always (required) |\n| 3 | **C4Component** | Developers | Internal components | Only if adds value |\n| 4 | **C4Deployment** | DevOps | Infrastructure nodes | For production systems |\n| - | **C4Dynamic** | Technical | Request flows (numbered) | For complex workflows |\n\n**Key insight:** Context + Container diagrams are sufficient for most software development teams. Only create Component\u002FCode diagrams when they genuinely add value.\n\n## Quick Start Examples\n\n### System Context (Level 1)\n\n```mermaid\nC4Context\n  title System Context - Workout Tracker\n\n  Person(user, \"User\", \"Tracks workouts and exercises\")\n  System(app, \"Workout Tracker\", \"Vue PWA for tracking strength and CrossFit workouts\")\n  System_Ext(browser, \"Web Browser\", \"Stores data in IndexedDB\")\n\n  Rel(user, app, \"Uses\")\n  Rel(app, browser, \"Persists data to\", \"IndexedDB\")\n```\n\n### Container Diagram (Level 2)\n\n```mermaid\nC4Container\n  title Container Diagram - Workout Tracker\n\n  Person(user, \"User\", \"Tracks workouts\")\n\n  Container_Boundary(app, \"Workout Tracker PWA\") {\n    Container(spa, \"SPA\", \"Vue 3, TypeScript\", \"Single-page application\")\n    Container(pinia, \"State Management\", \"Pinia\", \"Manages application state\")\n    ContainerDb(indexeddb, \"IndexedDB\", \"Dexie\", \"Local workout storage\")\n  }\n\n  Rel(user, spa, \"Uses\")\n  Rel(spa, pinia, \"Reads\u002Fwrites state\")\n  Rel(pinia, indexeddb, \"Persists\", \"Dexie ORM\")\n```\n\n### Dynamic Diagram (Request Flow)\n\n```mermaid\nC4Dynamic\n  title Dynamic Diagram - User Sign In Flow\n\n  ContainerDb(db, \"Database\", \"PostgreSQL\", \"User credentials\")\n  Container(spa, \"Single-Page App\", \"React\", \"Banking UI\")\n\n  Container_Boundary(api, \"API Application\") {\n    Component(signIn, \"Sign In Controller\", \"Express\", \"Auth endpoint\")\n    Component(security, \"Security Service\", \"JWT\", \"Validates credentials\")\n  }\n\n  Rel(spa, signIn, \"1. Submit credentials\", \"JSON\u002FHTTPS\")\n  Rel(signIn, security, \"2. Validate\")\n  Rel(security, db, \"3. Query user\", \"SQL\")\n\n  UpdateRelStyle(spa, signIn, $textColor=\"blue\", $offsetY=\"-30\")\n```\n\n### Deployment Diagram\n\n```mermaid\nC4Deployment\n  title Deployment Diagram - Production\n\n  Deployment_Node(browser, \"Customer Browser\", \"Chrome\u002FFirefox\") {\n    Container(spa, \"SPA\", \"React\", \"Web application\")\n  }\n\n  Deployment_Node(aws, \"AWS Cloud\", \"us-east-1\") {\n    Deployment_Node(ecs, \"ECS Cluster\", \"Fargate\") {\n      Container(api, \"API Service\", \"Node.js\", \"REST API\")\n    }\n    Deployment_Node(rds, \"RDS\", \"db.r5.large\") {\n      ContainerDb(db, \"Database\", \"PostgreSQL\", \"Application data\")\n    }\n  }\n\n  Rel(spa, api, \"API calls\", \"HTTPS\")\n  Rel(api, db, \"Reads\u002Fwrites\", \"JDBC\")\n```\n\n## Element Syntax\n\n### People and Systems\n\n```\nPerson(alias, \"Label\", \"Description\")\nPerson_Ext(alias, \"Label\", \"Description\")       # External person\nSystem(alias, \"Label\", \"Description\")\nSystem_Ext(alias, \"Label\", \"Description\")       # External system\nSystemDb(alias, \"Label\", \"Description\")         # Database system\nSystemQueue(alias, \"Label\", \"Description\")      # Queue system\n```\n\n### Containers and Components\n\n```\nContainer(alias, \"Label\", \"Technology\", \"Description\")\nContainer_Ext(alias, \"Label\", \"Technology\", \"Description\")\nContainerDb(alias, \"Label\", \"Technology\", \"Description\")\nContainerQueue(alias, \"Label\", \"Technology\", \"Description\")\nComponent(alias, \"Label\", \"Technology\", \"Description\")\nComponent_Ext(alias, \"Label\", \"Technology\", \"Description\")\nComponentDb(alias, \"Label\", \"Technology\", \"Description\")\n```\n\n### Boundaries\n\n```\nEnterprise_Boundary(alias, \"Label\") { ... }\nSystem_Boundary(alias, \"Label\") { ... }\nContainer_Boundary(alias, \"Label\") { ... }\nBoundary(alias, \"Label\", \"type\") { ... }\n```\n\n### Relationships\n\n```\nRel(from, to, \"Label\")\nRel(from, to, \"Label\", \"Technology\")\nBiRel(from, to, \"Label\")                        # Bidirectional (avoid; prefer unidirectional)\nRel_U \u002F Rel_D \u002F Rel_L \u002F Rel_R(from, to, \"Label\") # Direction hints\n```\n\n### Deployment Nodes\n\n```\nDeployment_Node(alias, \"Label\", \"Type\", \"Description\") { ... }\nNode(alias, \"Label\", \"Type\", \"Description\") { ... }  # Shorthand\n```\n\n## Styling and Layout\n\n```\nUpdateLayoutConfig($c4ShapeInRow=\"3\", $c4BoundaryInRow=\"1\")\nUpdateElementStyle(alias, $fontColor=\"red\", $bgColor=\"grey\", $borderColor=\"red\")\nUpdateRelStyle(from, to, $textColor=\"blue\", $lineColor=\"blue\", $offsetX=\"5\", $offsetY=\"-10\")\n```\n\nUse `$offsetX`\u002F`$offsetY` to fix overlapping relationship labels.\n\n## Best Practices\n\n1. **Every element must have**: Name, Type, Technology (where applicable), and Description\n2. **Use unidirectional arrows only** — bidirectional arrows create ambiguity\n3. **Label arrows with action verbs** — \"Sends email using\", \"Reads from\", not just \"uses\"\n4. **Include technology labels** — \"JSON\u002FHTTPS\", \"JDBC\", \"gRPC\"\n5. **Stay under 20 elements per diagram** — split complex systems into multiple diagrams\n6. **Start at Level 1**; one diagram per file; meaningful aliases (`orderService` not `s1`); concise descriptions; always include a title\n\n### What to Avoid\n\n- Confusing containers (deployable) vs components (non-deployable)\n- Modeling shared libraries as containers\n- Showing message brokers as a single container instead of individual topics\u002Fqueues\n- Adding undefined abstraction levels like \"subcomponents\"\n- Removing type labels to \"simplify\" diagrams\n\n## Microservices Guidelines\n\n- **Single team ownership:** model each microservice as a **container** (or container group) inside one `System_Boundary`.\n- **Multi-team ownership:** promote microservices to **software systems** in a Context diagram.\n- **Event-driven:** show individual topics\u002Fqueues as `ContainerQueue` elements (e.g. `order.created`), NOT a single \"Kafka\" box.\n\n## Output Location\n\nWrite architecture documentation to `docs\u002Farchitecture\u002F`:\n\n- `c4-context.md` — System context diagram\n- `c4-containers.md` — Container diagram\n- `c4-components-{feature}.md` — Component diagrams per feature\n- `c4-deployment.md` — Deployment diagram\n- `c4-dynamic-{flow}.md` — Dynamic diagrams for specific flows\n\n## Audience-Appropriate Detail\n\n| Audience | Recommended Diagrams |\n|----------|---------------------|\n| Executives | System Context only |\n| Product Managers | Context + Container |\n| Architects | Context + Container + key Components |\n| Developers | All levels as needed |\n| DevOps | Container + Deployment |\n",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5","skills\u002Fc4-architecture","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill c4-architecture",{"tool":56,"command":57},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill c4-architecture",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill c4-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Fskills\u002Fc4-architecture\u002FSKILL.md",true,[],[65,86,117,144,158,174],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":39},"01M6DF7D7478R55P46REYH4QAC","clarify-requirements","Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fworkspace-hooks\u002Fskills\u002Fclarify-requirements\u002FSKILL.md",[],[72,73,74,75,76,77,78,79,80,28,81,82,83,84,85],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","context","repo","injection","execution","file",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":97,"publishedAt":39},"01M6DF79CA4BHJS66J8EZDBPWJ","openmm-md","Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein \u002F protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fmcp\u002Fopenmm-md-mcp\u002Fskill\u002Fopenmm-md\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[98,99,100,101,102,103,104,105,106,107,108,109,110,111,28,112,113,114,115,116],"openmm md","how","decision","pick","linux","analyze","tool","stack","open","NVIDIA","gpu","license","workflow","windows","free","molecular dynamics","local","do","MCP",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":129,"publishedAt":39},"01M6DF76C1MG85VEWP8VZCBNMN","visual-review","Take screenshots of web pages and UI using Playwright for visual review and iteration","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fvisual-review\u002FSKILL.md",[123,126],{"categoryNo":124,"categoryName":125,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":127,"categoryName":128,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000008","测试与质量",[130,131,132,133,134,135,136,137,138,139,99,140,141,142,143],"review","visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":39},"01M6DF73AQVCBZKEN0YXEX9FXP","status","Diagnostic status report — shows metaswarm installation state, project setup, and potential issues","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstatus\u002FSKILL.md",[],[146,151,152,153,154,155,156,157],"setup","report","project","installation","project setup","issues","state",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":165,"publishedAt":39},"01M6DF6X6C2XB0P6GX76P7TTYV","start","Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstart\u002FSKILL.md",[164],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[160,166,77,167,168,169,28,170,171,172,173],"start issue","issue","ready","work on issue","user","work","work on","development",{"skillNo":175,"name":151,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":39},"01M6DF6QMJ9AJKFKHHKRT005PQ","Interactive project setup — detects your project, configures metaswarm, writes project-local files","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fsetup\u002FSKILL.md",[],[151,153,114,180,155,181],"files","interactive"]