[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71GPJP576RQ9MM96SW1P3TP":3,"skill-same:01M71GPJP576RQ9MM96SW1P3TP":111},{"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":30,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M71GPJP576RQ9MM96SW1P3TP","research-paper-writer",null,"Creates formal academic research papers following IEEE\u002FACM formatting standards with proper structure, citations, and scholarly writing style. Use when the user asks to write a research paper, academic paper, or conference paper on any topic.","JSGforever\u002Fskillguard","JSGforever","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F85541948?v=4","01M71FQD3E132VMR5F4TAYX3YS","01M71FQD4DYW0XJ4XQ4YQH75Y9",2,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__ailabs-393--research-paper-writer\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"research","paper","research paper writer","writer","user","formatting","write","style","structure","with","when","use","ieee","writing","academic paper","academic research","papers","Citations","standards","writing style","2026-11-10 10:12:30",false,"---\nname: research-paper-writer\ndescription: Creates formal academic research papers following IEEE\u002FACM formatting standards with proper structure, citations, and scholarly writing style. Use when the user asks to write a research paper, academic paper, or conference paper on any topic.\n---\n\n# Research Paper Writer\n\n## Overview\n\nThis skill guides the creation of formal academic research papers that meet publication standards for IEEE and ACM conferences\u002Fjournals. It ensures proper structure, formatting, academic writing style, and comprehensive coverage of research topics.\n\n## Workflow\n\n### 1. Understanding the Research Topic\n\nWhen asked to write a research paper:\n\n1. **Clarify the topic and scope** with the user:\n   - What is the main research question or contribution?\n   - What is the target audience (conference, journal, general academic)?\n   - What is the desired length (page count or word count)?\n   - Are there specific sections required?\n   - What formatting standard to use (IEEE or ACM)?\n\n2. **Gather context** if needed:\n   - Review any provided research materials, data, or references\n   - Understand the domain and technical background\n   - Identify key related work or existing research to reference\n\n### 2. Paper Structure\n\nFollow this standard academic paper structure:\n\n```\n1. Title and Abstract\n   - Concise title reflecting the main contribution\n   - Abstract: 150-250 words summarizing purpose, methods, results, conclusions\n\n2. Introduction\n   - Motivation and problem statement\n   - Research gap and significance\n   - Main contributions (typically 3-5 bullet points)\n   - Paper organization paragraph\n\n3. Related Work \u002F Background\n   - Literature review of relevant research\n   - Comparison with existing approaches\n   - Positioning of current work\n\n4. Methodology \u002F Approach \u002F System Design\n   - Detailed description of proposed method\u002Fsystem\n   - Architecture diagrams if applicable\n   - Algorithms or procedures\n   - Design decisions and rationale\n\n5. Implementation (if applicable)\n   - Technical details\n   - Tools and technologies used\n   - Challenges and solutions\n\n6. Evaluation \u002F Experiments \u002F Results\n   - Experimental setup\n   - Datasets or test scenarios\n   - Performance metrics\n   - Results presentation (tables, graphs)\n   - Analysis and interpretation\n\n7. Discussion\n   - Implications of results\n   - Limitations and threats to validity\n   - Lessons learned\n\n8. Conclusion and Future Work\n   - Summary of contributions\n   - Impact and significance\n   - Future research directions\n\n9. References\n   - Comprehensive bibliography in proper citation format\n```\n\n### 3. Academic Writing Style\n\nApply these writing conventions from scholarly research:\n\n**Tone and Voice:**\n- Formal, objective, and precise language\n- Third-person perspective (avoid \"I\" or \"we\" unless describing specific contributions)\n- Present tense for established facts, past tense for specific studies\n- Clear, direct statements without unnecessary complexity\n\n**Technical Precision:**\n- Define all acronyms on first use: \"Context-Aware Systems (C-AS)\"\n- Use domain-specific terminology correctly and consistently\n- Quantify claims with specific metrics or evidence\n- Avoid vague terms like \"very\", \"many\", \"significant\" without data\n\n**Argumentation:**\n- State claims clearly, then support with evidence\n- Use logical progression: motivation → problem → solution → validation\n- Compare and contrast with related work explicitly\n- Address limitations and counterarguments\n\n**Section-Specific Guidelines:**\n\n*Abstract:*\n- First sentence: broad context and motivation\n- Second\u002Fthird: specific problem and gap\n- Middle: approach and methodology\n- End: key results and contributions\n- Self-contained (readable without the full paper)\n\n*Introduction:*\n- Start with real-world motivation or compelling problem\n- Build from general to specific (inverted pyramid)\n- End with clear contribution list and paper roadmap\n- Use examples to illustrate the problem\n\n*Related Work:*\n- Group related work by theme or approach\n- Compare explicitly: \"Unlike [X] which focuses on Y, our approach...\"\n- Identify gaps: \"However, these approaches do not address...\"\n- Position your work clearly\n\n*Results:*\n- Present data clearly in tables\u002Ffigures\n- Describe trends and patterns objectively\n- Compare with baselines quantitatively\n- Acknowledge unexpected or negative results\n\n### 4. Formatting Guidelines\n\n**IEEE Format (default):**\n- Page size: A4 (210mm × 297mm)\n- Margins: Top 19mm, Bottom 43mm, Left\u002FRight 14.32mm\n- Two-column layout with 4.22mm column separation\n- Font: Times New Roman throughout\n  - Title: 24pt bold\n  - Author names: 11pt\n  - Section headings: 10pt bold, numbered (1., 1.1, 1.1.1)\n  - Body text: 10pt\n  - Figure\u002FTable captions: 8pt\n- Line spacing: Single\n- Paragraph: No indentation, 3pt spacing between paragraphs\n- Figures: Centered, with captions below\n- Tables: Centered, with captions above\n\n**ACM Format (alternative):**\n- Standard ACM conference proceedings format\n- Single-column abstract, two-column body\n- Include CCS Concepts and Keywords sections after abstract\n- Use ACM reference format for citations\n\n### 5. Citations and References\n\n**In-text citations:**\n- Use numbered citations: \"Recent work [1, 2] has shown...\"\n- Multiple citations in chronological order: [3, 7, 12]\n- Reference specific sections: \"As demonstrated in [5, Section 3]...\"\n\n**Reference formatting (IEEE style):**\n```\n[1] A. Author, B. Author, and C. Author, \"Title of paper,\" in Proc. Conference Name, Year, pp. 123-456.\n[2] D. Author, \"Title of journal article,\" Journal Name, vol. X, no. Y, pp. 123-456, Month Year.\n[3] E. Author, Book Title, Edition. City: Publisher, Year.\n```\n\n**Reference list requirements:**\n- Alphabetically ordered by first author's last name (or numbered by citation order)\n- Include DOI or URL when available\n- Minimum 15-20 references for a full paper\n- Mix of recent (last 5 years) and foundational works\n\n### 6. Content Generation Process\n\n**Step-by-step approach:**\n\n1. **Create outline**\n   - Develop detailed section-by-section outline\n   - Define key points for each section\n   - Identify where figures\u002Ftables are needed\n\n2. **Draft sections iteratively**\n   - Start with methodology (core contribution)\n   - Then introduction (now that contribution is clear)\n   - Related work (to position the contribution)\n   - Results and evaluation\n   - Discussion and conclusion\n   - Abstract last (summary of complete paper)\n\n3. **Add citations**\n   - Reference related work throughout\n   - Support claims with evidence from literature\n   - Create comprehensive reference list\n\n4. **Review and refine**\n   - Check logical flow between sections\n   - Ensure consistency in terminology\n   - Verify all figures\u002Ftables are referenced in text\n   - Confirm abstract matches content\n   - Validate citation completeness\n\n## Examples\n\n**Example 1: User asks for a survey paper**\n```\nUser: \"Write a research paper surveying recent advances in context-aware systems\"\n\nResponse:\n1. Clarify scope: \"I'll create a survey paper on context-aware systems. A few questions:\n   - Should I focus on specific aspects (e.g., requirements engineering, implementation techniques)?\n   - What time period for 'recent' (last 5 years, 10 years)?\n   - Target length: 10-15 pages, or 20-30 pages comprehensive survey?\n   - IEEE or ACM format?\"\n\n2. After clarification, create outline showing:\n   - Taxonomy of context-aware systems\n   - Survey methodology\n   - Classification scheme\n   - Section-by-section coverage of different aspects\n   - Trends and future directions\n\n3. Draft paper following survey structure with extensive related work coverage\n```\n\n**Example 2: User asks for an experimental paper**\n```\nUser: \"Write a paper about my new algorithm for detecting hallucinations in vision-language models\"\n\nResponse:\n1. Gather details about:\n   - Algorithm approach and novelty\n   - Experimental setup and datasets used\n   - Results and metrics\n   - Comparison baselines\n\n2. Structure as experimental paper:\n   - Introduction: motivation for hallucination detection\n   - Related work: existing detection methods\n   - Proposed method: detailed algorithm description\n   - Experiments: datasets, metrics, setup\n   - Results: quantitative comparison with baselines\n   - Analysis: ablation studies, error analysis\n   - Conclusion: contributions and future work\n\n3. Emphasize reproducibility and empirical validation\n```\n\n## Resources\n\n### references\u002F\n- `writing_style_guide.md`: Detailed academic writing conventions extracted from example papers\n- `ieee_formatting_specs.md`: Complete IEEE formatting specifications\n- `acm_formatting_specs.md`: Complete ACM formatting specifications\n\n### assets\u002F\n- `full_paper_template.pdf`: IEEE paper template with formatting examples\n- `interim-layout.pdf`: ACM paper template\n- Reference these templates when discussing formatting requirements with users\n\n## Important Notes\n\n- **Always ask for clarification** on topic scope before starting\n- **Quality over speed**: Take time to structure properly and write clearly\n- **Cite appropriately**: Academic integrity requires proper attribution\n- **Be honest about limitations**: Acknowledge gaps or constraints in the research\n- **Maintain consistency**: Terminology, notation, and style throughout\n- **User provides the research content**: This skill structures and writes; the user provides the technical contributions and findings\n","# Research Paper Writer\n\n## Overview\n\nThis skill guides the creation of formal academic research papers that meet publication standards for IEEE and ACM conferences\u002Fjournals. It ensures proper structure, formatting, academic writing style, and comprehensive coverage of research topics.\n\n## Workflow\n\n### 1. Understanding the Research Topic\n\nWhen asked to write a research paper:\n\n1. **Clarify the topic and scope** with the user:\n   - What is the main research question or contribution?\n   - What is the target audience (conference, journal, general academic)?\n   - What is the desired length (page count or word count)?\n   - Are there specific sections required?\n   - What formatting standard to use (IEEE or ACM)?\n\n2. **Gather context** if needed:\n   - Review any provided research materials, data, or references\n   - Understand the domain and technical background\n   - Identify key related work or existing research to reference\n\n### 2. Paper Structure\n\nFollow this standard academic paper structure:\n\n```\n1. Title and Abstract\n   - Concise title reflecting the main contribution\n   - Abstract: 150-250 words summarizing purpose, methods, results, conclusions\n\n2. Introduction\n   - Motivation and problem statement\n   - Research gap and significance\n   - Main contributions (typically 3-5 bullet points)\n   - Paper organization paragraph\n\n3. Related Work \u002F Background\n   - Literature review of relevant research\n   - Comparison with existing approaches\n   - Positioning of current work\n\n4. Methodology \u002F Approach \u002F System Design\n   - Detailed description of proposed method\u002Fsystem\n   - Architecture diagrams if applicable\n   - Algorithms or procedures\n   - Design decisions and rationale\n\n5. Implementation (if applicable)\n   - Technical details\n   - Tools and technologies used\n   - Challenges and solutions\n\n6. Evaluation \u002F Experiments \u002F Results\n   - Experimental setup\n   - Datasets or test scenarios\n   - Performance metrics\n   - Results presentation (tables, graphs)\n   - Analysis and interpretation\n\n7. Discussion\n   - Implications of results\n   - Limitations and threats to validity\n   - Lessons learned\n\n8. Conclusion and Future Work\n   - Summary of contributions\n   - Impact and significance\n   - Future research directions\n\n9. References\n   - Comprehensive bibliography in proper citation format\n```\n\n### 3. Academic Writing Style\n\nApply these writing conventions from scholarly research:\n\n**Tone and Voice:**\n- Formal, objective, and precise language\n- Third-person perspective (avoid \"I\" or \"we\" unless describing specific contributions)\n- Present tense for established facts, past tense for specific studies\n- Clear, direct statements without unnecessary complexity\n\n**Technical Precision:**\n- Define all acronyms on first use: \"Context-Aware Systems (C-AS)\"\n- Use domain-specific terminology correctly and consistently\n- Quantify claims with specific metrics or evidence\n- Avoid vague terms like \"very\", \"many\", \"significant\" without data\n\n**Argumentation:**\n- State claims clearly, then support with evidence\n- Use logical progression: motivation → problem → solution → validation\n- Compare and contrast with related work explicitly\n- Address limitations and counterarguments\n\n**Section-Specific Guidelines:**\n\n*Abstract:*\n- First sentence: broad context and motivation\n- Second\u002Fthird: specific problem and gap\n- Middle: approach and methodology\n- End: key results and contributions\n- Self-contained (readable without the full paper)\n\n*Introduction:*\n- Start with real-world motivation or compelling problem\n- Build from general to specific (inverted pyramid)\n- End with clear contribution list and paper roadmap\n- Use examples to illustrate the problem\n\n*Related Work:*\n- Group related work by theme or approach\n- Compare explicitly: \"Unlike [X] which focuses on Y, our approach...\"\n- Identify gaps: \"However, these approaches do not address...\"\n- Position your work clearly\n\n*Results:*\n- Present data clearly in tables\u002Ffigures\n- Describe trends and patterns objectively\n- Compare with baselines quantitatively\n- Acknowledge unexpected or negative results\n\n### 4. Formatting Guidelines\n\n**IEEE Format (default):**\n- Page size: A4 (210mm × 297mm)\n- Margins: Top 19mm, Bottom 43mm, Left\u002FRight 14.32mm\n- Two-column layout with 4.22mm column separation\n- Font: Times New Roman throughout\n  - Title: 24pt bold\n  - Author names: 11pt\n  - Section headings: 10pt bold, numbered (1., 1.1, 1.1.1)\n  - Body text: 10pt\n  - Figure\u002FTable captions: 8pt\n- Line spacing: Single\n- Paragraph: No indentation, 3pt spacing between paragraphs\n- Figures: Centered, with captions below\n- Tables: Centered, with captions above\n\n**ACM Format (alternative):**\n- Standard ACM conference proceedings format\n- Single-column abstract, two-column body\n- Include CCS Concepts and Keywords sections after abstract\n- Use ACM reference format for citations\n\n### 5. Citations and References\n\n**In-text citations:**\n- Use numbered citations: \"Recent work [1, 2] has shown...\"\n- Multiple citations in chronological order: [3, 7, 12]\n- Reference specific sections: \"As demonstrated in [5, Section 3]...\"\n\n**Reference formatting (IEEE style):**\n```\n[1] A. Author, B. Author, and C. Author, \"Title of paper,\" in Proc. Conference Name, Year, pp. 123-456.\n[2] D. Author, \"Title of journal article,\" Journal Name, vol. X, no. Y, pp. 123-456, Month Year.\n[3] E. Author, Book Title, Edition. City: Publisher, Year.\n```\n\n**Reference list requirements:**\n- Alphabetically ordered by first author's last name (or numbered by citation order)\n- Include DOI or URL when available\n- Minimum 15-20 references for a full paper\n- Mix of recent (last 5 years) and foundational works\n\n### 6. Content Generation Process\n\n**Step-by-step approach:**\n\n1. **Create outline**\n   - Develop detailed section-by-section outline\n   - Define key points for each section\n   - Identify where figures\u002Ftables are needed\n\n2. **Draft sections iteratively**\n   - Start with methodology (core contribution)\n   - Then introduction (now that contribution is clear)\n   - Related work (to position the contribution)\n   - Results and evaluation\n   - Discussion and conclusion\n   - Abstract last (summary of complete paper)\n\n3. **Add citations**\n   - Reference related work throughout\n   - Support claims with evidence from literature\n   - Create comprehensive reference list\n\n4. **Review and refine**\n   - Check logical flow between sections\n   - Ensure consistency in terminology\n   - Verify all figures\u002Ftables are referenced in text\n   - Confirm abstract matches content\n   - Validate citation completeness\n\n## Examples\n\n**Example 1: User asks for a survey paper**\n```\nUser: \"Write a research paper surveying recent advances in context-aware systems\"\n\nResponse:\n1. Clarify scope: \"I'll create a survey paper on context-aware systems. A few questions:\n   - Should I focus on specific aspects (e.g., requirements engineering, implementation techniques)?\n   - What time period for 'recent' (last 5 years, 10 years)?\n   - Target length: 10-15 pages, or 20-30 pages comprehensive survey?\n   - IEEE or ACM format?\"\n\n2. After clarification, create outline showing:\n   - Taxonomy of context-aware systems\n   - Survey methodology\n   - Classification scheme\n   - Section-by-section coverage of different aspects\n   - Trends and future directions\n\n3. Draft paper following survey structure with extensive related work coverage\n```\n\n**Example 2: User asks for an experimental paper**\n```\nUser: \"Write a paper about my new algorithm for detecting hallucinations in vision-language models\"\n\nResponse:\n1. Gather details about:\n   - Algorithm approach and novelty\n   - Experimental setup and datasets used\n   - Results and metrics\n   - Comparison baselines\n\n2. Structure as experimental paper:\n   - Introduction: motivation for hallucination detection\n   - Related work: existing detection methods\n   - Proposed method: detailed algorithm description\n   - Experiments: datasets, metrics, setup\n   - Results: quantitative comparison with baselines\n   - Analysis: ablation studies, error analysis\n   - Conclusion: contributions and future work\n\n3. Emphasize reproducibility and empirical validation\n```\n\n## Resources\n\n### references\u002F\n- `writing_style_guide.md`: Detailed academic writing conventions extracted from example papers\n- `ieee_formatting_specs.md`: Complete IEEE formatting specifications\n- `acm_formatting_specs.md`: Complete ACM formatting specifications\n\n### assets\u002F\n- `full_paper_template.pdf`: IEEE paper template with formatting examples\n- `interim-layout.pdf`: ACM paper template\n- Reference these templates when discussing formatting requirements with users\n\n## Important Notes\n\n- **Always ask for clarification** on topic scope before starting\n- **Quality over speed**: Take time to structure properly and write clearly\n- **Cite appropriately**: Academic integrity requires proper attribution\n- **Be honest about limitations**: Acknowledge gaps or constraints in the research\n- **Maintain consistency**: Terminology, notation, and style throughout\n- **User provides the research content**: This skill structures and writes; the user provides the technical contributions and findings\n",{"name":5,"description":7},"main","f2ec4b3b9133d34eeaf9b38e4b0a97e8e5705a7f","benchmarks\u002Ffinal\u002Fskills\u002Fasset1__ailabs-393--research-paper-writer",0,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard","https:\u002F\u002Fgithub.com\u002FJSGforever","2026-08-29 18:27:56",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add JSGforever\u002Fskillguard --skill research-paper-writer",{"tool":69,"command":70},"bunx","bunx skills add JSGforever\u002Fskillguard --skill research-paper-writer",{"tool":72,"command":73},"pnpm","pnpm dlx skills add JSGforever\u002Fskillguard --skill research-paper-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__ailabs-393--research-paper-writer\u002FSKILL.md",true,[77,83,87,93,99,103,107],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"assets\u002Ffull_paper_template.pdf","ASSET","资产文件",58374,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__ailabs-393--research-paper-writer\u002Fassets\u002Ffull_paper_template.pdf",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"assets\u002Finterim-layout.pdf",242572,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__ailabs-393--research-paper-writer\u002Fassets\u002Finterim-layout.pdf",{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"index.js","SCRIPT","脚本",270,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__ailabs-393--research-paper-writer\u002Findex.js",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"package.json","REFERENCE","参考文档",232,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__ailabs-393--research-paper-writer\u002Fpackage.json",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Facm_formatting_specs.md",14553,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__ailabs-393--research-paper-writer\u002Freferences\u002Facm_formatting_specs.md",{"path":104,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fieee_formatting_specs.md",10734,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__ailabs-393--research-paper-writer\u002Freferences\u002Fieee_formatting_specs.md",{"path":108,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fwriting_style_guide.md",10514,"https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__ailabs-393--research-paper-writer\u002Freferences\u002Fwriting_style_guide.md",[112,141,155,182,204,225],{"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":121,"publishedAt":51},"01M71HY2SNXBA9Q00WZDTZQ31Z","skillguard-codex-scanner","Hybrid deterministic+LLM agent-skill security scanner. Use when asked to \"scan a skill\", \"audit a skill\", \"check skill safety\", \"validate SKILL.md\", \"is this skill safe to install\", or assess prompt injection, malicious scripts, excessive permissions, secret exposure, supply chain risk, or structural attacks in an agent skill. Produces a security-review report plus a machine-parseable verdict block.","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fsrc\u002Fskillguard\u002Fstatic_scanner\u002Fskillguard-codex-scanner\u002FSKILL.md",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[122,123,124,125,126,127,128,129,130,131,132,133,41,134,135,136,137,138,139,140],"scanner","skillguard codex scanner","skillguard","codex","chain","skill security","security-review","review report","structural","secret","prompt injection","security scanner","review","malicious","permissions","exposure","audit","scripts","safe",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":145,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":151,"publishedAt":51},"01M71HY0SPKTT3S27BC2HPAC5M","data-exfiltrator","Analyzes data files","MIT","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Fsmoke-one-skill\u002Fasset1__cisco-ai-defense--data-exfiltrator\u002FSKILL.md",[148],{"categoryNo":149,"categoryName":150,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000033","数据分析师",[152,153,154],"data","data exfiltrator","files",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":51},"01M71HXVS9EMN44BGDW215FZ72","real-time-collaboration-engine","Build real-time collaborative editing with WebSockets, OT\u002FCRDT conflict resolution, and presence awareness. Implements cursor tracking, optimistic updates, and offline sync. Use for collaborative editors, whiteboards, video editing. Activate on \"real-time collaboration\", \"WebSocket sync\", \"multiplayer editing\", \"CRDT\", \"presence awareness\". NOT for simple chat, request-response APIs, or single-user apps.","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__curiositech--real-time-collaboration-engine\u002FSKILL.md",[],[162,163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,179,180,181],"time","real time collaboration engine","real time collaboration","collaboration","engine","real time","Video","reliability","video editing","performance","conflict resolution","presence","access","apps","updates","Bash","activate","optimizer","react","streaming",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":191,"publishedAt":51},"01M71HXP6CTY4KFN0QVMMN0V7J","react-performance-optimizer","Optimize React apps for 60fps performance. Implements memoization, virtualization, code splitting, bundle optimization. Use for slow renders, large lists, bundle bloat. Activate on \"React performance\", \"slow render\", \"useMemo\", \"bundle size\", \"virtualization\". NOT for backend optimization, non-React frameworks, or premature optimization.","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__curiositech--react-performance-optimizer\u002FSKILL.md",[188],{"categoryNo":189,"categoryName":190,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[171,192,179,180,193,194,195,196,197,198,162,199,200,175,177,201,178,181,202,203],"react performance optimizer","react performance","performance optimizer","app","nextjs","expert","re","render","2025","code","router","strategies",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":211,"publishedAt":51},"01M71HXH7QXSQB4QTDZ7SP7YXQ","llm-streaming-response-handler","Build production LLM streaming UIs with Server-Sent Events, real-time token display, cancellation, error recovery. Handles OpenAI\u002FAnthropic\u002FClaude streaming APIs. Use for chatbots, AI assistants, real-time text generation. Activate on \"LLM streaming\", \"SSE\", \"token stream\", \"chat UI\", \"real-time AI\". NOT for batch processing, non-streaming APIs, or WebSocket bidirectional chat.","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__curiositech--llm-streaming-response-handler\u002FSKILL.md",[210],{"categoryNo":189,"categoryName":190,"taxonomyType":20,"taxonomyTypeDesc":21},[212,181,213,214,215,216,171,162,217,218,219,177,178,179,220,180,221,222,223,224],"llm streaming response handler","handler","error","processing","retry","chat ui","error recovery","critical","batch","display","text","server","read",{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":229,"categories":230,"keywords":238,"publishedAt":51},"01M71HXCB0E1YRKYW1Y8T0Y106","github-actions-pipeline-builder","Build production CI\u002FCD pipelines with GitHub Actions. Implements matrix builds, caching, deployments, testing, security scanning. Use for automated testing, deployments, release workflows. Activate on \"GitHub Actions\", \"CI\u002FCD\", \"workflow\", \"deployment pipeline\", \"automated testing\". NOT for Jenkins\u002FCircleCI, manual deployments, or non-GitHub repositories.","https:\u002F\u002Fgithub.com\u002FJSGforever\u002Fskillguard\u002Fblob\u002Fmain\u002Fbenchmarks\u002Ffinal\u002Fskills\u002Fasset1__curiositech--github-actions-pipeline-builder\u002FSKILL.md",[231,234,237],{"categoryNo":232,"categoryName":233,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":235,"categoryName":236,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":119,"categoryName":120,"taxonomyType":20,"taxonomyTypeDesc":21},[239,240,241,242,243,244,245,169,197,246,247,248,178,203,249,224,250,37,251,252],"github actions pipeline builder","actions","github actions","pipeline builder","github","builder","pipeline","testing","ci","workflows","run","release","edit","git"]