[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NWDDFZ55REWRN1KF036M65":3,"skill-same:01M6NWDDFZ55REWRN1KF036M65":89},{"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":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6NWDDFZ55REWRN1KF036M65","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.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fintegrate-confluence\u002Falirezarezvani\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","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","integrate-confluence\u002Falirezarezvani\u002Fconfluence-expert",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill confluence-expert",{"tool":57,"command":58},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill confluence-expert",{"tool":60,"command":61},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill confluence-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fintegrate-confluence\u002Falirezarezvani\u002Fconfluence-expert\u002FSKILL.md",true,[65,71,75,79,85],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fmacro-cheat-sheet.md","REFERENCE","参考文档",7350,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fintegrate-confluence\u002Falirezarezvani\u002Fconfluence-expert\u002Freferences\u002Fmacro-cheat-sheet.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fspace-architecture-patterns.md",7694,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fintegrate-confluence\u002Falirezarezvani\u002Fconfluence-expert\u002Freferences\u002Fspace-architecture-patterns.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Ftemplates.md",14801,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fintegrate-confluence\u002Falirezarezvani\u002Fconfluence-expert\u002Freferences\u002Ftemplates.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fcontent_audit_analyzer.py","SCRIPT","脚本",15025,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fintegrate-confluence\u002Falirezarezvani\u002Fconfluence-expert\u002Fscripts\u002Fcontent_audit_analyzer.py",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fspace_structure_generator.py",18874,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fintegrate-confluence\u002Falirezarezvani\u002Fconfluence-expert\u002Fscripts\u002Fspace_structure_generator.py",[90,124,138,158,178,204],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":106,"publishedAt":39},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[96,101],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[107,108,109,110,23,111,112,113,114,115,28,116,117,118,119,120,121,122,37,123],"writing clearly and concisely","writing","concisely","text","more","timeless","error","professional","prose","use","read","Rules","commit messages","messages","error messages","ui","commit",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":39},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[131,132,108,133,134,116,135,136,137],"crafting effective readmes","README","templates","type","project","guidance","files",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":39},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000038","人力资源",[148,149,150,151,152,153,154,155,156,157,37],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","structured","community","onboarding",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":39},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[132,165,166,167,152,19,168,135,169,170,44,171,172,173,174,175,37,176,177],"project documentation","tree","kind","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":39},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[185,186,116,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":212,"publishedAt":39},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[210,211],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},[213,214,197,174,108,215,114,216,217,218,219,220,221,222,223,120,224,225,123,226],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]