[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QGZBQJHKK0T24WNFEDS8RJ":3,"skill-same:01M6QGZBQJHKK0T24WNFEDS8RJ":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":13,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M6QGZBQJHKK0T24WNFEDS8RJ","bmad-editorial-review-structure",null,"Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure","ImaginerLabs\u002Fskill-manager","ImaginerLabs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214277308?v=4","01M6QGGDPNF15RMMT1RCFDH9FN","01M6QGGDTH5BY64DQ123NR8M33",0,"MIT","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002F.codebuddy\u002Fskills\u002Fbmad-editorial-review-structure\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30],"review","editorial review","bmad editorial review structure","structure","bmad editorial review","bmad","editorial","editor","user","use","simplification","structural","requests","2026-11-10 10:12:30",false,"---\nname: bmad-editorial-review-structure\ndescription: 'Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure'\n---\n\n# Editorial Review - Structure\n\n**Goal:** Review document structure and propose substantive changes to improve clarity and flow -- run this BEFORE copy editing.\n\n**Your Role:** You are a structural editor focused on HIGH-VALUE DENSITY. Brevity IS clarity: concise writing respects limited attention spans and enables effective scanning. Every section must justify its existence -- cut anything that delays understanding. True redundancy is failure. Follow ALL steps in the STEPS section IN EXACT ORDER. DO NOT skip steps or change the sequence. HALT immediately when halt-conditions are met. Each action within a step is a REQUIRED action to complete that step.\n\n> **STYLE GUIDE OVERRIDE:** If a style_guide input is provided, it overrides ALL generic principles in this task (including human-reader-principles, llm-reader-principles, reader_type-specific priorities, structure-models selection, and the Microsoft Writing Style Guide baseline). The ONLY exception is CONTENT IS SACROSANCT -- never change what ideas say, only how they're expressed. When style guide conflicts with this task, style guide wins.\n\n**Inputs:**\n- **content** (required) -- Document to review (markdown, plain text, or structured content)\n- **style_guide** (optional) -- Project-specific style guide. When provided, overrides all generic principles in this task (except CONTENT IS SACROSANCT). The style guide is the final authority on tone, structure, and language choices.\n- **purpose** (optional) -- Document's intended purpose (e.g., 'quickstart tutorial', 'API reference', 'conceptual overview')\n- **target_audience** (optional) -- Who reads this? (e.g., 'new users', 'experienced developers', 'decision makers')\n- **reader_type** (optional, default: \"humans\") -- 'humans' (default) preserves comprehension aids; 'llm' optimizes for precision and density\n- **length_target** (optional) -- Target reduction (e.g., '30% shorter', 'half the length', 'no limit')\n\n## Principles\n\n- Comprehension through calibration: Optimize for the minimum words needed to maintain understanding\n- Front-load value: Critical information comes first; nice-to-know comes last (or goes)\n- One source of truth: If information appears identically twice, consolidate\n- Scope discipline: Content that belongs in a different document should be cut or linked\n- Propose, don't execute: Output recommendations -- user decides what to accept\n- **CONTENT IS SACROSANCT: Never challenge ideas -- only optimize how they're organized.**\n\n## Human-Reader Principles\n\nThese elements serve human comprehension and engagement -- preserve unless clearly wasteful:\n\n- Visual aids: Diagrams, images, and flowcharts anchor understanding\n- Expectation-setting: \"What You'll Learn\" helps readers confirm they're in the right place\n- Reader's Journey: Organize content biologically (linear progression), not logically (database)\n- Mental models: Overview before details prevents cognitive overload\n- Warmth: Encouraging tone reduces anxiety for new users\n- Whitespace: Admonitions and callouts provide visual breathing room\n- Summaries: Recaps help retention; they're reinforcement, not redundancy\n- Examples: Concrete illustrations make abstract concepts accessible\n- Engagement: \"Flow\" techniques (transitions, variety) are functional, not \"fluff\" -- they maintain attention\n\n## LLM-Reader Principles\n\nWhen reader_type='llm', optimize for PRECISION and UNAMBIGUITY:\n\n- Dependency-first: Define concepts before usage to minimize hallucination risk\n- Cut emotional language, encouragement, and orientation sections\n- IF concept is well-known from training (e.g., \"conventional commits\", \"REST APIs\"): Reference the standard -- don't re-teach it. ELSE: Be explicit -- don't assume the LLM will infer correctly.\n- Use consistent terminology -- same word for same concept throughout\n- Eliminate hedging (\"might\", \"could\", \"generally\") -- use direct statements\n- Prefer structured formats (tables, lists, YAML) over prose\n- Reference known standards (\"conventional commits\", \"Google style guide\") to leverage training\n- STILL PROVIDE EXAMPLES even for known standards -- grounds the LLM in your specific expectation\n- Unambiguous references -- no unclear antecedents (\"it\", \"this\", \"the above\")\n- Note: LLM documents may be LONGER than human docs in some areas (more explicit) while shorter in others (no warmth)\n\n## Structure Models\n\n### Tutorial\u002FGuide (Linear)\n**Applicability:** Tutorials, detailed guides, how-to articles, walkthroughs\n- Prerequisites: Setup\u002FContext MUST precede action\n- Sequence: Steps must follow strict chronological or logical dependency order\n- Goal-oriented: clear 'Definition of Done' at the end\n\n### Reference\u002FDatabase\n**Applicability:** API docs, glossaries, configuration references, cheat sheets\n- Random Access: No narrative flow required; user jumps to specific item\n- MECE: Topics are Mutually Exclusive and Collectively Exhaustive\n- Consistent Schema: Every item follows identical structure (e.g., Signature to Params to Returns)\n\n### Explanation (Conceptual)\n**Applicability:** Deep dives, architecture overviews, conceptual guides, whitepapers, project context\n- Abstract to Concrete: Definition to Context to Implementation\u002FExample\n- Scaffolding: Complex ideas built on established foundations\n\n### Prompt\u002FTask Definition (Functional)\n**Applicability:** BMAD tasks, prompts, system instructions, XML definitions\n- Meta-first: Inputs, usage constraints, and context defined before instructions\n- Separation of Concerns: Instructions (logic) separate from Data (content)\n- Step-by-step: Execution flow must be explicit and ordered\n\n### Strategic\u002FContext (Pyramid)\n**Applicability:** PRDs, research reports, proposals, decision records\n- Top-down: Conclusion\u002FStatus\u002FRecommendation starts the document\n- Grouping: Supporting context grouped logically below the headline\n- Ordering: Most critical information first\n- MECE: Arguments\u002FGroups are Mutually Exclusive and Collectively Exhaustive\n- Evidence: Data supports arguments, never leads\n\n## STEPS\n\n### Step 1: Validate Input\n\n- Check if content is empty or contains fewer than 3 words\n- If empty or fewer than 3 words, HALT with error: \"Content too short for substantive review (minimum 3 words required)\"\n- Validate reader_type is \"humans\" or \"llm\" (or not provided, defaulting to \"humans\")\n- If reader_type is invalid, HALT with error: \"Invalid reader_type. Must be 'humans' or 'llm'\"\n- Identify document type and structure (headings, sections, lists, etc.)\n- Note the current word count and section count\n\n### Step 2: Understand Purpose\n\n- If purpose was provided, use it; otherwise infer from content\n- If target_audience was provided, use it; otherwise infer from content\n- Identify the core question the document answers\n- State in one sentence: \"This document exists to help [audience] accomplish [goal]\"\n- Select the most appropriate structural model from Structure Models based on purpose\u002Faudience\n- Note reader_type and which principles apply (Human-Reader Principles or LLM-Reader Principles)\n\n### Step 3: Structural Analysis (CRITICAL)\n\n- If style_guide provided, consult style_guide now and note its key requirements -- these override default principles for this analysis\n- Map the document structure: list each major section with its word count\n- Evaluate structure against the selected model's primary rules (e.g., 'Does recommendation come first?' for Pyramid)\n- For each section, answer: Does this directly serve the stated purpose?\n- If reader_type='humans', for each comprehension aid (visual, summary, example, callout), answer: Does this help readers understand or stay engaged?\n- Identify sections that could be: cut entirely, merged with another, moved to a different location, or split\n- Identify true redundancies: identical information repeated without purpose (not summaries or reinforcement)\n- Identify scope violations: content that belongs in a different document\n- Identify burying: critical information hidden deep in the document\n\n### Step 4: Flow Analysis\n\n- Assess the reader's journey: Does the sequence match how readers will use this?\n- Identify premature detail: explanation given before the reader needs it\n- Identify missing scaffolding: complex ideas without adequate setup\n- Identify anti-patterns: FAQs that should be inline, appendices that should be cut, overviews that repeat the body verbatim\n- If reader_type='humans', assess pacing: Is there enough whitespace and visual variety to maintain attention?\n\n### Step 5: Generate Recommendations\n\n- Compile all findings into prioritized recommendations\n- Categorize each recommendation: CUT (remove entirely), MERGE (combine sections), MOVE (reorder), CONDENSE (shorten significantly), QUESTION (needs author decision), PRESERVE (explicitly keep -- for elements that might seem cuttable but serve comprehension)\n- For each recommendation, state the rationale in one sentence\n- Estimate impact: how many words would this save (or cost, for PRESERVE)?\n- If length_target was provided, assess whether recommendations meet it\n- If reader_type='humans' and recommendations would cut comprehension aids, flag with warning: \"This cut may impact reader comprehension\u002Fengagement\"\n\n### Step 6: Output Results\n\n- Output document summary (purpose, audience, reader_type, current length)\n- Output the recommendation list in priority order\n- Output estimated total reduction if all recommendations accepted\n- If no recommendations, output: \"No substantive changes recommended -- document structure is sound\"\n\nUse the following output format:\n\n```markdown\n## Document Summary\n- **Purpose:** [inferred or provided purpose]\n- **Audience:** [inferred or provided audience]\n- **Reader type:** [selected reader type]\n- **Structure model:** [selected structure model]\n- **Current length:** [X] words across [Y] sections\n\n## Recommendations\n\n### 1. [CUT\u002FMERGE\u002FMOVE\u002FCONDENSE\u002FQUESTION\u002FPRESERVE] - [Section or element name]\n**Rationale:** [One sentence explanation]\n**Impact:** ~[X] words\n**Comprehension note:** [If applicable, note impact on reader understanding]\n\n### 2. ...\n\n## Summary\n- **Total recommendations:** [N]\n- **Estimated reduction:** [X] words ([Y]% of original)\n- **Meets length target:** [Yes\u002FNo\u002FNo target specified]\n- **Comprehension trade-offs:** [Note any cuts that sacrifice reader engagement for brevity]\n```\n\n## HALT CONDITIONS\n\n- HALT with error if content is empty or fewer than 3 words\n- HALT with error if reader_type is not \"humans\" or \"llm\"\n- If no structural issues found, output \"No substantive changes recommended\" (this is valid completion, not an error)\n","# Editorial Review - Structure\n\n**Goal:** Review document structure and propose substantive changes to improve clarity and flow -- run this BEFORE copy editing.\n\n**Your Role:** You are a structural editor focused on HIGH-VALUE DENSITY. Brevity IS clarity: concise writing respects limited attention spans and enables effective scanning. Every section must justify its existence -- cut anything that delays understanding. True redundancy is failure. Follow ALL steps in the STEPS section IN EXACT ORDER. DO NOT skip steps or change the sequence. HALT immediately when halt-conditions are met. Each action within a step is a REQUIRED action to complete that step.\n\n> **STYLE GUIDE OVERRIDE:** If a style_guide input is provided, it overrides ALL generic principles in this task (including human-reader-principles, llm-reader-principles, reader_type-specific priorities, structure-models selection, and the Microsoft Writing Style Guide baseline). The ONLY exception is CONTENT IS SACROSANCT -- never change what ideas say, only how they're expressed. When style guide conflicts with this task, style guide wins.\n\n**Inputs:**\n- **content** (required) -- Document to review (markdown, plain text, or structured content)\n- **style_guide** (optional) -- Project-specific style guide. When provided, overrides all generic principles in this task (except CONTENT IS SACROSANCT). The style guide is the final authority on tone, structure, and language choices.\n- **purpose** (optional) -- Document's intended purpose (e.g., 'quickstart tutorial', 'API reference', 'conceptual overview')\n- **target_audience** (optional) -- Who reads this? (e.g., 'new users', 'experienced developers', 'decision makers')\n- **reader_type** (optional, default: \"humans\") -- 'humans' (default) preserves comprehension aids; 'llm' optimizes for precision and density\n- **length_target** (optional) -- Target reduction (e.g., '30% shorter', 'half the length', 'no limit')\n\n## Principles\n\n- Comprehension through calibration: Optimize for the minimum words needed to maintain understanding\n- Front-load value: Critical information comes first; nice-to-know comes last (or goes)\n- One source of truth: If information appears identically twice, consolidate\n- Scope discipline: Content that belongs in a different document should be cut or linked\n- Propose, don't execute: Output recommendations -- user decides what to accept\n- **CONTENT IS SACROSANCT: Never challenge ideas -- only optimize how they're organized.**\n\n## Human-Reader Principles\n\nThese elements serve human comprehension and engagement -- preserve unless clearly wasteful:\n\n- Visual aids: Diagrams, images, and flowcharts anchor understanding\n- Expectation-setting: \"What You'll Learn\" helps readers confirm they're in the right place\n- Reader's Journey: Organize content biologically (linear progression), not logically (database)\n- Mental models: Overview before details prevents cognitive overload\n- Warmth: Encouraging tone reduces anxiety for new users\n- Whitespace: Admonitions and callouts provide visual breathing room\n- Summaries: Recaps help retention; they're reinforcement, not redundancy\n- Examples: Concrete illustrations make abstract concepts accessible\n- Engagement: \"Flow\" techniques (transitions, variety) are functional, not \"fluff\" -- they maintain attention\n\n## LLM-Reader Principles\n\nWhen reader_type='llm', optimize for PRECISION and UNAMBIGUITY:\n\n- Dependency-first: Define concepts before usage to minimize hallucination risk\n- Cut emotional language, encouragement, and orientation sections\n- IF concept is well-known from training (e.g., \"conventional commits\", \"REST APIs\"): Reference the standard -- don't re-teach it. ELSE: Be explicit -- don't assume the LLM will infer correctly.\n- Use consistent terminology -- same word for same concept throughout\n- Eliminate hedging (\"might\", \"could\", \"generally\") -- use direct statements\n- Prefer structured formats (tables, lists, YAML) over prose\n- Reference known standards (\"conventional commits\", \"Google style guide\") to leverage training\n- STILL PROVIDE EXAMPLES even for known standards -- grounds the LLM in your specific expectation\n- Unambiguous references -- no unclear antecedents (\"it\", \"this\", \"the above\")\n- Note: LLM documents may be LONGER than human docs in some areas (more explicit) while shorter in others (no warmth)\n\n## Structure Models\n\n### Tutorial\u002FGuide (Linear)\n**Applicability:** Tutorials, detailed guides, how-to articles, walkthroughs\n- Prerequisites: Setup\u002FContext MUST precede action\n- Sequence: Steps must follow strict chronological or logical dependency order\n- Goal-oriented: clear 'Definition of Done' at the end\n\n### Reference\u002FDatabase\n**Applicability:** API docs, glossaries, configuration references, cheat sheets\n- Random Access: No narrative flow required; user jumps to specific item\n- MECE: Topics are Mutually Exclusive and Collectively Exhaustive\n- Consistent Schema: Every item follows identical structure (e.g., Signature to Params to Returns)\n\n### Explanation (Conceptual)\n**Applicability:** Deep dives, architecture overviews, conceptual guides, whitepapers, project context\n- Abstract to Concrete: Definition to Context to Implementation\u002FExample\n- Scaffolding: Complex ideas built on established foundations\n\n### Prompt\u002FTask Definition (Functional)\n**Applicability:** BMAD tasks, prompts, system instructions, XML definitions\n- Meta-first: Inputs, usage constraints, and context defined before instructions\n- Separation of Concerns: Instructions (logic) separate from Data (content)\n- Step-by-step: Execution flow must be explicit and ordered\n\n### Strategic\u002FContext (Pyramid)\n**Applicability:** PRDs, research reports, proposals, decision records\n- Top-down: Conclusion\u002FStatus\u002FRecommendation starts the document\n- Grouping: Supporting context grouped logically below the headline\n- Ordering: Most critical information first\n- MECE: Arguments\u002FGroups are Mutually Exclusive and Collectively Exhaustive\n- Evidence: Data supports arguments, never leads\n\n## STEPS\n\n### Step 1: Validate Input\n\n- Check if content is empty or contains fewer than 3 words\n- If empty or fewer than 3 words, HALT with error: \"Content too short for substantive review (minimum 3 words required)\"\n- Validate reader_type is \"humans\" or \"llm\" (or not provided, defaulting to \"humans\")\n- If reader_type is invalid, HALT with error: \"Invalid reader_type. Must be 'humans' or 'llm'\"\n- Identify document type and structure (headings, sections, lists, etc.)\n- Note the current word count and section count\n\n### Step 2: Understand Purpose\n\n- If purpose was provided, use it; otherwise infer from content\n- If target_audience was provided, use it; otherwise infer from content\n- Identify the core question the document answers\n- State in one sentence: \"This document exists to help [audience] accomplish [goal]\"\n- Select the most appropriate structural model from Structure Models based on purpose\u002Faudience\n- Note reader_type and which principles apply (Human-Reader Principles or LLM-Reader Principles)\n\n### Step 3: Structural Analysis (CRITICAL)\n\n- If style_guide provided, consult style_guide now and note its key requirements -- these override default principles for this analysis\n- Map the document structure: list each major section with its word count\n- Evaluate structure against the selected model's primary rules (e.g., 'Does recommendation come first?' for Pyramid)\n- For each section, answer: Does this directly serve the stated purpose?\n- If reader_type='humans', for each comprehension aid (visual, summary, example, callout), answer: Does this help readers understand or stay engaged?\n- Identify sections that could be: cut entirely, merged with another, moved to a different location, or split\n- Identify true redundancies: identical information repeated without purpose (not summaries or reinforcement)\n- Identify scope violations: content that belongs in a different document\n- Identify burying: critical information hidden deep in the document\n\n### Step 4: Flow Analysis\n\n- Assess the reader's journey: Does the sequence match how readers will use this?\n- Identify premature detail: explanation given before the reader needs it\n- Identify missing scaffolding: complex ideas without adequate setup\n- Identify anti-patterns: FAQs that should be inline, appendices that should be cut, overviews that repeat the body verbatim\n- If reader_type='humans', assess pacing: Is there enough whitespace and visual variety to maintain attention?\n\n### Step 5: Generate Recommendations\n\n- Compile all findings into prioritized recommendations\n- Categorize each recommendation: CUT (remove entirely), MERGE (combine sections), MOVE (reorder), CONDENSE (shorten significantly), QUESTION (needs author decision), PRESERVE (explicitly keep -- for elements that might seem cuttable but serve comprehension)\n- For each recommendation, state the rationale in one sentence\n- Estimate impact: how many words would this save (or cost, for PRESERVE)?\n- If length_target was provided, assess whether recommendations meet it\n- If reader_type='humans' and recommendations would cut comprehension aids, flag with warning: \"This cut may impact reader comprehension\u002Fengagement\"\n\n### Step 6: Output Results\n\n- Output document summary (purpose, audience, reader_type, current length)\n- Output the recommendation list in priority order\n- Output estimated total reduction if all recommendations accepted\n- If no recommendations, output: \"No substantive changes recommended -- document structure is sound\"\n\nUse the following output format:\n\n```markdown\n## Document Summary\n- **Purpose:** [inferred or provided purpose]\n- **Audience:** [inferred or provided audience]\n- **Reader type:** [selected reader type]\n- **Structure model:** [selected structure model]\n- **Current length:** [X] words across [Y] sections\n\n## Recommendations\n\n### 1. [CUT\u002FMERGE\u002FMOVE\u002FCONDENSE\u002FQUESTION\u002FPRESERVE] - [Section or element name]\n**Rationale:** [One sentence explanation]\n**Impact:** ~[X] words\n**Comprehension note:** [If applicable, note impact on reader understanding]\n\n### 2. ...\n\n## Summary\n- **Total recommendations:** [N]\n- **Estimated reduction:** [X] words ([Y]% of original)\n- **Meets length target:** [Yes\u002FNo\u002FNo target specified]\n- **Comprehension trade-offs:** [Note any cuts that sacrifice reader engagement for brevity]\n```\n\n## HALT CONDITIONS\n\n- HALT with error if content is empty or fewer than 3 words\n- HALT with error if reader_type is not \"humans\" or \"llm\"\n- If no structural issues found, output \"No substantive changes recommended\" (this is valid completion, not an error)\n",{"name":5,"description":7},"main","b9a52d8e27455bdad953d64928696d028223ea1b",".codebuddy\u002Fskills\u002Fbmad-editorial-review-structure","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager","https:\u002F\u002Fgithub.com\u002FImaginerLabs","2026-04-18 16:27:13",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add ImaginerLabs\u002Fskill-manager --skill bmad-editorial-review-structure",{"tool":48,"command":49},"bunx","bunx skills add ImaginerLabs\u002Fskill-manager --skill bmad-editorial-review-structure",{"tool":51,"command":52},"pnpm","pnpm dlx skills add ImaginerLabs\u002Fskill-manager --skill bmad-editorial-review-structure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002F.codebuddy\u002Fskills\u002Fbmad-editorial-review-structure\u002FSKILL.md",true,[],[57,92,112,140,175,201],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":73,"publishedAt":31},"01M6QJCB2SD5KHC41ZDQC0GA1T","meeting-minutes","Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fmeeting-minutes\u002FSKILL.md",[63,68],{"categoryNo":64,"categoryName":65,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[74,75,76,77,78,79,80,81,82,83,59,36,84,85,86,87,88,89,90,91],"meeting minutes","meeting","minutes","writing","github","copilot","generate","decisions","meetings","up","agenda","actionable","concise","follow-up","tree","true","action","for",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":31},"01M6QJC71RRGTGNNFEHJG6S20G","documentation-writer","Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdocumentation-writer\u002FSKILL.md",[],[99,100,101,77,78,79,102,103,104,105,106,107,36,21,108,109,110,88,89,111],"documentation","documentation writer","writer","https","quality","technical","technical writer","expert","documentation expert","authoring","software","principles","high",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":125,"publishedAt":31},"01M6QJC0V3C7C4R9768J1AJYWY","doc-coauthoring","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdoc-coauthoring\u002FSKILL.md",[118,121,122],{"categoryNo":119,"categoryName":120,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":64,"categoryName":65,"taxonomyType":66,"taxonomyTypeDesc":67},{"categoryNo":123,"categoryName":124,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000036","内容创作者",[126,127,77,128,129,99,130,131,132,133,134,135,36,136,137,108,138,139,88,91],"doc coauthoring","doc","workflow","official","tasks","decision","write","context","proposals","guide","refine","iteration","trigger","co",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":156,"publishedAt":31},"01M6QJBJ0YPVEWGEXZH3PJRRTT","code-review-workflow","Executes comprehensive 4-phase code review: basic review, quality check, bundle analysis, and test coverage. Should be used when the user mentions comprehensive code review, checking code quality, or reviewing staged changes with multi-phase analysis. This is the comprehensive review workflow, distinct from focused skills like frontend-code-review, staged-code-review, or code-change-test-designer.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-review-workflow\u002FSKILL.md",[146,149,152,153],{"categoryNo":147,"categoryName":148,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":150,"categoryName":151,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":64,"categoryName":65,"taxonomyType":66,"taxonomyTypeDesc":67},{"categoryNo":154,"categoryName":155,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000030","开发工程师",[157,18,128,158,159,160,161,162,163,164,165,166,167,168,169,170,171,172,173,174],"code review","code","code review workflow","testing","frontend","test","change","code quality","code-review","analysis","check","coverage","quality check","basic","multi","comprehensive code review","with","phase",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":190,"publishedAt":31},"01M6QJB7XNHV3VEEQF4W7FMWF6","code-change-test-designer","Analyzes code changes and designs comprehensive test cases. Reads diffs, summarizes capability changes, and designs test cases covering main flows and edge cases. Should be used when the user mentions test coverage, designing tests for code changes, or analyzing diff\u002Fcommit for testing purposes. Distinguished from code-review-workflow which provides comprehensive review, this skill focuses on test case design for code changes.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-change-test-designer\u002FSKILL.md",[181,182,185,186,187],{"categoryNo":150,"categoryName":151,"taxonomyType":66,"taxonomyTypeDesc":67},{"categoryNo":183,"categoryName":184,"taxonomyType":66,"taxonomyTypeDesc":67},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":64,"categoryName":65,"taxonomyType":66,"taxonomyTypeDesc":67},{"categoryNo":154,"categoryName":155,"taxonomyType":71,"taxonomyTypeDesc":72},{"categoryNo":188,"categoryName":189,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000032","设计师",[162,163,158,191,192,160,193,194,128,195,165,196,168,197,36,198,199,200,91,174],"designer","code change test designer","design","diffs","commit","edge","diff","tests","flows","which",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":208,"publishedAt":31},"01M6QJB195WD7DCJWDMKWKB29S","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmeta-skills\u002Fskill-creator\u002FSKILL.md",[207],{"categoryNo":64,"categoryName":65,"taxonomyType":66,"taxonomyTypeDesc":67},[209,210,211,212,129,213,214,215,216,217,166,218,219,220,36,221,222,88,91,203],"skill creator","creator","performance","run evals","variance analysis","create","run","benchmark","Meta","improve","edit","evals","optimize","existing skill"]