[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSM89AZNTN9QSZA2YYZ0V2":3,"skill-same:01M6FSM89AZNTN9QSZA2YYZ0V2":75},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":14,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6FSM89AZNTN9QSZA2YYZ0V2","klaviyo-automation",null,"Automate Klaviyo tasks via Rube MCP (Composio): manage email\u002FSMS campaigns, inspect campaign messages, track tags, and monitor send jobs. 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\u002Fklaviyo-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,41,42,43],"automation","klaviyo","klaviyo automation","jobs","MCP","tags","via","sms","campaigns","composio","monitor","community","tasks","manage","campaign","first","Tools","messages","email","search","2026-11-10 10:12:30",false,"---\nname: klaviyo-automation\ndescription: \"Automate Klaviyo tasks via Rube MCP (Composio): manage email\u002FSMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Klaviyo Automation via Rube MCP\n\nAutomate Klaviyo email and SMS marketing operations through Composio's Klaviyo toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Klaviyo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `klaviyo`\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 `klaviyo`\n3. If connection is not ACTIVE, follow the returned auth link to complete Klaviyo authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Filter Campaigns\n\n**When to use**: User wants to browse, search, or filter marketing campaigns\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGNS` - List campaigns with channel and status filters [Required]\n\n**Key parameters**:\n- `channel`: Campaign channel - 'email' or 'sms' (required by Klaviyo API)\n- `filter`: Additional filter string (e.g., `equals(status,\"draft\")`)\n- `sort`: Sort field with optional `-` prefix for descending (e.g., '-created_at', 'name')\n- `page_cursor`: Pagination cursor for next page\n- `include_archived`: Include archived campaigns (default: false)\n\n**Pitfalls**:\n- `channel` is required; omitting it can produce incomplete or unexpected results\n- Pagination is mandatory for full coverage; a single call returns only one page (default ~10)\n- Follow `page_cursor` until exhausted to get all campaigns\n- Status filtering via `filter` (e.g., `equals(status,\"draft\")`) can return mixed statuses; always validate `data[].attributes.status` client-side\n- Status strings are case-sensitive and can be compound (e.g., 'Cancelled: No Recipients')\n- Response shape is nested: `response.data.data` with status at `data[].attributes.status`\n\n### 2. Get Campaign Details\n\n**When to use**: User wants detailed information about a specific campaign\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGNS` - Find campaign to get its ID [Prerequisite]\n2. `KLAVIYO_GET_CAMPAIGN` - Retrieve full campaign details [Required]\n\n**Key parameters**:\n- `campaign_id`: Campaign ID string (e.g., '01GDDKASAP8TKDDA2GRZDSVP4H')\n- `include_messages`: Include campaign messages in response\n- `include_tags`: Include tags in response\n\n**Pitfalls**:\n- Campaign IDs are alphanumeric strings, not numeric\n- `include_messages` and `include_tags` add related data to the response via Klaviyo's include mechanism\n- Campaign details include audiences, send strategy, tracking options, and scheduling info\n\n### 3. Inspect Campaign Messages\n\n**When to use**: User wants to view the email\u002FSMS content of a campaign\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN` - Find campaign and its message IDs [Prerequisite]\n2. `KLAVIYO_GET_CAMPAIGN_MESSAGE` - Get message content details [Required]\n\n**Key parameters**:\n- `id`: Message ID string\n- `fields__campaign__message`: Sparse fieldset for message attributes (e.g., 'content.subject', 'content.from_email', 'content.body')\n- `fields__campaign`: Sparse fieldset for campaign attributes\n- `fields__template`: Sparse fieldset for template attributes\n- `include`: Related resources to include ('campaign', 'template')\n\n**Pitfalls**:\n- Message IDs are separate from campaign IDs; extract from campaign response\n- Sparse fieldset syntax uses dot notation for nested fields: 'content.subject', 'content.from_email'\n- Email messages have content fields: subject, preview_text, from_email, from_label, reply_to_email\n- SMS messages have content fields: body\n- Including 'template' provides the HTML\u002Ftext content of the email\n\n### 4. Manage Campaign Tags\n\n**When to use**: User wants to view tags associated with campaigns for organization\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS` - Get tag IDs for a campaign [Required]\n\n**Key parameters**:\n- `id`: Campaign ID string\n\n**Pitfalls**:\n- Returns only tag IDs, not tag names\u002Fdetails\n- Tag IDs can be used with Klaviyo's tag endpoints for full details\n- Rate limit: 3\u002Fs burst, 60\u002Fm steady (stricter than other endpoints)\n\n### 5. Monitor Campaign Send Jobs\n\n**When to use**: User wants to check the status of a campaign send operation\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN_SEND_JOB` - Check send job status [Required]\n\n**Key parameters**:\n- `id`: Send job ID\n\n**Pitfalls**:\n- Send job IDs are returned when a campaign send is initiated\n- Job statuses indicate whether the send is queued, in progress, complete, or failed\n- Rate limit: 10\u002Fs burst, 150\u002Fm steady\n\n## Common Patterns\n\n### Campaign Discovery Pattern\n\n```\n1. Call KLAVIYO_GET_CAMPAIGNS with channel='email'\n2. Paginate through all results via page_cursor\n3. Filter by status client-side for accuracy\n4. Extract campaign IDs for detailed inspection\n```\n\n### Sparse Fieldset Pattern\n\nKlaviyo supports sparse fieldsets to reduce response size:\n```\nfields__campaign__message=['content.subject', 'content.from_email', 'send_times']\nfields__campaign=['name', 'status', 'send_time']\nfields__template=['name', 'html', 'text']\n```\n\n### Pagination\n\n- Klaviyo uses cursor-based pagination\n- Check response for `page_cursor` in the pagination metadata\n- Pass cursor as `page_cursor` in next request\n- Default page size is ~10 campaigns\n- Continue until no more cursor is returned\n\n### Filter Syntax\n\n```\n- equals(status,\"draft\") - Campaigns in draft status\n- equals(name,\"Newsletter\") - Campaign named \"Newsletter\"\n- greater-than(created_at,\"2024-01-01T00:00:00Z\") - Created after date\n```\n\n## Known Pitfalls\n\n**API Version**:\n- Klaviyo API uses versioned endpoints (e.g., v2024-07-15)\n- Response schemas may change between API versions\n- Tool responses follow the version configured in the Composio integration\n\n**Response Nesting**:\n- Data is nested: `response.data.data[].attributes`\n- Campaign status at `data[].attributes.status`\n- Mis-parsing the nesting yields empty or incorrect results\n- Always navigate through the full path defensively\n\n**Rate Limits**:\n- Burst: 10\u002Fs (3\u002Fs for tag endpoints)\n- Steady: 150\u002Fm (60\u002Fm for tag endpoints)\n- Required scope: campaigns:read\n- Implement backoff on 429 responses\n\n**Status Values**:\n- Status strings are case-sensitive\n- Compound statuses exist (e.g., 'Cancelled: No Recipients')\n- Server-side filtering may return mixed statuses; always validate client-side\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List campaigns | KLAVIYO_GET_CAMPAIGNS | channel, filter, sort, page_cursor |\n| Get campaign details | KLAVIYO_GET_CAMPAIGN | campaign_id, include_messages, include_tags |\n| Get campaign message | KLAVIYO_GET_CAMPAIGN_MESSAGE | id, fields__campaign__message |\n| Get campaign tags | KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS | id |\n| Get send job status | KLAVIYO_GET_CAMPAIGN_SEND_JOB | id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Klaviyo Automation via Rube MCP\n\nAutomate Klaviyo email and SMS marketing operations through Composio's Klaviyo toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Klaviyo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `klaviyo`\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 `klaviyo`\n3. If connection is not ACTIVE, follow the returned auth link to complete Klaviyo authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Filter Campaigns\n\n**When to use**: User wants to browse, search, or filter marketing campaigns\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGNS` - List campaigns with channel and status filters [Required]\n\n**Key parameters**:\n- `channel`: Campaign channel - 'email' or 'sms' (required by Klaviyo API)\n- `filter`: Additional filter string (e.g., `equals(status,\"draft\")`)\n- `sort`: Sort field with optional `-` prefix for descending (e.g., '-created_at', 'name')\n- `page_cursor`: Pagination cursor for next page\n- `include_archived`: Include archived campaigns (default: false)\n\n**Pitfalls**:\n- `channel` is required; omitting it can produce incomplete or unexpected results\n- Pagination is mandatory for full coverage; a single call returns only one page (default ~10)\n- Follow `page_cursor` until exhausted to get all campaigns\n- Status filtering via `filter` (e.g., `equals(status,\"draft\")`) can return mixed statuses; always validate `data[].attributes.status` client-side\n- Status strings are case-sensitive and can be compound (e.g., 'Cancelled: No Recipients')\n- Response shape is nested: `response.data.data` with status at `data[].attributes.status`\n\n### 2. Get Campaign Details\n\n**When to use**: User wants detailed information about a specific campaign\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGNS` - Find campaign to get its ID [Prerequisite]\n2. `KLAVIYO_GET_CAMPAIGN` - Retrieve full campaign details [Required]\n\n**Key parameters**:\n- `campaign_id`: Campaign ID string (e.g., '01GDDKASAP8TKDDA2GRZDSVP4H')\n- `include_messages`: Include campaign messages in response\n- `include_tags`: Include tags in response\n\n**Pitfalls**:\n- Campaign IDs are alphanumeric strings, not numeric\n- `include_messages` and `include_tags` add related data to the response via Klaviyo's include mechanism\n- Campaign details include audiences, send strategy, tracking options, and scheduling info\n\n### 3. Inspect Campaign Messages\n\n**When to use**: User wants to view the email\u002FSMS content of a campaign\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN` - Find campaign and its message IDs [Prerequisite]\n2. `KLAVIYO_GET_CAMPAIGN_MESSAGE` - Get message content details [Required]\n\n**Key parameters**:\n- `id`: Message ID string\n- `fields__campaign__message`: Sparse fieldset for message attributes (e.g., 'content.subject', 'content.from_email', 'content.body')\n- `fields__campaign`: Sparse fieldset for campaign attributes\n- `fields__template`: Sparse fieldset for template attributes\n- `include`: Related resources to include ('campaign', 'template')\n\n**Pitfalls**:\n- Message IDs are separate from campaign IDs; extract from campaign response\n- Sparse fieldset syntax uses dot notation for nested fields: 'content.subject', 'content.from_email'\n- Email messages have content fields: subject, preview_text, from_email, from_label, reply_to_email\n- SMS messages have content fields: body\n- Including 'template' provides the HTML\u002Ftext content of the email\n\n### 4. Manage Campaign Tags\n\n**When to use**: User wants to view tags associated with campaigns for organization\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS` - Get tag IDs for a campaign [Required]\n\n**Key parameters**:\n- `id`: Campaign ID string\n\n**Pitfalls**:\n- Returns only tag IDs, not tag names\u002Fdetails\n- Tag IDs can be used with Klaviyo's tag endpoints for full details\n- Rate limit: 3\u002Fs burst, 60\u002Fm steady (stricter than other endpoints)\n\n### 5. Monitor Campaign Send Jobs\n\n**When to use**: User wants to check the status of a campaign send operation\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN_SEND_JOB` - Check send job status [Required]\n\n**Key parameters**:\n- `id`: Send job ID\n\n**Pitfalls**:\n- Send job IDs are returned when a campaign send is initiated\n- Job statuses indicate whether the send is queued, in progress, complete, or failed\n- Rate limit: 10\u002Fs burst, 150\u002Fm steady\n\n## Common Patterns\n\n### Campaign Discovery Pattern\n\n```\n1. Call KLAVIYO_GET_CAMPAIGNS with channel='email'\n2. Paginate through all results via page_cursor\n3. Filter by status client-side for accuracy\n4. Extract campaign IDs for detailed inspection\n```\n\n### Sparse Fieldset Pattern\n\nKlaviyo supports sparse fieldsets to reduce response size:\n```\nfields__campaign__message=['content.subject', 'content.from_email', 'send_times']\nfields__campaign=['name', 'status', 'send_time']\nfields__template=['name', 'html', 'text']\n```\n\n### Pagination\n\n- Klaviyo uses cursor-based pagination\n- Check response for `page_cursor` in the pagination metadata\n- Pass cursor as `page_cursor` in next request\n- Default page size is ~10 campaigns\n- Continue until no more cursor is returned\n\n### Filter Syntax\n\n```\n- equals(status,\"draft\") - Campaigns in draft status\n- equals(name,\"Newsletter\") - Campaign named \"Newsletter\"\n- greater-than(created_at,\"2024-01-01T00:00:00Z\") - Created after date\n```\n\n## Known Pitfalls\n\n**API Version**:\n- Klaviyo API uses versioned endpoints (e.g., v2024-07-15)\n- Response schemas may change between API versions\n- Tool responses follow the version configured in the Composio integration\n\n**Response Nesting**:\n- Data is nested: `response.data.data[].attributes`\n- Campaign status at `data[].attributes.status`\n- Mis-parsing the nesting yields empty or incorrect results\n- Always navigate through the full path defensively\n\n**Rate Limits**:\n- Burst: 10\u002Fs (3\u002Fs for tag endpoints)\n- Steady: 150\u002Fm (60\u002Fm for tag endpoints)\n- Required scope: campaigns:read\n- Implement backoff on 429 responses\n\n**Status Values**:\n- Status strings are case-sensitive\n- Compound statuses exist (e.g., 'Cancelled: No Recipients')\n- Server-side filtering may return mixed statuses; always validate client-side\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List campaigns | KLAVIYO_GET_CAMPAIGNS | channel, filter, sort, page_cursor |\n| Get campaign details | KLAVIYO_GET_CAMPAIGN | campaign_id, include_messages, include_tags |\n| Get campaign message | KLAVIYO_GET_CAMPAIGN_MESSAGE | id, fields__campaign__message |\n| Get campaign tags | KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS | id |\n| Get send job status | KLAVIYO_GET_CAMPAIGN_SEND_JOB | id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":49,"source":35,"requires":50,"description":7},"unknown",{"mcp":51},[52],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fklaviyo-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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add reikiplanet\u002Fdaoskills --skill klaviyo-automation",{"tool":67,"command":68},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill klaviyo-automation",{"tool":70,"command":71},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill klaviyo-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fklaviyo-automation\u002FSKILL.md",true,[],[76,102,114,129,149,172],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":44},"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",[],[83,84,85,86,87,88,35,89,90,91,92,93,94,95,96,97,98,99,100,101],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":44},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[109,110,100,111,112,35,90,91,92,86,113,87],"ar","vr ar","interaction","requirements","performance",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":44},"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",[],[116,121,122,123,124,125,35,126,92,127,128,86],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":44},"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",[],[136,137,138,139,140,35,141,142,143,144,126,145,146,147,148],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":44},"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",[],[156,157,158,159,160,161,162,163,35,92,86,164,87,165,166,167,168,169,170,171],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":44},"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",[],[179,180,181,182,183,184,185,186,169,126,187,188,189,35,190,191,192,166,193,194],"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"]