[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M778WMM00EYSA7D3DEMPEC7J":3,"skill-same:01M778WMM00EYSA7D3DEMPEC7J":62},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M778WMM00EYSA7D3DEMPEC7J","atlassian-templates",null,"Atlassian Template and Files Creator\u002FModifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use when building org-wide templates, custom blueprints, page layouts, and automated content generation.","kruxshnx\u002Fclaude-skills-devin","kruxshnx","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F127938788?v=4","01M757YM3F96N4K1BSE7Z0NQK7","ARJANGI GOVINDA KRISHNA","01M757YM43H5T7MP2B3DC13GZ2",2,"MIT","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fproject-management\u002Fskills\u002Fatlassian-templates\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"atlassian-templates\"\ndescription: Atlassian Template and Files Creator\u002FModifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use when building org-wide templates, custom blueprints, page layouts, and automated content generation.\n---\n\n# Atlassian Template & Files Creator Expert\n\nSpecialist in creating, modifying, and managing reusable templates and files for Jira and Confluence. Ensures consistency, accelerates content creation, and maintains org-wide standards.\n\n---\n\n## Workflows\n\n### Template Creation Process\n1. **Discover**: Interview stakeholders to understand needs\n2. **Analyze**: Review existing content patterns\n3. **Design**: Create template structure and placeholders\n4. **Implement**: Build template with macros and formatting\n5. **Test**: Validate with sample data — confirm template renders correctly in preview before publishing\n6. **Document**: Create usage instructions\n7. **Publish**: Deploy to appropriate space\u002Fproject via MCP (see MCP Operations below)\n8. **Verify**: Confirm deployment success; roll back to previous version if errors occur\n9. **Train**: Educate users on template usage\n10. **Monitor**: Track adoption and gather feedback\n11. **Iterate**: Refine based on usage\n\n### Template Modification Process\n1. **Assess**: Review change request and impact\n2. **Version**: Create new version, keep old available\n3. **Modify**: Update template structure\u002Fcontent\n4. **Test**: Validate changes don't break existing usage; preview updated template before publishing\n5. **Migrate**: Provide migration path for existing content\n6. **Communicate**: Announce changes to users\n7. **Support**: Assist users with migration\n8. **Archive**: Deprecate old version after transition; confirm deprecated template is unlisted, not deleted\n\n### Blueprint Development\n1. Define blueprint scope and purpose\n2. Design multi-page structure\n3. Create page templates for each section\n4. Configure page creation rules\n5. Add dynamic content (Jira queries, user data)\n6. Test blueprint creation flow end-to-end with a sample space\n7. Verify all macro references resolve correctly before deployment\n8. **HANDOFF TO**: Atlassian Admin for global deployment\n\n---\n\n## Confluence Templates Library\n\nSee **TEMPLATES.md** for full reference tables and copy-paste-ready template structures. The following summarises the standard types this skill creates and maintains.\n\n### Confluence Template Types\n| Template | Purpose | Key Macros Used |\n|----------|---------|-----------------|\n| **Meeting Notes** | Structured meeting records with agenda, decisions, and action items | `{date}`, `{tasks}`, `{panel}`, `{info}`, `{note}` |\n| **Project Charter** | Org-level project scope, stakeholder RACI, timeline, and budget | `{panel}`, `{status}`, `{timeline}`, `{info}` |\n| **Sprint Retrospective** | Agile ceremony template with What Went Well \u002F Didn't Go Well \u002F Actions | `{panel}`, `{expand}`, `{tasks}`, `{status}` |\n| **PRD** | Feature definition with goals, user stories, functional\u002Fnon-functional requirements, and release plan | `{panel}`, `{status}`, `{jira}`, `{warning}` |\n| **Decision Log** | Structured option analysis with decision matrix and implementation tracking | `{panel}`, `{status}`, `{info}`, `{tasks}` |\n\n**Standard Sections** included across all Confluence templates:\n- Header panel with metadata (owner, date, status)\n- Clearly labelled content sections with inline placeholder instructions\n- Action items block using `{tasks}` macro\n- Related links and references\n\n### Complete Example: Meeting Notes Template\n\nThe following is a copy-paste-ready Meeting Notes template in Confluence storage format (wiki markup):\n\n```\n{panel:title=Meeting Metadata|borderColor=#0052CC|titleBGColor=#0052CC|titleColor=#FFFFFF}\n*Date:* {date}\n*Owner \u002F Facilitator:* @[facilitator name]\n*Attendees:* @[name], @[name]\n*Status:* {status:colour=Yellow|title=In Progress}\n{panel}\n\nh2. Agenda\n# [Agenda item 1]\n# [Agenda item 2]\n# [Agenda item 3]\n\nh2. Discussion & Decisions\n{panel:title=Key Decisions|borderColor=#36B37E|titleBGColor=#36B37E|titleColor=#FFFFFF}\n* *Decision 1:* [What was decided and why]\n* *Decision 2:* [What was decided and why]\n{panel}\n\n{info:title=Notes}\n[Detailed discussion notes, context, or background here]\n{info}\n\nh2. Action Items\n{tasks}\n* [ ] [Action item] — Owner: @[name] — Due: {date}\n* [ ] [Action item] — Owner: @[name] — Due: {date}\n{tasks}\n\nh2. Next Steps & Related Links\n* Next meeting: {date}\n* Related pages: [link]\n* Related Jira issues: {jira:key=PROJ-123}\n```\n\n> Full examples for all other template types (Project Charter, Sprint Retrospective, PRD, Decision Log) and all Jira templates can be generated on request or found in **TEMPLATES.md**.\n\n---\n\n## Jira Templates Library\n\n### Jira Template Types\n| Template | Purpose | Key Sections |\n|----------|---------|--------------|\n| **User Story** | Feature requests in As a \u002F I want \u002F So that format | Acceptance Criteria (Given\u002FWhen\u002FThen), Design links, Technical Notes, Definition of Done |\n| **Bug Report** | Defect capture with reproduction steps | Environment, Steps to Reproduce, Expected vs Actual Behavior, Severity, Workaround |\n| **Epic** | High-level initiative scope | Vision, Goals, Success Metrics, Story Breakdown, Dependencies, Timeline |\n\n**Standard Sections** included across all Jira templates:\n- Clear summary line\n- Acceptance or success criteria as checkboxes\n- Related issues and dependencies block\n- Definition of Done (for stories)\n\n---\n\n## Macro Usage Guidelines\n\n**Dynamic Content**: Use macros for auto-updating content (dates, user mentions, Jira queries)\n**Visual Hierarchy**: Use `{panel}`, `{info}`, and `{note}` to create visual distinction\n**Interactivity**: Use `{expand}` for collapsible sections in long templates\n**Integration**: Embed Jira charts and tables via `{jira}` macro for live data\n\n---\n\n## Atlassian MCP Integration\n\n**Primary Tools**: Confluence MCP, Jira MCP\n\n### Template Operations via MCP\n\nAll MCP calls below use the exact parameter names expected by the Atlassian MCP server. Replace angle-bracket placeholders with real values before executing.\n\n**Create a Confluence page template:**\n```json\n{\n  \"tool\": \"confluence_create_page\",\n  \"parameters\": {\n    \"space_key\": \"PROJ\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cstorage-format template content>\",\n    \"labels\": [\"template\", \"meeting-notes\"],\n    \"parent_id\": \"\u003Coptional parent page id>\"\n  }\n}\n```\n\n**Update an existing template:**\n```json\n{\n  \"tool\": \"confluence_update_page\",\n  \"parameters\": {\n    \"page_id\": \"\u003Cexisting page id>\",\n    \"version\": \"\u003Ccurrent_version + 1>\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cupdated storage-format content>\",\n    \"version_comment\": \"v2 — added status macro to header\"\n  }\n}\n```\n\n**Create a Jira issue description template (via field configuration):**\n```json\n{\n  \"tool\": \"jira_update_field_configuration\",\n  \"parameters\": {\n    \"project_key\": \"PROJ\",\n    \"field_id\": \"description\",\n    \"default_value\": \"\u003Ctemplate markdown or Atlassian Document Format JSON>\"\n  }\n}\n```\n\n**Deploy template to multiple spaces (batch):**\n```json\n\u002F\u002F Repeat for each target space key\n{\n  \"tool\": \"confluence_create_page\",\n  \"parameters\": {\n    \"space_key\": \"\u003CSPACE_KEY>\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cstorage-format template content>\",\n    \"labels\": [\"template\"]\n  }\n}\n\u002F\u002F After each create, verify:\n{\n  \"tool\": \"confluence_get_page\",\n  \"parameters\": {\n    \"space_key\": \"\u003CSPACE_KEY>\",\n    \"title\": \"Template: Meeting Notes\"\n  }\n}\n\u002F\u002F Assert response status == 200 and page body is non-empty before proceeding to next space\n```\n\n**Validation checkpoint after deployment:**\n- Retrieve the created\u002Fupdated page and assert it renders without macro errors\n- Check that `{jira}` embeds resolve against the target Jira project\n- Confirm `{tasks}` blocks are interactive in the published view\n- If any check fails: revert using `confluence_update_page` with `version: \u003Ccurrent + 1>` and the previous version body\n\n---\n\n## Best Practices & Governance\n\n**Org-Specific Standards:**\n- Track template versions with version notes in the page header\n- Mark outdated templates with a `{warning}` banner before archiving; archive (do not delete)\n- Maintain usage guides linked from each template\n- Gather feedback on a quarterly review cycle; incorporate usage metrics before deprecating\n\n**Quality Gates (apply before every deployment):**\n- Example content provided for each section\n- Tested with sample data in preview\n- Version comment added to change log\n- Feedback mechanism in place (comments enabled or linked survey)\n\n**Governance Process**:\n1. Request and justification\n2. Design and review\n3. Testing with pilot users\n4. Documentation\n5. Approval\n6. Deployment (via MCP or manual)\n7. Training\n8. Monitoring\n\n---\n\n## Handoff Protocols\n\nSee **HANDOFFS.md** for the full handoff matrix. Summary:\n\n| Partner | Receives FROM | Sends TO |\n|---------|--------------|---------|\n| **Senior PM** | Template requirements, reporting templates, executive formats | Completed templates, usage analytics, optimization suggestions |\n| **Scrum Master** | Sprint ceremony needs, team-specific requests, retro format preferences | Sprint-ready templates, agile ceremony structures, velocity tracking templates |\n| **Jira Expert** | Issue template requirements, custom field display needs | Issue description templates, field config templates, JQL query templates |\n| **Confluence Expert** | Space-specific needs, global template requests, blueprint requirements | Configured page templates, blueprint structures, deployment plans |\n| **Atlassian Admin** | Org-wide standards, global deployment requirements, compliance templates | Global templates for approval, usage reports, compliance status |\n","# Atlassian Template & Files Creator Expert\n\nSpecialist in creating, modifying, and managing reusable templates and files for Jira and Confluence. Ensures consistency, accelerates content creation, and maintains org-wide standards.\n\n---\n\n## Workflows\n\n### Template Creation Process\n1. **Discover**: Interview stakeholders to understand needs\n2. **Analyze**: Review existing content patterns\n3. **Design**: Create template structure and placeholders\n4. **Implement**: Build template with macros and formatting\n5. **Test**: Validate with sample data — confirm template renders correctly in preview before publishing\n6. **Document**: Create usage instructions\n7. **Publish**: Deploy to appropriate space\u002Fproject via MCP (see MCP Operations below)\n8. **Verify**: Confirm deployment success; roll back to previous version if errors occur\n9. **Train**: Educate users on template usage\n10. **Monitor**: Track adoption and gather feedback\n11. **Iterate**: Refine based on usage\n\n### Template Modification Process\n1. **Assess**: Review change request and impact\n2. **Version**: Create new version, keep old available\n3. **Modify**: Update template structure\u002Fcontent\n4. **Test**: Validate changes don't break existing usage; preview updated template before publishing\n5. **Migrate**: Provide migration path for existing content\n6. **Communicate**: Announce changes to users\n7. **Support**: Assist users with migration\n8. **Archive**: Deprecate old version after transition; confirm deprecated template is unlisted, not deleted\n\n### Blueprint Development\n1. Define blueprint scope and purpose\n2. Design multi-page structure\n3. Create page templates for each section\n4. Configure page creation rules\n5. Add dynamic content (Jira queries, user data)\n6. Test blueprint creation flow end-to-end with a sample space\n7. Verify all macro references resolve correctly before deployment\n8. **HANDOFF TO**: Atlassian Admin for global deployment\n\n---\n\n## Confluence Templates Library\n\nSee **TEMPLATES.md** for full reference tables and copy-paste-ready template structures. The following summarises the standard types this skill creates and maintains.\n\n### Confluence Template Types\n| Template | Purpose | Key Macros Used |\n|----------|---------|-----------------|\n| **Meeting Notes** | Structured meeting records with agenda, decisions, and action items | `{date}`, `{tasks}`, `{panel}`, `{info}`, `{note}` |\n| **Project Charter** | Org-level project scope, stakeholder RACI, timeline, and budget | `{panel}`, `{status}`, `{timeline}`, `{info}` |\n| **Sprint Retrospective** | Agile ceremony template with What Went Well \u002F Didn't Go Well \u002F Actions | `{panel}`, `{expand}`, `{tasks}`, `{status}` |\n| **PRD** | Feature definition with goals, user stories, functional\u002Fnon-functional requirements, and release plan | `{panel}`, `{status}`, `{jira}`, `{warning}` |\n| **Decision Log** | Structured option analysis with decision matrix and implementation tracking | `{panel}`, `{status}`, `{info}`, `{tasks}` |\n\n**Standard Sections** included across all Confluence templates:\n- Header panel with metadata (owner, date, status)\n- Clearly labelled content sections with inline placeholder instructions\n- Action items block using `{tasks}` macro\n- Related links and references\n\n### Complete Example: Meeting Notes Template\n\nThe following is a copy-paste-ready Meeting Notes template in Confluence storage format (wiki markup):\n\n```\n{panel:title=Meeting Metadata|borderColor=#0052CC|titleBGColor=#0052CC|titleColor=#FFFFFF}\n*Date:* {date}\n*Owner \u002F Facilitator:* @[facilitator name]\n*Attendees:* @[name], @[name]\n*Status:* {status:colour=Yellow|title=In Progress}\n{panel}\n\nh2. Agenda\n# [Agenda item 1]\n# [Agenda item 2]\n# [Agenda item 3]\n\nh2. Discussion & Decisions\n{panel:title=Key Decisions|borderColor=#36B37E|titleBGColor=#36B37E|titleColor=#FFFFFF}\n* *Decision 1:* [What was decided and why]\n* *Decision 2:* [What was decided and why]\n{panel}\n\n{info:title=Notes}\n[Detailed discussion notes, context, or background here]\n{info}\n\nh2. Action Items\n{tasks}\n* [ ] [Action item] — Owner: @[name] — Due: {date}\n* [ ] [Action item] — Owner: @[name] — Due: {date}\n{tasks}\n\nh2. Next Steps & Related Links\n* Next meeting: {date}\n* Related pages: [link]\n* Related Jira issues: {jira:key=PROJ-123}\n```\n\n> Full examples for all other template types (Project Charter, Sprint Retrospective, PRD, Decision Log) and all Jira templates can be generated on request or found in **TEMPLATES.md**.\n\n---\n\n## Jira Templates Library\n\n### Jira Template Types\n| Template | Purpose | Key Sections |\n|----------|---------|--------------|\n| **User Story** | Feature requests in As a \u002F I want \u002F So that format | Acceptance Criteria (Given\u002FWhen\u002FThen), Design links, Technical Notes, Definition of Done |\n| **Bug Report** | Defect capture with reproduction steps | Environment, Steps to Reproduce, Expected vs Actual Behavior, Severity, Workaround |\n| **Epic** | High-level initiative scope | Vision, Goals, Success Metrics, Story Breakdown, Dependencies, Timeline |\n\n**Standard Sections** included across all Jira templates:\n- Clear summary line\n- Acceptance or success criteria as checkboxes\n- Related issues and dependencies block\n- Definition of Done (for stories)\n\n---\n\n## Macro Usage Guidelines\n\n**Dynamic Content**: Use macros for auto-updating content (dates, user mentions, Jira queries)\n**Visual Hierarchy**: Use `{panel}`, `{info}`, and `{note}` to create visual distinction\n**Interactivity**: Use `{expand}` for collapsible sections in long templates\n**Integration**: Embed Jira charts and tables via `{jira}` macro for live data\n\n---\n\n## Atlassian MCP Integration\n\n**Primary Tools**: Confluence MCP, Jira MCP\n\n### Template Operations via MCP\n\nAll MCP calls below use the exact parameter names expected by the Atlassian MCP server. Replace angle-bracket placeholders with real values before executing.\n\n**Create a Confluence page template:**\n```json\n{\n  \"tool\": \"confluence_create_page\",\n  \"parameters\": {\n    \"space_key\": \"PROJ\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cstorage-format template content>\",\n    \"labels\": [\"template\", \"meeting-notes\"],\n    \"parent_id\": \"\u003Coptional parent page id>\"\n  }\n}\n```\n\n**Update an existing template:**\n```json\n{\n  \"tool\": \"confluence_update_page\",\n  \"parameters\": {\n    \"page_id\": \"\u003Cexisting page id>\",\n    \"version\": \"\u003Ccurrent_version + 1>\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cupdated storage-format content>\",\n    \"version_comment\": \"v2 — added status macro to header\"\n  }\n}\n```\n\n**Create a Jira issue description template (via field configuration):**\n```json\n{\n  \"tool\": \"jira_update_field_configuration\",\n  \"parameters\": {\n    \"project_key\": \"PROJ\",\n    \"field_id\": \"description\",\n    \"default_value\": \"\u003Ctemplate markdown or Atlassian Document Format JSON>\"\n  }\n}\n```\n\n**Deploy template to multiple spaces (batch):**\n```json\n\u002F\u002F Repeat for each target space key\n{\n  \"tool\": \"confluence_create_page\",\n  \"parameters\": {\n    \"space_key\": \"\u003CSPACE_KEY>\",\n    \"title\": \"Template: Meeting Notes\",\n    \"body\": \"\u003Cstorage-format template content>\",\n    \"labels\": [\"template\"]\n  }\n}\n\u002F\u002F After each create, verify:\n{\n  \"tool\": \"confluence_get_page\",\n  \"parameters\": {\n    \"space_key\": \"\u003CSPACE_KEY>\",\n    \"title\": \"Template: Meeting Notes\"\n  }\n}\n\u002F\u002F Assert response status == 200 and page body is non-empty before proceeding to next space\n```\n\n**Validation checkpoint after deployment:**\n- Retrieve the created\u002Fupdated page and assert it renders without macro errors\n- Check that `{jira}` embeds resolve against the target Jira project\n- Confirm `{tasks}` blocks are interactive in the published view\n- If any check fails: revert using `confluence_update_page` with `version: \u003Ccurrent + 1>` and the previous version body\n\n---\n\n## Best Practices & Governance\n\n**Org-Specific Standards:**\n- Track template versions with version notes in the page header\n- Mark outdated templates with a `{warning}` banner before archiving; archive (do not delete)\n- Maintain usage guides linked from each template\n- Gather feedback on a quarterly review cycle; incorporate usage metrics before deprecating\n\n**Quality Gates (apply before every deployment):**\n- Example content provided for each section\n- Tested with sample data in preview\n- Version comment added to change log\n- Feedback mechanism in place (comments enabled or linked survey)\n\n**Governance Process**:\n1. Request and justification\n2. Design and review\n3. Testing with pilot users\n4. Documentation\n5. Approval\n6. Deployment (via MCP or manual)\n7. Training\n8. Monitoring\n\n---\n\n## Handoff Protocols\n\nSee **HANDOFFS.md** for the full handoff matrix. Summary:\n\n| Partner | Receives FROM | Sends TO |\n|---------|--------------|---------|\n| **Senior PM** | Template requirements, reporting templates, executive formats | Completed templates, usage analytics, optimization suggestions |\n| **Scrum Master** | Sprint ceremony needs, team-specific requests, retro format preferences | Sprint-ready templates, agile ceremony structures, velocity tracking templates |\n| **Jira Expert** | Issue template requirements, custom field display needs | Issue description templates, field config templates, JQL query templates |\n| **Confluence Expert** | Space-specific needs, global template requests, blueprint requirements | Configured page templates, blueprint structures, deployment plans |\n| **Atlassian Admin** | Org-wide standards, global deployment requirements, compliance templates | Global templates for approval, usage reports, compliance status |\n",{"name":5,"description":7},"devin\u002F1780503568-install-devin-skills","c1c6a7ac191f1fb795ae7f57f2fbfa600d3ef56b","project-management\u002Fskills\u002Fatlassian-templates",0,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin","https:\u002F\u002Fgithub.com\u002Fkruxshnx","https:\u002F\u002Fgovinda-krishna.vercel.app\u002F","2026-06-04 00:21:41",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kruxshnx\u002Fclaude-skills-devin --skill atlassian-templates",{"tool":38,"command":39},"bunx","bunx skills add kruxshnx\u002Fclaude-skills-devin --skill atlassian-templates",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kruxshnx\u002Fclaude-skills-devin --skill atlassian-templates","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fproject-management\u002Fskills\u002Fatlassian-templates\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fgovernance-framework.md","REFERENCE","参考文档",8900,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fproject-management\u002Fskills\u002Fatlassian-templates\u002Freferences\u002Fgovernance-framework.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Ftemplate-design-patterns.md",6521,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fproject-management\u002Fskills\u002Fatlassian-templates\u002Freferences\u002Ftemplate-design-patterns.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Ftemplate_scaffolder.py","SCRIPT","脚本",16975,"https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fproject-management\u002Fskills\u002Fatlassian-templates\u002Fscripts\u002Ftemplate_scaffolder.py",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M779G0P3W78CJF700K9AHJ6M","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M779FBBF54JKVQAGBAYHWE0B","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M779EQ39CGK5Q4V78KC0HNMV","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M779EDS05MYFXBF7PGTVSDMA","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"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":97,"publishedAt":19},"01M779DVA52T5F0YC5HSM9BW4Z","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M779D3SGW8FM1N8G0HK860WT","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002Fkruxshnx\u002Fclaude-skills-devin\u002Fblob\u002Fdevin\u002F1780503568-install-devin-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]