[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FY932AK3033SWTQDP8AVVC":3,"skill-same:01M6FY932AK3033SWTQDP8AVVC":71},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6FY932AK3033SWTQDP8AVVC","amplitude-automation",null,"Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. 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\u002Fskills\u002Fautomation\u002Famplitude-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],"automation","amplitude automation","amplitude","MCP","tasks","search","Tools","first","automate","user","community","composio","events","identification","via","activity","2026-11-10 10:12:30",false,"---\nname: amplitude-automation\ndescription: \"Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Amplitude Automation via Rube MCP\n\nAutomate Amplitude product analytics through Composio's Amplitude toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Amplitude connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `amplitude`\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 `amplitude`\n3. If connection is not ACTIVE, follow the returned auth link to complete Amplitude authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Send Events\n\n**When to use**: User wants to track events or send event data to Amplitude\n\n**Tool sequence**:\n1. `AMPLITUDE_SEND_EVENTS` - Send one or more events to Amplitude [Required]\n\n**Key parameters**:\n- `events`: Array of event objects, each containing:\n  - `event_type`: Name of the event (e.g., 'page_view', 'purchase')\n  - `user_id`: Unique user identifier (required if no `device_id`)\n  - `device_id`: Device identifier (required if no `user_id`)\n  - `event_properties`: Object with custom event properties\n  - `user_properties`: Object with user properties to set\n  - `time`: Event timestamp in milliseconds since epoch\n\n**Pitfalls**:\n- At least one of `user_id` or `device_id` is required per event\n- `event_type` is required for every event; cannot be empty\n- `time` must be in milliseconds (13-digit epoch), not seconds\n- Batch limit applies; check schema for maximum events per request\n- Events are processed asynchronously; successful API response does not mean data is immediately queryable\n\n### 2. Get User Activity\n\n**When to use**: User wants to view event history for a specific user\n\n**Tool sequence**:\n1. `AMPLITUDE_FIND_USER` - Find user by ID or property [Prerequisite]\n2. `AMPLITUDE_GET_USER_ACTIVITY` - Retrieve user's event stream [Required]\n\n**Key parameters**:\n- `user`: Amplitude internal user ID (from FIND_USER)\n- `offset`: Pagination offset for event list\n- `limit`: Maximum number of events to return\n\n**Pitfalls**:\n- `user` parameter requires Amplitude's internal user ID, NOT your application's user_id\n- Must call FIND_USER first to resolve your user_id to Amplitude's internal ID\n- Activity is returned in reverse chronological order by default\n- Large activity histories require pagination via `offset`\n\n### 3. Find and Identify Users\n\n**When to use**: User wants to look up users or set user properties\n\n**Tool sequence**:\n1. `AMPLITUDE_FIND_USER` - Search for a user by various identifiers [Required]\n2. `AMPLITUDE_IDENTIFY` - Set or update user properties [Optional]\n\n**Key parameters**:\n- For FIND_USER:\n  - `user`: Search term (user_id, email, or Amplitude ID)\n- For IDENTIFY:\n  - `user_id`: Your application's user identifier\n  - `device_id`: Device identifier (alternative to user_id)\n  - `user_properties`: Object with `$set`, `$unset`, `$add`, `$append` operations\n\n**Pitfalls**:\n- FIND_USER searches across user_id, device_id, and Amplitude ID\n- IDENTIFY uses special property operations (`$set`, `$unset`, `$add`, `$append`)\n- `$set` overwrites existing values; `$setOnce` only sets if not already set\n- At least one of `user_id` or `device_id` is required for IDENTIFY\n- User property changes are eventually consistent; not immediate\n\n### 4. Manage Cohorts\n\n**When to use**: User wants to list cohorts, view cohort details, or update cohort membership\n\n**Tool sequence**:\n1. `AMPLITUDE_LIST_COHORTS` - List all saved cohorts [Required]\n2. `AMPLITUDE_GET_COHORT` - Get detailed cohort information [Optional]\n3. `AMPLITUDE_UPDATE_COHORT_MEMBERSHIP` - Add\u002Fremove users from a cohort [Optional]\n4. `AMPLITUDE_CHECK_COHORT_STATUS` - Check async cohort operation status [Optional]\n\n**Key parameters**:\n- For LIST_COHORTS: No required parameters\n- For GET_COHORT: `cohort_id` (from list results)\n- For UPDATE_COHORT_MEMBERSHIP:\n  - `cohort_id`: Target cohort ID\n  - `memberships`: Object with `add` and\u002For `remove` arrays of user IDs\n- For CHECK_COHORT_STATUS: `request_id` from update response\n\n**Pitfalls**:\n- Cohort IDs are required for all cohort-specific operations\n- UPDATE_COHORT_MEMBERSHIP is asynchronous; use CHECK_COHORT_STATUS to verify\n- `request_id` from the update response is needed for status checking\n- Maximum membership changes per request may be limited; chunk large updates\n- Only behavioral cohorts support API membership updates\n\n### 5. Browse Event Categories\n\n**When to use**: User wants to discover available event types and categories in Amplitude\n\n**Tool sequence**:\n1. `AMPLITUDE_GET_EVENT_CATEGORIES` - List all event categories [Required]\n\n**Key parameters**:\n- No required parameters; returns all configured event categories\n\n**Pitfalls**:\n- Categories are configured in Amplitude UI; API provides read access\n- Event names within categories are case-sensitive\n- Use these categories to validate event_type values before sending events\n\n## Common Patterns\n\n### ID Resolution\n\n**Application user_id -> Amplitude internal ID**:\n```\n1. Call AMPLITUDE_FIND_USER with user=your_user_id\n2. Extract Amplitude's internal user ID from response\n3. Use internal ID for GET_USER_ACTIVITY\n```\n\n**Cohort name -> Cohort ID**:\n```\n1. Call AMPLITUDE_LIST_COHORTS\n2. Find cohort by name in results\n3. Extract id for cohort operations\n```\n\n### User Property Operations\n\nAmplitude IDENTIFY supports these property operations:\n- `$set`: Set property value (overwrites existing)\n- `$setOnce`: Set only if property not already set\n- `$add`: Increment numeric property\n- `$append`: Append to list property\n- `$unset`: Remove property entirely\n\nExample structure:\n```json\n{\n  \"user_properties\": {\n    \"$set\": {\"plan\": \"premium\", \"company\": \"Acme\"},\n    \"$add\": {\"login_count\": 1}\n  }\n}\n```\n\n### Async Operation Pattern\n\nFor cohort membership updates:\n```\n1. Call AMPLITUDE_UPDATE_COHORT_MEMBERSHIP -> get request_id\n2. Call AMPLITUDE_CHECK_COHORT_STATUS with request_id\n3. Repeat step 2 until status is 'complete' or 'error'\n```\n\n## Known Pitfalls\n\n**User IDs**:\n- Amplitude has its own internal user IDs separate from your application's\n- FIND_USER resolves your IDs to Amplitude's internal IDs\n- GET_USER_ACTIVITY requires Amplitude's internal ID, not your user_id\n\n**Event Timestamps**:\n- Must be in milliseconds since epoch (13 digits)\n- Seconds (10 digits) will be interpreted as very old dates\n- Omitting timestamp uses server receive time\n\n**Rate Limits**:\n- Event ingestion has throughput limits per project\n- Batch events where possible to reduce API calls\n- Cohort membership updates have async processing limits\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- User activity returns events in reverse chronological order\n- Cohort lists may include archived cohorts; check status field\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Send events | AMPLITUDE_SEND_EVENTS | events (array) |\n| Find user | AMPLITUDE_FIND_USER | user |\n| Get user activity | AMPLITUDE_GET_USER_ACTIVITY | user, offset, limit |\n| Identify user | AMPLITUDE_IDENTIFY | user_id, user_properties |\n| List cohorts | AMPLITUDE_LIST_COHORTS | (none) |\n| Get cohort | AMPLITUDE_GET_COHORT | cohort_id |\n| Update cohort members | AMPLITUDE_UPDATE_COHORT_MEMBERSHIP | cohort_id, memberships |\n| Check cohort status | AMPLITUDE_CHECK_COHORT_STATUS | request_id |\n| List event categories | AMPLITUDE_GET_EVENT_CATEGORIES | (none) |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Amplitude Automation via Rube MCP\n\nAutomate Amplitude product analytics through Composio's Amplitude toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Amplitude connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `amplitude`\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 `amplitude`\n3. If connection is not ACTIVE, follow the returned auth link to complete Amplitude authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Send Events\n\n**When to use**: User wants to track events or send event data to Amplitude\n\n**Tool sequence**:\n1. `AMPLITUDE_SEND_EVENTS` - Send one or more events to Amplitude [Required]\n\n**Key parameters**:\n- `events`: Array of event objects, each containing:\n  - `event_type`: Name of the event (e.g., 'page_view', 'purchase')\n  - `user_id`: Unique user identifier (required if no `device_id`)\n  - `device_id`: Device identifier (required if no `user_id`)\n  - `event_properties`: Object with custom event properties\n  - `user_properties`: Object with user properties to set\n  - `time`: Event timestamp in milliseconds since epoch\n\n**Pitfalls**:\n- At least one of `user_id` or `device_id` is required per event\n- `event_type` is required for every event; cannot be empty\n- `time` must be in milliseconds (13-digit epoch), not seconds\n- Batch limit applies; check schema for maximum events per request\n- Events are processed asynchronously; successful API response does not mean data is immediately queryable\n\n### 2. Get User Activity\n\n**When to use**: User wants to view event history for a specific user\n\n**Tool sequence**:\n1. `AMPLITUDE_FIND_USER` - Find user by ID or property [Prerequisite]\n2. `AMPLITUDE_GET_USER_ACTIVITY` - Retrieve user's event stream [Required]\n\n**Key parameters**:\n- `user`: Amplitude internal user ID (from FIND_USER)\n- `offset`: Pagination offset for event list\n- `limit`: Maximum number of events to return\n\n**Pitfalls**:\n- `user` parameter requires Amplitude's internal user ID, NOT your application's user_id\n- Must call FIND_USER first to resolve your user_id to Amplitude's internal ID\n- Activity is returned in reverse chronological order by default\n- Large activity histories require pagination via `offset`\n\n### 3. Find and Identify Users\n\n**When to use**: User wants to look up users or set user properties\n\n**Tool sequence**:\n1. `AMPLITUDE_FIND_USER` - Search for a user by various identifiers [Required]\n2. `AMPLITUDE_IDENTIFY` - Set or update user properties [Optional]\n\n**Key parameters**:\n- For FIND_USER:\n  - `user`: Search term (user_id, email, or Amplitude ID)\n- For IDENTIFY:\n  - `user_id`: Your application's user identifier\n  - `device_id`: Device identifier (alternative to user_id)\n  - `user_properties`: Object with `$set`, `$unset`, `$add`, `$append` operations\n\n**Pitfalls**:\n- FIND_USER searches across user_id, device_id, and Amplitude ID\n- IDENTIFY uses special property operations (`$set`, `$unset`, `$add`, `$append`)\n- `$set` overwrites existing values; `$setOnce` only sets if not already set\n- At least one of `user_id` or `device_id` is required for IDENTIFY\n- User property changes are eventually consistent; not immediate\n\n### 4. Manage Cohorts\n\n**When to use**: User wants to list cohorts, view cohort details, or update cohort membership\n\n**Tool sequence**:\n1. `AMPLITUDE_LIST_COHORTS` - List all saved cohorts [Required]\n2. `AMPLITUDE_GET_COHORT` - Get detailed cohort information [Optional]\n3. `AMPLITUDE_UPDATE_COHORT_MEMBERSHIP` - Add\u002Fremove users from a cohort [Optional]\n4. `AMPLITUDE_CHECK_COHORT_STATUS` - Check async cohort operation status [Optional]\n\n**Key parameters**:\n- For LIST_COHORTS: No required parameters\n- For GET_COHORT: `cohort_id` (from list results)\n- For UPDATE_COHORT_MEMBERSHIP:\n  - `cohort_id`: Target cohort ID\n  - `memberships`: Object with `add` and\u002For `remove` arrays of user IDs\n- For CHECK_COHORT_STATUS: `request_id` from update response\n\n**Pitfalls**:\n- Cohort IDs are required for all cohort-specific operations\n- UPDATE_COHORT_MEMBERSHIP is asynchronous; use CHECK_COHORT_STATUS to verify\n- `request_id` from the update response is needed for status checking\n- Maximum membership changes per request may be limited; chunk large updates\n- Only behavioral cohorts support API membership updates\n\n### 5. Browse Event Categories\n\n**When to use**: User wants to discover available event types and categories in Amplitude\n\n**Tool sequence**:\n1. `AMPLITUDE_GET_EVENT_CATEGORIES` - List all event categories [Required]\n\n**Key parameters**:\n- No required parameters; returns all configured event categories\n\n**Pitfalls**:\n- Categories are configured in Amplitude UI; API provides read access\n- Event names within categories are case-sensitive\n- Use these categories to validate event_type values before sending events\n\n## Common Patterns\n\n### ID Resolution\n\n**Application user_id -> Amplitude internal ID**:\n```\n1. Call AMPLITUDE_FIND_USER with user=your_user_id\n2. Extract Amplitude's internal user ID from response\n3. Use internal ID for GET_USER_ACTIVITY\n```\n\n**Cohort name -> Cohort ID**:\n```\n1. Call AMPLITUDE_LIST_COHORTS\n2. Find cohort by name in results\n3. Extract id for cohort operations\n```\n\n### User Property Operations\n\nAmplitude IDENTIFY supports these property operations:\n- `$set`: Set property value (overwrites existing)\n- `$setOnce`: Set only if property not already set\n- `$add`: Increment numeric property\n- `$append`: Append to list property\n- `$unset`: Remove property entirely\n\nExample structure:\n```json\n{\n  \"user_properties\": {\n    \"$set\": {\"plan\": \"premium\", \"company\": \"Acme\"},\n    \"$add\": {\"login_count\": 1}\n  }\n}\n```\n\n### Async Operation Pattern\n\nFor cohort membership updates:\n```\n1. Call AMPLITUDE_UPDATE_COHORT_MEMBERSHIP -> get request_id\n2. Call AMPLITUDE_CHECK_COHORT_STATUS with request_id\n3. Repeat step 2 until status is 'complete' or 'error'\n```\n\n## Known Pitfalls\n\n**User IDs**:\n- Amplitude has its own internal user IDs separate from your application's\n- FIND_USER resolves your IDs to Amplitude's internal IDs\n- GET_USER_ACTIVITY requires Amplitude's internal ID, not your user_id\n\n**Event Timestamps**:\n- Must be in milliseconds since epoch (13 digits)\n- Seconds (10 digits) will be interpreted as very old dates\n- Omitting timestamp uses server receive time\n\n**Rate Limits**:\n- Event ingestion has throughput limits per project\n- Batch events where possible to reduce API calls\n- Cohort membership updates have async processing limits\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- User activity returns events in reverse chronological order\n- Cohort lists may include archived cohorts; check status field\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Send events | AMPLITUDE_SEND_EVENTS | events (array) |\n| Find user | AMPLITUDE_FIND_USER | user |\n| Get user activity | AMPLITUDE_GET_USER_ACTIVITY | user, offset, limit |\n| Identify user | AMPLITUDE_IDENTIFY | user_id, user_properties |\n| List cohorts | AMPLITUDE_LIST_COHORTS | (none) |\n| Get cohort | AMPLITUDE_GET_COHORT | cohort_id |\n| Update cohort members | AMPLITUDE_UPDATE_COHORT_MEMBERSHIP | cohort_id, memberships |\n| Check cohort status | AMPLITUDE_CHECK_COHORT_STATUS | request_id |\n| List event categories | AMPLITUDE_GET_EVENT_CATEGORIES | (none) |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":45,"source":34,"requires":46,"description":7},"unknown",{"mcp":47},[48],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","skills\u002Fautomation\u002Famplitude-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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add reikiplanet\u002Fdaoskills --skill amplitude-automation",{"tool":63,"command":64},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill amplitude-automation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill amplitude-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fautomation\u002Famplitude-automation\u002FSKILL.md",true,[],[72,98,110,125,145,168],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":40},"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",[],[79,80,81,82,83,84,34,85,86,87,88,89,90,91,92,93,94,95,96,97],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"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":40},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[105,106,96,107,108,34,86,87,88,82,109,83],"ar","vr ar","interaction","requirements","performance",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":40},"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",[],[112,117,118,119,120,121,34,122,88,123,124,82],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","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":40},"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,34,137,138,139,140,122,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":40},"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,34,88,82,160,83,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":40},"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,122,183,184,185,34,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"]