[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSM57485N2YGSBCETXDX45":3,"skill-same:01M6FSM57485N2YGSBCETXDX45":72},{"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":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":14,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6FSM57485N2YGSBCETXDX45","jira-automation",null,"Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fjira-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"automation","jira automation","jira","tasks","issues","search","Tools","first","MCP","projects","automate","community","composio","via","users","sprints","comments","2026-11-10 10:12:30",false,"---\nname: jira-automation\ndescription: \"Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Jira Automation via Rube MCP\n\nAutomate Jira operations through Composio's Jira toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\n3. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Search and Filter Issues\n\n**When to use**: User wants to find issues using JQL or browse project issues\n\n**Tool sequence**:\n1. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required]\n2. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional]\n\n**Key parameters**:\n- `jql`: JQL query string (e.g., `project = PROJ AND status = \"In Progress\"`)\n- `maxResults`: Max results per page (default 50, max 100)\n- `startAt`: Pagination offset\n- `fields`: Array of field names to return\n- `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE\n\n**Pitfalls**:\n- JQL field names are case-sensitive and must match Jira configuration\n- Custom fields use IDs like `customfield_10001`, not display names\n- Results are paginated; check `total` vs `startAt + maxResults` to continue\n\n### 2. Create and Edit Issues\n\n**When to use**: User wants to create new issues or update existing ones\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List projects to find project key [Prerequisite]\n2. `JIRA_GET_FIELDS` - Get available fields and their IDs [Prerequisite]\n3. `JIRA_CREATE_ISSUE` - Create a new issue [Required]\n4. `JIRA_EDIT_ISSUE` - Update fields on an existing issue [Optional]\n5. `JIRA_ASSIGN_ISSUE` - Assign issue to a user [Optional]\n\n**Key parameters**:\n- `project`: Project key (e.g., 'PROJ')\n- `issuetype`: Issue type name (e.g., 'Bug', 'Story', 'Task')\n- `summary`: Issue title\n- `description`: Issue description (Atlassian Document Format or plain text)\n- `issueIdOrKey`: Issue key for edits\n\n**Pitfalls**:\n- Issue types and required fields vary by project; use GET_FIELDS to check\n- Custom fields require exact field IDs, not display names\n- Description may need Atlassian Document Format (ADF) for rich content\n\n### 3. Manage Sprints and Boards\n\n**When to use**: User wants to work with agile boards, sprints, and backlogs\n\n**Tool sequence**:\n1. `JIRA_LIST_BOARDS` - List all boards [Prerequisite]\n2. `JIRA_LIST_SPRINTS` - List sprints for a board [Required]\n3. `JIRA_MOVE_ISSUE_TO_SPRINT` - Move issue to a sprint [Optional]\n4. `JIRA_CREATE_SPRINT` - Create a new sprint [Optional]\n\n**Key parameters**:\n- `boardId`: Board ID from LIST_BOARDS\n- `sprintId`: Sprint ID for move operations\n- `name`: Sprint name for creation\n- `startDate`\u002F`endDate`: Sprint dates in ISO format\n\n**Pitfalls**:\n- Boards and sprints are specific to Jira Software (not Jira Core)\n- Only one sprint can be active at a time per board\n\n### 4. Manage Comments\n\n**When to use**: User wants to add or view comments on issues\n\n**Tool sequence**:\n1. `JIRA_LIST_ISSUE_COMMENTS` - List existing comments [Optional]\n2. `JIRA_ADD_COMMENT` - Add a comment to an issue [Required]\n\n**Key parameters**:\n- `issueIdOrKey`: Issue key like 'PROJ-123'\n- `body`: Comment body (supports ADF for rich text)\n\n**Pitfalls**:\n- Comments support ADF (Atlassian Document Format) for formatting\n- Mentions use account IDs, not usernames\n\n### 5. Manage Projects and Users\n\n**When to use**: User wants to list projects, find users, or manage project roles\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List all projects [Optional]\n2. `JIRA_GET_PROJECT` - Get project details [Optional]\n3. `JIRA_FIND_USERS` \u002F `JIRA_GET_ALL_USERS` - Search for users [Optional]\n4. `JIRA_GET_PROJECT_ROLES` - List project roles [Optional]\n5. `JIRA_ADD_USERS_TO_PROJECT_ROLE` - Add user to role [Optional]\n\n**Key parameters**:\n- `projectIdOrKey`: Project key\n- `query`: Search text for FIND_USERS\n- `roleId`: Role ID for role operations\n\n**Pitfalls**:\n- User operations use account IDs (not email or display name)\n- Project roles differ from global permissions\n\n## Common Patterns\n\n### JQL Syntax\n\n**Common operators**:\n- `project = \"PROJ\"` - Filter by project\n- `status = \"In Progress\"` - Filter by status\n- `assignee = currentUser()` - Current user's issues\n- `created >= -7d` - Created in last 7 days\n- `labels = \"bug\"` - Filter by label\n- `priority = High` - Filter by priority\n- `ORDER BY created DESC` - Sort results\n\n**Combinators**:\n- `AND` - Both conditions\n- `OR` - Either condition\n- `NOT` - Negate condition\n\n### Pagination\n\n- Use `startAt` and `maxResults` parameters\n- Check `total` in response to determine remaining pages\n- Continue until `startAt + maxResults >= total`\n\n## Known Pitfalls\n\n**Field Names**:\n- Custom fields use IDs like `customfield_10001`\n- Use JIRA_GET_FIELDS to discover field IDs and names\n- Field names in JQL may differ from API field names\n\n**Authentication**:\n- Jira Cloud uses account IDs, not usernames\n- Site URL must be configured correctly in the connection\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults |\n| Get issue | JIRA_GET_ISSUE | issueIdOrKey |\n| Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary |\n| Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields |\n| Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId |\n| Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body |\n| List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey |\n| List projects | JIRA_GET_ALL_PROJECTS | (none) |\n| Get project | JIRA_GET_PROJECT | projectIdOrKey |\n| List boards | JIRA_LIST_BOARDS | (none) |\n| List sprints | JIRA_LIST_SPRINTS | boardId |\n| Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues |\n| Create sprint | JIRA_CREATE_SPRINT | name, boardId |\n| Find users | JIRA_FIND_USERS | query |\n| Get fields | JIRA_GET_FIELDS | (none) |\n| List filters | JIRA_LIST_FILTERS | (none) |\n| Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey |\n| Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Jira Automation via Rube MCP\n\nAutomate Jira operations through Composio's Jira toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Jira connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `jira`\n3. If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Search and Filter Issues\n\n**When to use**: User wants to find issues using JQL or browse project issues\n\n**Tool sequence**:\n1. `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` - Search with JQL query [Required]\n2. `JIRA_GET_ISSUE` - Get full details of a specific issue [Optional]\n\n**Key parameters**:\n- `jql`: JQL query string (e.g., `project = PROJ AND status = \"In Progress\"`)\n- `maxResults`: Max results per page (default 50, max 100)\n- `startAt`: Pagination offset\n- `fields`: Array of field names to return\n- `issueIdOrKey`: Issue key like 'PROJ-123' for GET_ISSUE\n\n**Pitfalls**:\n- JQL field names are case-sensitive and must match Jira configuration\n- Custom fields use IDs like `customfield_10001`, not display names\n- Results are paginated; check `total` vs `startAt + maxResults` to continue\n\n### 2. Create and Edit Issues\n\n**When to use**: User wants to create new issues or update existing ones\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List projects to find project key [Prerequisite]\n2. `JIRA_GET_FIELDS` - Get available fields and their IDs [Prerequisite]\n3. `JIRA_CREATE_ISSUE` - Create a new issue [Required]\n4. `JIRA_EDIT_ISSUE` - Update fields on an existing issue [Optional]\n5. `JIRA_ASSIGN_ISSUE` - Assign issue to a user [Optional]\n\n**Key parameters**:\n- `project`: Project key (e.g., 'PROJ')\n- `issuetype`: Issue type name (e.g., 'Bug', 'Story', 'Task')\n- `summary`: Issue title\n- `description`: Issue description (Atlassian Document Format or plain text)\n- `issueIdOrKey`: Issue key for edits\n\n**Pitfalls**:\n- Issue types and required fields vary by project; use GET_FIELDS to check\n- Custom fields require exact field IDs, not display names\n- Description may need Atlassian Document Format (ADF) for rich content\n\n### 3. Manage Sprints and Boards\n\n**When to use**: User wants to work with agile boards, sprints, and backlogs\n\n**Tool sequence**:\n1. `JIRA_LIST_BOARDS` - List all boards [Prerequisite]\n2. `JIRA_LIST_SPRINTS` - List sprints for a board [Required]\n3. `JIRA_MOVE_ISSUE_TO_SPRINT` - Move issue to a sprint [Optional]\n4. `JIRA_CREATE_SPRINT` - Create a new sprint [Optional]\n\n**Key parameters**:\n- `boardId`: Board ID from LIST_BOARDS\n- `sprintId`: Sprint ID for move operations\n- `name`: Sprint name for creation\n- `startDate`\u002F`endDate`: Sprint dates in ISO format\n\n**Pitfalls**:\n- Boards and sprints are specific to Jira Software (not Jira Core)\n- Only one sprint can be active at a time per board\n\n### 4. Manage Comments\n\n**When to use**: User wants to add or view comments on issues\n\n**Tool sequence**:\n1. `JIRA_LIST_ISSUE_COMMENTS` - List existing comments [Optional]\n2. `JIRA_ADD_COMMENT` - Add a comment to an issue [Required]\n\n**Key parameters**:\n- `issueIdOrKey`: Issue key like 'PROJ-123'\n- `body`: Comment body (supports ADF for rich text)\n\n**Pitfalls**:\n- Comments support ADF (Atlassian Document Format) for formatting\n- Mentions use account IDs, not usernames\n\n### 5. Manage Projects and Users\n\n**When to use**: User wants to list projects, find users, or manage project roles\n\n**Tool sequence**:\n1. `JIRA_GET_ALL_PROJECTS` - List all projects [Optional]\n2. `JIRA_GET_PROJECT` - Get project details [Optional]\n3. `JIRA_FIND_USERS` \u002F `JIRA_GET_ALL_USERS` - Search for users [Optional]\n4. `JIRA_GET_PROJECT_ROLES` - List project roles [Optional]\n5. `JIRA_ADD_USERS_TO_PROJECT_ROLE` - Add user to role [Optional]\n\n**Key parameters**:\n- `projectIdOrKey`: Project key\n- `query`: Search text for FIND_USERS\n- `roleId`: Role ID for role operations\n\n**Pitfalls**:\n- User operations use account IDs (not email or display name)\n- Project roles differ from global permissions\n\n## Common Patterns\n\n### JQL Syntax\n\n**Common operators**:\n- `project = \"PROJ\"` - Filter by project\n- `status = \"In Progress\"` - Filter by status\n- `assignee = currentUser()` - Current user's issues\n- `created >= -7d` - Created in last 7 days\n- `labels = \"bug\"` - Filter by label\n- `priority = High` - Filter by priority\n- `ORDER BY created DESC` - Sort results\n\n**Combinators**:\n- `AND` - Both conditions\n- `OR` - Either condition\n- `NOT` - Negate condition\n\n### Pagination\n\n- Use `startAt` and `maxResults` parameters\n- Check `total` in response to determine remaining pages\n- Continue until `startAt + maxResults >= total`\n\n## Known Pitfalls\n\n**Field Names**:\n- Custom fields use IDs like `customfield_10001`\n- Use JIRA_GET_FIELDS to discover field IDs and names\n- Field names in JQL may differ from API field names\n\n**Authentication**:\n- Jira Cloud uses account IDs, not usernames\n- Site URL must be configured correctly in the connection\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults |\n| Get issue | JIRA_GET_ISSUE | issueIdOrKey |\n| Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary |\n| Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields |\n| Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId |\n| Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body |\n| List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey |\n| List projects | JIRA_GET_ALL_PROJECTS | (none) |\n| Get project | JIRA_GET_PROJECT | projectIdOrKey |\n| List boards | JIRA_LIST_BOARDS | (none) |\n| List sprints | JIRA_LIST_SPRINTS | boardId |\n| Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues |\n| Create sprint | JIRA_CREATE_SPRINT | name, boardId |\n| Find users | JIRA_FIND_USERS | query |\n| Get fields | JIRA_GET_FIELDS | (none) |\n| List filters | JIRA_LIST_FILTERS | (none) |\n| Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey |\n| Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":46,"source":35,"requires":47,"description":7},"unknown",{"mcp":48},[49],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fjira-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add reikiplanet\u002Fdaoskills --skill jira-automation",{"tool":64,"command":65},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill jira-automation",{"tool":67,"command":68},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill jira-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fjira-automation\u002FSKILL.md",true,[],[73,99,111,125,145,168],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":41},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[80,81,82,83,84,85,35,86,87,88,89,90,91,92,93,94,95,96,97,98],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":41},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[106,107,97,108,109,35,87,88,89,83,110,84],"ar","vr ar","interaction","requirements","performance",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":41},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[113,118,119,120,121,122,35,123,89,33,124,83],"project scaffolding","From Scratch","tech","project","scaffolding","use","applications",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":41},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[132,133,134,135,136,35,137,138,139,140,123,141,142,143,144],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":41},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[152,153,154,155,156,157,158,159,35,89,83,160,84,161,162,163,164,165,166,167],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":41},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[175,176,177,178,179,180,181,182,165,123,183,184,185,35,186,187,188,162,189,190],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]