[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ACGWNVCBXVBF102CGNZQ48":3,"skill-same:01M6ACGWNVCBXVBF102CGNZQ48":84},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M6ACGWNVCBXVBF102CGNZQ48","maka-architecture-docs",null,"Draft, restructure, translate, or review bilingual Chinese-English architecture documentation for the Maka Agent backend. Use when Codex works on Maka technical narratives, component or mechanism explanations, architecture decisions, system flows, engineering guides, or documentation quality checks and needs blog-like clarity without losing architectural precision. Do not use it to impose a fixed topic list or information architecture unless the user asks for one.","apache\u002Fmaka","apache","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47359?v=4","01M6AC83E6K4FDKK7HZ8WNMQKE","The Apache Software Foundation","01M6ACGN569Q91C1K1T4YFW41W",5963,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fapache\u002Fmaka\u002Fblob\u002Fmain\u002Fskills\u002Fmaka-architecture-docs\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32],"docs","architecture","maka","maka architecture docs","review","codex","translate","component","documentation","2026-11-10 10:12:30",false,"---\nname: maka-architecture-docs\ndescription: Draft, restructure, translate, or review bilingual Chinese-English architecture documentation for the Maka Agent backend. Use when Codex works on Maka technical narratives, component or mechanism explanations, architecture decisions, system flows, engineering guides, or documentation quality checks and needs blog-like clarity without losing architectural precision. Do not use it to impose a fixed topic list or information architecture unless the user asks for one.\n---\n\u003C!--\n  Licensed to the Apache Software Foundation (ASF) under one\n  or more contributor license agreements.  See the NOTICE file\n  distributed with this work for additional information\n  regarding copyright ownership.  The ASF licenses this file\n  to you under the Apache License, Version 2.0 (the\n  \"License\"); you may not use this file except in compliance\n  with the License.  You may obtain a copy of the License at\n\n      http:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0\n\n  Unless required by applicable law or agreed to in writing,\n  software distributed under the License is distributed on an\n  \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\n  KIND, either express or implied.  See the License for the\n  specific language governing permissions and limitations\n  under the License.\n-->\n\n# Maka Architecture Docs\n\nCreate architecture documentation that is easy to enter, technically rigorous, and maintainable in both Chinese and English. Treat the user's chosen subject and document organization as constraints; this skill governs writing quality, evidence, bilingual consistency, and review.\n\n## Select the task mode\n\n- **Draft**: create a new document from code, design notes, interviews, or a user brief.\n- **Rewrite**: improve an existing document while preserving its technical meaning.\n- **Translate**: produce a natural counterpart in the other language, not a sentence-by-sentence transliteration.\n- **Review**: identify concrete gaps in clarity, evidence, correctness, or bilingual consistency.\n- **Standardize**: align multiple documents on terminology, metadata, status labels, and structure without forcing them into identical narratives.\n\nConfirm the intended mode from the request. Infer it when safe; ask only when different interpretations would materially change the output.\n\n## Follow the workflow\n\n1. **Establish the article contract.** State the one core question, intended reader, expected reading depth, source language, and claimed implementation status. Do not invent a topic or replace the user's outline.\n2. **Collect evidence.** Inspect the relevant code paths, tests, schemas, configuration, ADRs, and existing documents before presenting implementation details as facts. Separate verified behavior from plans and interpretation.\n3. **Build the narrative.** Move from problem and intuition to a concrete scenario, then mechanism, boundaries, failures, and trade-offs. Include only the sections that help answer the core question.\n4. **Add technical anchors.** Connect claims to real components, state transitions, invariants, interfaces, observability signals, or code locations as appropriate.\n5. **Create the bilingual counterpart.** Preserve concepts, status, examples, diagrams, and section identity while rewriting naturally for the target language.\n6. **Run the quality gate.** Review both language versions against `references\u002Fquality-gate.md`. Fix failed required checks before calling the document complete.\n\nRead `references\u002Fwriting-standard.md` whenever drafting, rewriting, or standardizing architecture content. Read `references\u002Fbilingual-standard.md` whenever creating or reviewing both languages. Use `assets\u002Farticle-template.md` as a starting scaffold only when it fits the chosen subject; remove irrelevant sections rather than filling them mechanically.\n\n## Apply non-negotiable rules\n\n- Start from a reader question or engineering problem, not a component inventory.\n- Distinguish **Current**, **Planned**, **Exploratory**, **Deprecated**, and **Historical** claims.\n- Never present an unverified design assumption as current implementation.\n- Explain important mechanisms through intuition, scenario, mechanism, and boundary.\n- Cover meaningful failure paths and trade-offs, not only the happy path.\n- Keep diagrams purposeful and language-neutral where practical; explain what each diagram includes and omits.\n- Use stable terms. Do not alternate among synonyms for variety when they represent the same Maka concept.\n- Prefer separate, complete Chinese and English documents with shared assets over interleaved paragraph-by-paragraph translation.\n- Preserve uncertainty. Translation must not strengthen or weaken a claim.\n- Optimize for progressive depth: a reader should gain value from the opening summary without reading the entire article.\n\n## Handle reviews\n\nLead with actionable findings ordered by impact. Cite the exact section or line when possible. Check, in order:\n\n1. factual correctness and status confusion;\n2. missing boundaries, invariants, or failure behavior;\n3. broken narrative or unexplained concepts;\n4. bilingual semantic drift and terminology inconsistency;\n5. maintainability issues such as duplicated diagrams or unstable code references;\n6. style polish.\n\nIf there are no material findings, say so and identify any verification limits.\n\n## Deliver artifacts\n\nWhen creating files, follow the repository's existing documentation layout. If no convention exists, recommend rather than silently establish a new repository-wide structure. Keep language counterparts at matching relative paths or give them stable shared document IDs. Report which technical claims were verified and which remain planned or uncertain.\n","\u003C!--\n  Licensed to the Apache Software Foundation (ASF) under one\n  or more contributor license agreements.  See the NOTICE file\n  distributed with this work for additional information\n  regarding copyright ownership.  The ASF licenses this file\n  to you under the Apache License, Version 2.0 (the\n  \"License\"); you may not use this file except in compliance\n  with the License.  You may obtain a copy of the License at\n\n      http:\u002F\u002Fwww.apache.org\u002Flicenses\u002FLICENSE-2.0\n\n  Unless required by applicable law or agreed to in writing,\n  software distributed under the License is distributed on an\n  \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY\n  KIND, either express or implied.  See the License for the\n  specific language governing permissions and limitations\n  under the License.\n-->\n\n# Maka Architecture Docs\n\nCreate architecture documentation that is easy to enter, technically rigorous, and maintainable in both Chinese and English. Treat the user's chosen subject and document organization as constraints; this skill governs writing quality, evidence, bilingual consistency, and review.\n\n## Select the task mode\n\n- **Draft**: create a new document from code, design notes, interviews, or a user brief.\n- **Rewrite**: improve an existing document while preserving its technical meaning.\n- **Translate**: produce a natural counterpart in the other language, not a sentence-by-sentence transliteration.\n- **Review**: identify concrete gaps in clarity, evidence, correctness, or bilingual consistency.\n- **Standardize**: align multiple documents on terminology, metadata, status labels, and structure without forcing them into identical narratives.\n\nConfirm the intended mode from the request. Infer it when safe; ask only when different interpretations would materially change the output.\n\n## Follow the workflow\n\n1. **Establish the article contract.** State the one core question, intended reader, expected reading depth, source language, and claimed implementation status. Do not invent a topic or replace the user's outline.\n2. **Collect evidence.** Inspect the relevant code paths, tests, schemas, configuration, ADRs, and existing documents before presenting implementation details as facts. Separate verified behavior from plans and interpretation.\n3. **Build the narrative.** Move from problem and intuition to a concrete scenario, then mechanism, boundaries, failures, and trade-offs. Include only the sections that help answer the core question.\n4. **Add technical anchors.** Connect claims to real components, state transitions, invariants, interfaces, observability signals, or code locations as appropriate.\n5. **Create the bilingual counterpart.** Preserve concepts, status, examples, diagrams, and section identity while rewriting naturally for the target language.\n6. **Run the quality gate.** Review both language versions against `references\u002Fquality-gate.md`. Fix failed required checks before calling the document complete.\n\nRead `references\u002Fwriting-standard.md` whenever drafting, rewriting, or standardizing architecture content. Read `references\u002Fbilingual-standard.md` whenever creating or reviewing both languages. Use `assets\u002Farticle-template.md` as a starting scaffold only when it fits the chosen subject; remove irrelevant sections rather than filling them mechanically.\n\n## Apply non-negotiable rules\n\n- Start from a reader question or engineering problem, not a component inventory.\n- Distinguish **Current**, **Planned**, **Exploratory**, **Deprecated**, and **Historical** claims.\n- Never present an unverified design assumption as current implementation.\n- Explain important mechanisms through intuition, scenario, mechanism, and boundary.\n- Cover meaningful failure paths and trade-offs, not only the happy path.\n- Keep diagrams purposeful and language-neutral where practical; explain what each diagram includes and omits.\n- Use stable terms. Do not alternate among synonyms for variety when they represent the same Maka concept.\n- Prefer separate, complete Chinese and English documents with shared assets over interleaved paragraph-by-paragraph translation.\n- Preserve uncertainty. Translation must not strengthen or weaken a claim.\n- Optimize for progressive depth: a reader should gain value from the opening summary without reading the entire article.\n\n## Handle reviews\n\nLead with actionable findings ordered by impact. Cite the exact section or line when possible. Check, in order:\n\n1. factual correctness and status confusion;\n2. missing boundaries, invariants, or failure behavior;\n3. broken narrative or unexplained concepts;\n4. bilingual semantic drift and terminology inconsistency;\n5. maintainability issues such as duplicated diagrams or unstable code references;\n6. style polish.\n\nIf there are no material findings, say so and identify any verification limits.\n\n## Deliver artifacts\n\nWhen creating files, follow the repository's existing documentation layout. If no convention exists, recommend rather than silently establish a new repository-wide structure. Keep language counterparts at matching relative paths or give them stable shared document IDs. Report which technical claims were verified and which remain planned or uncertain.\n",{"name":5,"description":7},"main","85a1031c10d104456127f35aac1523b9ffb1a384","skills\u002Fmaka-architecture-docs",576,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmaka","https:\u002F\u002Fgithub.com\u002Fapache","https:\u002F\u002Fwww.apache.org\u002F","2026-11-13 02:28:34",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add apache\u002Fmaka --skill maka-architecture-docs",{"tool":52,"command":53},"bunx","bunx skills add apache\u002Fmaka --skill maka-architecture-docs",{"tool":55,"command":56},"pnpm","pnpm dlx skills add apache\u002Fmaka --skill maka-architecture-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fapache\u002Fmaka\u002Fblob\u002Fmain\u002Fskills\u002Fmaka-architecture-docs\u002FSKILL.md",true,[60,66,72,76,80],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"agents\u002Fopenai.yaml","REFERENCE","参考文档",1038,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmaka\u002Fblob\u002Fmain\u002Fskills\u002Fmaka-architecture-docs\u002Fagents\u002Fopenai.yaml",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Farticle-template.md","ASSET","资产文件",2751,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmaka\u002Fblob\u002Fmain\u002Fskills\u002Fmaka-architecture-docs\u002Fassets\u002Farticle-template.md",{"path":73,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fbilingual-standard.md",4436,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmaka\u002Fblob\u002Fmain\u002Fskills\u002Fmaka-architecture-docs\u002Freferences\u002Fbilingual-standard.md",{"path":77,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fquality-gate.md",3666,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmaka\u002Fblob\u002Fmain\u002Fskills\u002Fmaka-architecture-docs\u002Freferences\u002Fquality-gate.md",{"path":81,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fwriting-standard.md",6405,"https:\u002F\u002Fgithub.com\u002Fapache\u002Fmaka\u002Fblob\u002Fmain\u002Fskills\u002Fmaka-architecture-docs\u002Freferences\u002Fwriting-standard.md",[85,96,109],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":33},"01M6ACGZJS73JGSVSB1T6H9F4S","maka-cli","Coordinate Maka CLI as a worker to submit tasks, inspect progress, update saved models, and handle Session questions or approvals.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fmaka\u002Fblob\u002Fmain\u002Fskills\u002Fmaka-cli\u002FSKILL.md",[],[92,26,93,94,95],"maka cli","cli","update","tasks",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":33},"01M6ACGTDB3DBG1F7F803ZHDW2","Computer Use","Use when the user asks to inspect or operate a local desktop application UI, including reading windows, clicking controls, filling forms, using menus, scrolling lists, moving windows, or waiting for dialogs. Trigger for requests such as \"operate this app\", \"do this in TextEdit\u002FCalculator\u002FSettings\", \"look at the current window\", or \"click\u002Ftype\u002Fscroll\"; prefer Browser tools for web pages and non-GUI tools for files or terminal work.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fmaka\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime\u002Fresources\u002Fbundled-skills\u002Fcomputer-use\u002FSKILL.md",[],[98,103,26,104,105,106,107,108],"browser","search","desktop","windows","web","terminal",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":123,"publishedAt":33},"01M6ACGQKD21BK5N7JTVTCRN8F","code-review","Adversarially review pull requests and code changes against the actual problem. Use for GitHub Copilot code review to assess correctness, root cause, simplicity, deletions, test quality, maintainability, and merge readiness.","https:\u002F\u002Fgithub.com\u002Fapache\u002Fmaka\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcode-review\u002FSKILL.md",[115,118],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[28,124,125,126,127,128,129,130,131,132],"code","code review","github","test","pull requests","merge","pull","github copilot","copilot"]