[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KBY7JFEQ26R0HA8KSSJ4ZD":3,"skill-same:01M6KBY7JFEQ26R0HA8KSSJ4ZD":90},{"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":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6KBY7JFEQ26R0HA8KSSJ4ZD","confluence-expert",null,"Atlassian Confluence expert for creating and managing spaces, knowledge bases, and documentation. Configures space permissions and hierarchies, creates page templates with macros, sets up documentation taxonomies, designs page layouts, and manages content governance. Use when users need to build or restructure a Confluence space, design page hierarchies with permission structures, author or standardise documentation templates, embed Jira reports in pages, run knowledge base audits, or establish documentation standards and collaborative workflows.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproject-management\u002Fconfluence-expert\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"expert","confluence","confluence expert","atlassian","for","Documentation Standards","knowledge base","permission","content governance","reports","standards","up","design","knowledge","documentation templates","permissions","run","jira","documentation","workflows","2026-11-10 10:12:30",false,"---\nname: \"confluence-expert\"\ndescription: Atlassian Confluence expert for creating and managing spaces, knowledge bases, and documentation. Configures space permissions and hierarchies, creates page templates with macros, sets up documentation taxonomies, designs page layouts, and manages content governance. Use when users need to build or restructure a Confluence space, design page hierarchies with permission structures, author or standardise documentation templates, embed Jira reports in pages, run knowledge base audits, or establish documentation standards and collaborative workflows.\n---\n\n# Atlassian Confluence Expert\n\nMaster-level expertise in Confluence space management, documentation architecture, content creation, macros, templates, and collaborative knowledge management.\n\n## Atlassian MCP Integration\n\n**Primary Tool**: Confluence MCP Server\n\n**Key Operations**:\n\n```\n\u002F\u002F Create a new space\ncreate_space({ key: \"TEAM\", name: \"Engineering Team\", description: \"Engineering team knowledge base\" })\n\n\u002F\u002F Create a page under a parent\ncreate_page({ spaceKey: \"TEAM\", title: \"Sprint 42 Notes\", parentId: \"123456\", body: \"\u003Cp>Meeting notes in storage-format HTML\u003C\u002Fp>\" })\n\n\u002F\u002F Update an existing page (version must be incremented)\nupdate_page({ pageId: \"789012\", version: 4, body: \"\u003Cp>Updated content\u003C\u002Fp>\" })\n\n\u002F\u002F Delete a page\ndelete_page({ pageId: \"789012\" })\n\n\u002F\u002F Search with CQL\nsearch({ cql: 'space = \"TEAM\" AND label = \"meeting-notes\" ORDER BY lastModified DESC' })\n\n\u002F\u002F Retrieve child pages for hierarchy inspection\nget_children({ pageId: \"123456\" })\n\n\u002F\u002F Apply a label to a page\nadd_label({ pageId: \"789012\", label: \"archived\" })\n```\n\n**Integration Points**:\n- Create documentation for Senior PM projects\n- Support Scrum Master with ceremony templates\n- Link to Jira issues for Jira Expert\n- Provide templates for Template Creator\n\n> **See also**: `MACROS.md` for macro syntax reference, `TEMPLATES.md` for full template library, `PERMISSIONS.md` for permission scheme details.\n\n## Workflows\n\n### Space Creation\n1. Determine space type (Team, Project, Knowledge Base, Personal)\n2. Create space with clear name and description\n3. Set space homepage with overview\n4. Configure space permissions:\n   - View, Edit, Create, Delete\n   - Admin privileges\n5. Create initial page tree structure\n6. Add space shortcuts for navigation\n7. **Verify**: Navigate to the space URL and confirm the homepage loads; check that a non-admin test user sees the correct permission level\n8. **HANDOFF TO**: Teams for content population\n\n### Page Architecture\n**Best Practices**:\n- Use page hierarchy (parent-child relationships)\n- Maximum 3 levels deep for navigation\n- Consistent naming conventions\n- Date-stamp meeting notes\n\n**Recommended Structure**:\n```\nSpace Home\n├── Overview & Getting Started\n├── Team Information\n│   ├── Team Members & Roles\n│   ├── Communication Channels\n│   └── Working Agreements\n├── Projects\n│   ├── Project A\n│   │   ├── Overview\n│   │   ├── Requirements\n│   │   └── Meeting Notes\n│   └── Project B\n├── Processes & Workflows\n├── Meeting Notes (Archive)\n└── Resources & References\n```\n\n### Template Creation\n1. Identify repeatable content pattern\n2. Create page with structure and placeholders\n3. Add instructions in placeholders\n4. Format with appropriate macros\n5. Save as template\n6. Share with space or make global\n7. **Verify**: Create a test page from the template and confirm all placeholders render correctly before sharing with the team\n8. **USE**: References for advanced template patterns\n\n### Documentation Strategy\n1. **Assess** current documentation state\n2. **Define** documentation goals and audience\n3. **Organize** content taxonomy and structure\n4. **Create** templates and guidelines\n5. **Migrate** existing documentation\n6. **Train** teams on best practices\n7. **Monitor** usage and adoption\n8. **REPORT TO**: Senior PM on documentation health\n\n### Knowledge Base Management\n**Article Types**:\n- How-to guides\n- Troubleshooting docs\n- FAQs\n- Reference documentation\n- Process documentation\n\n**Quality Standards**:\n- Clear title and description\n- Structured with headings\n- Updated date visible\n- Owner identified\n- Reviewed quarterly\n\n## Essential Macros\n\n> Full macro reference with all parameters: see `MACROS.md`.\n\n### Content Macros\n**Info, Note, Warning, Tip**:\n```\n{info}\nImportant information here\n{info}\n```\n\n**Expand**:\n```\n{expand:title=Click to expand}\nHidden content here\n{expand}\n```\n\n**Table of Contents**:\n```\n{toc:maxLevel=3}\n```\n\n**Excerpt & Excerpt Include**:\n```\n{excerpt}\nReusable content\n{excerpt}\n\n{excerpt-include:Page Name}\n```\n\n### Dynamic Content\n**Jira Issues**:\n```\n{jira:JQL=project = PROJ AND status = \"In Progress\"}\n```\n\n**Jira Chart**:\n```\n{jirachart:type=pie|jql=project = PROJ|statType=statuses}\n```\n\n**Recently Updated**:\n```\n{recently-updated:spaces=@all|max=10}\n```\n\n**Content by Label**:\n```\n{contentbylabel:label=meeting-notes|maxResults=20}\n```\n\n### Collaboration Macros\n**Status**:\n```\n{status:colour=Green|title=Approved}\n```\n\n**Task List**:\n```\n{tasks}\n- [ ] Task 1\n- [x] Task 2 completed\n{tasks}\n```\n\n**User Mention**:\n```\n@username\n```\n\n**Date**:\n```\n{date:format=dd MMM yyyy}\n```\n\n## Page Layouts & Formatting\n\n**Two-Column Layout**:\n```\n{section}\n{column:width=50%}\nLeft content\n{column}\n{column:width=50%}\nRight content\n{column}\n{section}\n```\n\n**Panel**:\n```\n{panel:title=Panel Title|borderColor=#ccc}\nPanel content\n{panel}\n```\n\n**Code Block**:\n```\n{code:javascript}\nconst example = \"code here\";\n{code}\n```\n\n## Templates Library\n\n> Full template library with complete markup: see `TEMPLATES.md`. Key templates summarised below.\n\n| Template | Purpose | Key Sections |\n|----------|---------|--------------|\n| **Meeting Notes** | Sprint\u002Fteam meetings | Agenda, Discussion, Decisions, Action Items (tasks macro) |\n| **Project Overview** | Project kickoff & status | Quick Facts panel, Objectives, Stakeholders table, Milestones (Jira macro), Risks |\n| **Decision Log** | Architectural\u002Fstrategic decisions | Context, Options Considered, Decision, Consequences, Next Steps |\n| **Sprint Retrospective** | Agile ceremony docs | What Went Well (info), What Didn't (warning), Action Items (tasks), Metrics |\n\n## Space Permissions\n\n> Full permission scheme details: see `PERMISSIONS.md`.\n\n### Permission Schemes\n**Public Space**:\n- All users: View\n- Team members: Edit, Create\n- Space admins: Admin\n\n**Team Space**:\n- Team members: View, Edit, Create\n- Team leads: Admin\n- Others: No access\n\n**Project Space**:\n- Stakeholders: View\n- Project team: Edit, Create\n- PM: Admin\n\n## Content Governance\n\n**Review Cycles**:\n- Critical docs: Monthly\n- Standard docs: Quarterly\n- Archive docs: Annually\n\n**Archiving Strategy**:\n- Move outdated content to Archive space\n- Label with \"archived\" and date\n- Maintain for 2 years, then delete\n- Keep audit trail\n\n**Content Quality Checklist**:\n- [ ] Clear, descriptive title\n- [ ] Owner\u002Fauthor identified\n- [ ] Last updated date visible\n- [ ] Appropriate labels applied\n- [ ] Links functional\n- [ ] Formatting consistent\n- [ ] No sensitive data exposed\n\n## Decision Framework\n\n**When to Escalate to Atlassian Admin**:\n- Need org-wide template\n- Require cross-space permissions\n- Blueprint configuration\n- Global automation rules\n- Space export\u002Fimport\n\n**When to Collaborate with Jira Expert**:\n- Embed Jira queries and charts\n- Link pages to Jira issues\n- Create Jira-based reports\n- Sync documentation with tickets\n\n**When to Support Scrum Master**:\n- Sprint documentation templates\n- Retrospective pages\n- Team working agreements\n- Process documentation\n\n**When to Support Senior PM**:\n- Executive report pages\n- Portfolio documentation\n- Stakeholder communication\n- Strategic planning docs\n\n## Handoff Protocols\n\n**FROM Senior PM**:\n- Documentation requirements\n- Space structure needs\n- Template requirements\n- Knowledge management strategy\n\n**TO Senior PM**:\n- Documentation coverage reports\n- Content usage analytics\n- Knowledge gaps identified\n- Template adoption metrics\n\n**FROM Scrum Master**:\n- Sprint ceremony templates\n- Team documentation needs\n- Meeting notes structure\n- Retrospective format\n\n**TO Scrum Master**:\n- Configured templates\n- Space for team docs\n- Training on best practices\n- Documentation guidelines\n\n**WITH Jira Expert**:\n- Jira-Confluence linking\n- Embedded Jira reports\n- Issue-to-page connections\n- Cross-tool workflow\n\n## Best Practices\n\n**Organization**:\n- Consistent naming conventions\n- Meaningful labels\n- Logical page hierarchy\n- Related pages linked\n- Clear navigation\n\n**Maintenance**:\n- Regular content audits\n- Remove duplication\n- Update outdated information\n- Archive obsolete content\n- Monitor page analytics\n\n## Analytics & Metrics\n\n**Usage Metrics**:\n- Page views per space\n- Most visited pages\n- Search queries\n- Contributor activity\n- Orphaned pages\n\n**Health Indicators**:\n- Pages without recent updates\n- Pages without owners\n- Duplicate content\n- Broken links\n- Empty spaces\n\n## Related Skills\n\n- **Jira Expert** (`project-management\u002Fjira-expert\u002F`) — Jira issue macros and linking complement Confluence docs\n- **Atlassian Templates** (`project-management\u002Fatlassian-templates\u002F`) — Template patterns for Confluence content creation\n","# Atlassian Confluence Expert\n\nMaster-level expertise in Confluence space management, documentation architecture, content creation, macros, templates, and collaborative knowledge management.\n\n## Atlassian MCP Integration\n\n**Primary Tool**: Confluence MCP Server\n\n**Key Operations**:\n\n```\n\u002F\u002F Create a new space\ncreate_space({ key: \"TEAM\", name: \"Engineering Team\", description: \"Engineering team knowledge base\" })\n\n\u002F\u002F Create a page under a parent\ncreate_page({ spaceKey: \"TEAM\", title: \"Sprint 42 Notes\", parentId: \"123456\", body: \"\u003Cp>Meeting notes in storage-format HTML\u003C\u002Fp>\" })\n\n\u002F\u002F Update an existing page (version must be incremented)\nupdate_page({ pageId: \"789012\", version: 4, body: \"\u003Cp>Updated content\u003C\u002Fp>\" })\n\n\u002F\u002F Delete a page\ndelete_page({ pageId: \"789012\" })\n\n\u002F\u002F Search with CQL\nsearch({ cql: 'space = \"TEAM\" AND label = \"meeting-notes\" ORDER BY lastModified DESC' })\n\n\u002F\u002F Retrieve child pages for hierarchy inspection\nget_children({ pageId: \"123456\" })\n\n\u002F\u002F Apply a label to a page\nadd_label({ pageId: \"789012\", label: \"archived\" })\n```\n\n**Integration Points**:\n- Create documentation for Senior PM projects\n- Support Scrum Master with ceremony templates\n- Link to Jira issues for Jira Expert\n- Provide templates for Template Creator\n\n> **See also**: `MACROS.md` for macro syntax reference, `TEMPLATES.md` for full template library, `PERMISSIONS.md` for permission scheme details.\n\n## Workflows\n\n### Space Creation\n1. Determine space type (Team, Project, Knowledge Base, Personal)\n2. Create space with clear name and description\n3. Set space homepage with overview\n4. Configure space permissions:\n   - View, Edit, Create, Delete\n   - Admin privileges\n5. Create initial page tree structure\n6. Add space shortcuts for navigation\n7. **Verify**: Navigate to the space URL and confirm the homepage loads; check that a non-admin test user sees the correct permission level\n8. **HANDOFF TO**: Teams for content population\n\n### Page Architecture\n**Best Practices**:\n- Use page hierarchy (parent-child relationships)\n- Maximum 3 levels deep for navigation\n- Consistent naming conventions\n- Date-stamp meeting notes\n\n**Recommended Structure**:\n```\nSpace Home\n├── Overview & Getting Started\n├── Team Information\n│   ├── Team Members & Roles\n│   ├── Communication Channels\n│   └── Working Agreements\n├── Projects\n│   ├── Project A\n│   │   ├── Overview\n│   │   ├── Requirements\n│   │   └── Meeting Notes\n│   └── Project B\n├── Processes & Workflows\n├── Meeting Notes (Archive)\n└── Resources & References\n```\n\n### Template Creation\n1. Identify repeatable content pattern\n2. Create page with structure and placeholders\n3. Add instructions in placeholders\n4. Format with appropriate macros\n5. Save as template\n6. Share with space or make global\n7. **Verify**: Create a test page from the template and confirm all placeholders render correctly before sharing with the team\n8. **USE**: References for advanced template patterns\n\n### Documentation Strategy\n1. **Assess** current documentation state\n2. **Define** documentation goals and audience\n3. **Organize** content taxonomy and structure\n4. **Create** templates and guidelines\n5. **Migrate** existing documentation\n6. **Train** teams on best practices\n7. **Monitor** usage and adoption\n8. **REPORT TO**: Senior PM on documentation health\n\n### Knowledge Base Management\n**Article Types**:\n- How-to guides\n- Troubleshooting docs\n- FAQs\n- Reference documentation\n- Process documentation\n\n**Quality Standards**:\n- Clear title and description\n- Structured with headings\n- Updated date visible\n- Owner identified\n- Reviewed quarterly\n\n## Essential Macros\n\n> Full macro reference with all parameters: see `MACROS.md`.\n\n### Content Macros\n**Info, Note, Warning, Tip**:\n```\n{info}\nImportant information here\n{info}\n```\n\n**Expand**:\n```\n{expand:title=Click to expand}\nHidden content here\n{expand}\n```\n\n**Table of Contents**:\n```\n{toc:maxLevel=3}\n```\n\n**Excerpt & Excerpt Include**:\n```\n{excerpt}\nReusable content\n{excerpt}\n\n{excerpt-include:Page Name}\n```\n\n### Dynamic Content\n**Jira Issues**:\n```\n{jira:JQL=project = PROJ AND status = \"In Progress\"}\n```\n\n**Jira Chart**:\n```\n{jirachart:type=pie|jql=project = PROJ|statType=statuses}\n```\n\n**Recently Updated**:\n```\n{recently-updated:spaces=@all|max=10}\n```\n\n**Content by Label**:\n```\n{contentbylabel:label=meeting-notes|maxResults=20}\n```\n\n### Collaboration Macros\n**Status**:\n```\n{status:colour=Green|title=Approved}\n```\n\n**Task List**:\n```\n{tasks}\n- [ ] Task 1\n- [x] Task 2 completed\n{tasks}\n```\n\n**User Mention**:\n```\n@username\n```\n\n**Date**:\n```\n{date:format=dd MMM yyyy}\n```\n\n## Page Layouts & Formatting\n\n**Two-Column Layout**:\n```\n{section}\n{column:width=50%}\nLeft content\n{column}\n{column:width=50%}\nRight content\n{column}\n{section}\n```\n\n**Panel**:\n```\n{panel:title=Panel Title|borderColor=#ccc}\nPanel content\n{panel}\n```\n\n**Code Block**:\n```\n{code:javascript}\nconst example = \"code here\";\n{code}\n```\n\n## Templates Library\n\n> Full template library with complete markup: see `TEMPLATES.md`. Key templates summarised below.\n\n| Template | Purpose | Key Sections |\n|----------|---------|--------------|\n| **Meeting Notes** | Sprint\u002Fteam meetings | Agenda, Discussion, Decisions, Action Items (tasks macro) |\n| **Project Overview** | Project kickoff & status | Quick Facts panel, Objectives, Stakeholders table, Milestones (Jira macro), Risks |\n| **Decision Log** | Architectural\u002Fstrategic decisions | Context, Options Considered, Decision, Consequences, Next Steps |\n| **Sprint Retrospective** | Agile ceremony docs | What Went Well (info), What Didn't (warning), Action Items (tasks), Metrics |\n\n## Space Permissions\n\n> Full permission scheme details: see `PERMISSIONS.md`.\n\n### Permission Schemes\n**Public Space**:\n- All users: View\n- Team members: Edit, Create\n- Space admins: Admin\n\n**Team Space**:\n- Team members: View, Edit, Create\n- Team leads: Admin\n- Others: No access\n\n**Project Space**:\n- Stakeholders: View\n- Project team: Edit, Create\n- PM: Admin\n\n## Content Governance\n\n**Review Cycles**:\n- Critical docs: Monthly\n- Standard docs: Quarterly\n- Archive docs: Annually\n\n**Archiving Strategy**:\n- Move outdated content to Archive space\n- Label with \"archived\" and date\n- Maintain for 2 years, then delete\n- Keep audit trail\n\n**Content Quality Checklist**:\n- [ ] Clear, descriptive title\n- [ ] Owner\u002Fauthor identified\n- [ ] Last updated date visible\n- [ ] Appropriate labels applied\n- [ ] Links functional\n- [ ] Formatting consistent\n- [ ] No sensitive data exposed\n\n## Decision Framework\n\n**When to Escalate to Atlassian Admin**:\n- Need org-wide template\n- Require cross-space permissions\n- Blueprint configuration\n- Global automation rules\n- Space export\u002Fimport\n\n**When to Collaborate with Jira Expert**:\n- Embed Jira queries and charts\n- Link pages to Jira issues\n- Create Jira-based reports\n- Sync documentation with tickets\n\n**When to Support Scrum Master**:\n- Sprint documentation templates\n- Retrospective pages\n- Team working agreements\n- Process documentation\n\n**When to Support Senior PM**:\n- Executive report pages\n- Portfolio documentation\n- Stakeholder communication\n- Strategic planning docs\n\n## Handoff Protocols\n\n**FROM Senior PM**:\n- Documentation requirements\n- Space structure needs\n- Template requirements\n- Knowledge management strategy\n\n**TO Senior PM**:\n- Documentation coverage reports\n- Content usage analytics\n- Knowledge gaps identified\n- Template adoption metrics\n\n**FROM Scrum Master**:\n- Sprint ceremony templates\n- Team documentation needs\n- Meeting notes structure\n- Retrospective format\n\n**TO Scrum Master**:\n- Configured templates\n- Space for team docs\n- Training on best practices\n- Documentation guidelines\n\n**WITH Jira Expert**:\n- Jira-Confluence linking\n- Embedded Jira reports\n- Issue-to-page connections\n- Cross-tool workflow\n\n## Best Practices\n\n**Organization**:\n- Consistent naming conventions\n- Meaningful labels\n- Logical page hierarchy\n- Related pages linked\n- Clear navigation\n\n**Maintenance**:\n- Regular content audits\n- Remove duplication\n- Update outdated information\n- Archive obsolete content\n- Monitor page analytics\n\n## Analytics & Metrics\n\n**Usage Metrics**:\n- Page views per space\n- Most visited pages\n- Search queries\n- Contributor activity\n- Orphaned pages\n\n**Health Indicators**:\n- Pages without recent updates\n- Pages without owners\n- Duplicate content\n- Broken links\n- Empty spaces\n\n## Related Skills\n\n- **Jira Expert** (`project-management\u002Fjira-expert\u002F`) — Jira issue macros and linking complement Confluence docs\n- **Atlassian Templates** (`project-management\u002Fatlassian-templates\u002F`) — Template patterns for Confluence content creation\n",{"name":5,"description":7},"main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","project-management\u002Fconfluence-expert",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill confluence-expert",{"tool":58,"command":59},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill confluence-expert",{"tool":61,"command":62},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill confluence-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproject-management\u002Fconfluence-expert\u002FSKILL.md",true,[66,72,76,80,86],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fmacro-cheat-sheet.md","REFERENCE","参考文档",7350,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproject-management\u002Fconfluence-expert\u002Freferences\u002Fmacro-cheat-sheet.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fspace-architecture-patterns.md",7693,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproject-management\u002Fconfluence-expert\u002Freferences\u002Fspace-architecture-patterns.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Ftemplates.md",14794,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproject-management\u002Fconfluence-expert\u002Freferences\u002Ftemplates.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Fcontent_audit_analyzer.py","SCRIPT","脚本",15025,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproject-management\u002Fconfluence-expert\u002Fscripts\u002Fcontent_audit_analyzer.py",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fspace_structure_generator.py",18874,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproject-management\u002Fconfluence-expert\u002Fscripts\u002Fspace_structure_generator.py",[91,122,147,171,201,221],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":102,"publishedAt":39},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,23],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":39},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[129,130,131,132,133,134,135,136,110,111,137,138,139,140,141,142,143,144,145,146],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":39},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[154,155,156,157,158,159,160,161,162,111,29,163,164,165,166,167,168,169,170,23],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":185,"publishedAt":39},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[177,182],{"categoryNo":178,"categoryName":179,"taxonomyType":180,"taxonomyTypeDesc":181},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":183,"categoryName":184,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000032","设计师",[186,187,170,31,38,188,189,190,191,111,192,193,194,195,196,197,198,199,23,200],"quality manager qms iso13485","quality","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":208,"publishedAt":39},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[207],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},[209,187,170,210,211,212,213,214,103,215,191,216,155,217,218,219,138,196,23,220],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":234,"publishedAt":39},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[227,230,233],{"categoryNo":228,"categoryName":229,"taxonomyType":180,"taxonomyTypeDesc":181},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":231,"categoryName":232,"taxonomyType":180,"taxonomyTypeDesc":181},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},[37,235,187,170,210,236,237,107,191,238,239,240,241,242,139,243,244,245,246,23],"quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]