[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSN26CS67S744ZPQVCZ8X3":3,"skill-same:01M6FSN26CS67S744ZPQVCZ8X3":73},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6FSN26CS67S744ZPQVCZ8X3","mixpanel-automation",null,"Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. 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\u002Fmixpanel-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],"automation","mixpanel automation","mixpanel","profiles","MCP","via","events","jql","composio","community","queries","user","automate","segmentation","first","Tools","search","tasks","2026-11-10 10:12:30",false,"---\nname: mixpanel-automation\ndescription: \"Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Mixpanel Automation via Rube MCP\n\nAutomate Mixpanel product analytics through Composio's Mixpanel toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Mixpanel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`\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 `mixpanel`\n3. If connection is not ACTIVE, follow the returned auth link to complete Mixpanel authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Aggregate Event Data\n\n**When to use**: User wants to count events, get totals, or track event trends over time\n\n**Tool sequence**:\n1. `MIXPANEL_GET_ALL_PROJECTS` - List projects to get project ID [Prerequisite]\n2. `MIXPANEL_AGGREGATE_EVENT_COUNTS` - Get event counts and aggregations [Required]\n\n**Key parameters**:\n- `event`: Event name or array of event names to aggregate\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `unit`: Time granularity ('minute', 'hour', 'day', 'week', 'month')\n- `type`: Aggregation type ('general', 'unique', 'average')\n- `where`: Filter expression for event properties\n\n**Pitfalls**:\n- Date format must be 'YYYY-MM-DD'; other formats cause errors\n- Event names are case-sensitive; use exact names from your Mixpanel project\n- `where` filter uses Mixpanel expression syntax (e.g., `properties[\"country\"] == \"US\"`)\n- Maximum date range may be limited depending on your Mixpanel plan\n\n### 2. Run Segmentation Queries\n\n**When to use**: User wants to break down events by properties for detailed analysis\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_SEGMENTATION` - Run segmentation analysis [Required]\n\n**Key parameters**:\n- `event`: Event name to segment\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `on`: Property to segment by (e.g., `properties[\"country\"]`)\n- `unit`: Time granularity\n- `type`: Count type ('general', 'unique', 'average')\n- `where`: Filter expression\n- `limit`: Maximum number of segments to return\n\n**Pitfalls**:\n- The `on` parameter uses Mixpanel property expression syntax\n- Property references must use `properties[\"prop_name\"]` format\n- Segmentation on high-cardinality properties returns capped results; use `limit`\n- Results are grouped by the segmentation property and time unit\n\n### 3. Analyze Funnels\n\n**When to use**: User wants to track conversion funnels and identify drop-off points\n\n**Tool sequence**:\n1. `MIXPANEL_LIST_FUNNELS` - List saved funnels to find funnel ID [Prerequisite]\n2. `MIXPANEL_QUERY_FUNNEL` - Execute funnel analysis [Required]\n\n**Key parameters**:\n- `funnel_id`: ID of the saved funnel to query\n- `from_date` \u002F `to_date`: Date range\n- `unit`: Time granularity\n- `where`: Filter expression\n- `on`: Property to segment funnel by\n- `length`: Conversion window in days\n\n**Pitfalls**:\n- `funnel_id` is required; resolve via LIST_FUNNELS first\n- Funnels must be created in Mixpanel UI first; API only queries existing funnels\n- Conversion window (`length`) defaults vary; set explicitly for accuracy\n- Large date ranges with segmentation can produce very large responses\n\n### 4. Manage User Profiles\n\n**When to use**: User wants to query or update user profiles in Mixpanel\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_PROFILES` - Search and filter user profiles [Required]\n2. `MIXPANEL_PROFILE_BATCH_UPDATE` - Update multiple user profiles [Optional]\n\n**Key parameters**:\n- `where`: Filter expression for profile properties (e.g., `properties[\"plan\"] == \"premium\"`)\n- `output_properties`: Array of property names to include in results\n- `page`: Page number for pagination\n- `session_id`: Session ID for consistent pagination (from first response)\n- For batch update: array of profile updates with `$distinct_id` and property operations\n\n**Pitfalls**:\n- Profile queries return paginated results; use `session_id` from first response for consistent paging\n- `where` uses Mixpanel expression syntax for profile properties\n- BATCH_UPDATE applies operations (`$set`, `$unset`, `$add`, `$append`) to profiles\n- Batch update has a maximum number of profiles per request; chunk larger updates\n- Profile property names are case-sensitive\n\n### 5. Manage Cohorts\n\n**When to use**: User wants to list or analyze user cohorts\n\n**Tool sequence**:\n1. `MIXPANEL_COHORTS_LIST` - List all saved cohorts [Required]\n\n**Key parameters**:\n- No required parameters; returns all accessible cohorts\n- Response includes cohort `id`, `name`, `description`, `count`\n\n**Pitfalls**:\n- Cohorts are created and managed in Mixpanel UI; API provides read access\n- Cohort IDs are numeric; use exact ID from list results\n- Cohort counts may be approximate for very large cohorts\n- Cohorts can be used as filters in other queries via `where` expressions\n\n### 6. Run JQL and Insight Queries\n\n**When to use**: User wants to run custom JQL queries or insight analyses\n\n**Tool sequence**:\n1. `MIXPANEL_JQL_QUERY` - Execute a custom JQL (JavaScript Query Language) query [Optional]\n2. `MIXPANEL_QUERY_INSIGHT` - Run a saved insight query [Optional]\n\n**Key parameters**:\n- For JQL: `script` containing the JQL JavaScript code\n- For Insight: `bookmark_id` of the saved insight\n- `project_id`: Project context for the query\n\n**Pitfalls**:\n- JQL uses JavaScript-like syntax specific to Mixpanel\n- JQL queries have execution time limits; optimize for efficiency\n- Insight `bookmark_id` must reference an existing saved insight\n- JQL is a legacy feature; check Mixpanel documentation for current availability\n\n## Common Patterns\n\n### ID Resolution\n\n**Project name -> Project ID**:\n```\n1. Call MIXPANEL_GET_ALL_PROJECTS\n2. Find project by name in results\n3. Extract project id\n```\n\n**Funnel name -> Funnel ID**:\n```\n1. Call MIXPANEL_LIST_FUNNELS\n2. Find funnel by name\n3. Extract funnel_id\n```\n\n### Mixpanel Expression Syntax\n\nUsed in `where` and `on` parameters:\n- Property reference: `properties[\"property_name\"]`\n- Equality: `properties[\"country\"] == \"US\"`\n- Comparison: `properties[\"age\"] > 25`\n- Boolean: `properties[\"is_premium\"] == true`\n- Contains: `\"search_term\" in properties[\"name\"]`\n- AND\u002FOR: `properties[\"country\"] == \"US\" and properties[\"plan\"] == \"pro\"`\n\n### Pagination\n\n- Event queries: Follow date-based pagination by adjusting date ranges\n- Profile queries: Use `page` number and `session_id` for consistent results\n- Funnel\u002Fcohort lists: Typically return complete results without pagination\n\n## Known Pitfalls\n\n**Date Formats**:\n- Always use 'YYYY-MM-DD' format\n- Date ranges are inclusive on both ends\n- Data freshness depends on Mixpanel ingestion delay (typically minutes)\n\n**Expression Syntax**:\n- Property references always use `properties[\"name\"]` format\n- String values must be quoted: `properties[\"status\"] == \"active\"`\n- Numeric values are unquoted: `properties[\"count\"] > 10`\n- Boolean values: `true` \u002F `false` (lowercase)\n\n**Rate Limits**:\n- Mixpanel API has rate limits per project\n- Large segmentation queries may time out; reduce date range or segments\n- Use batch operations where available to minimize API calls\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Event data is typically grouped by date and segment\n- Numeric values may be returned as strings; parse explicitly\n- Empty date ranges return empty objects, not empty arrays\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | MIXPANEL_GET_ALL_PROJECTS | (none) |\n| Aggregate events | MIXPANEL_AGGREGATE_EVENT_COUNTS | event, from_date, to_date, unit |\n| Segmentation | MIXPANEL_QUERY_SEGMENTATION | event, on, from_date, to_date |\n| List funnels | MIXPANEL_LIST_FUNNELS | (none) |\n| Query funnel | MIXPANEL_QUERY_FUNNEL | funnel_id, from_date, to_date |\n| Query profiles | MIXPANEL_QUERY_PROFILES | where, output_properties, page |\n| Batch update profiles | MIXPANEL_PROFILE_BATCH_UPDATE | (profile update objects) |\n| List cohorts | MIXPANEL_COHORTS_LIST | (none) |\n| JQL query | MIXPANEL_JQL_QUERY | script |\n| Query insight | MIXPANEL_QUERY_INSIGHT | bookmark_id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Mixpanel Automation via Rube MCP\n\nAutomate Mixpanel product analytics through Composio's Mixpanel toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Mixpanel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`\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 `mixpanel`\n3. If connection is not ACTIVE, follow the returned auth link to complete Mixpanel authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Aggregate Event Data\n\n**When to use**: User wants to count events, get totals, or track event trends over time\n\n**Tool sequence**:\n1. `MIXPANEL_GET_ALL_PROJECTS` - List projects to get project ID [Prerequisite]\n2. `MIXPANEL_AGGREGATE_EVENT_COUNTS` - Get event counts and aggregations [Required]\n\n**Key parameters**:\n- `event`: Event name or array of event names to aggregate\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `unit`: Time granularity ('minute', 'hour', 'day', 'week', 'month')\n- `type`: Aggregation type ('general', 'unique', 'average')\n- `where`: Filter expression for event properties\n\n**Pitfalls**:\n- Date format must be 'YYYY-MM-DD'; other formats cause errors\n- Event names are case-sensitive; use exact names from your Mixpanel project\n- `where` filter uses Mixpanel expression syntax (e.g., `properties[\"country\"] == \"US\"`)\n- Maximum date range may be limited depending on your Mixpanel plan\n\n### 2. Run Segmentation Queries\n\n**When to use**: User wants to break down events by properties for detailed analysis\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_SEGMENTATION` - Run segmentation analysis [Required]\n\n**Key parameters**:\n- `event`: Event name to segment\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `on`: Property to segment by (e.g., `properties[\"country\"]`)\n- `unit`: Time granularity\n- `type`: Count type ('general', 'unique', 'average')\n- `where`: Filter expression\n- `limit`: Maximum number of segments to return\n\n**Pitfalls**:\n- The `on` parameter uses Mixpanel property expression syntax\n- Property references must use `properties[\"prop_name\"]` format\n- Segmentation on high-cardinality properties returns capped results; use `limit`\n- Results are grouped by the segmentation property and time unit\n\n### 3. Analyze Funnels\n\n**When to use**: User wants to track conversion funnels and identify drop-off points\n\n**Tool sequence**:\n1. `MIXPANEL_LIST_FUNNELS` - List saved funnels to find funnel ID [Prerequisite]\n2. `MIXPANEL_QUERY_FUNNEL` - Execute funnel analysis [Required]\n\n**Key parameters**:\n- `funnel_id`: ID of the saved funnel to query\n- `from_date` \u002F `to_date`: Date range\n- `unit`: Time granularity\n- `where`: Filter expression\n- `on`: Property to segment funnel by\n- `length`: Conversion window in days\n\n**Pitfalls**:\n- `funnel_id` is required; resolve via LIST_FUNNELS first\n- Funnels must be created in Mixpanel UI first; API only queries existing funnels\n- Conversion window (`length`) defaults vary; set explicitly for accuracy\n- Large date ranges with segmentation can produce very large responses\n\n### 4. Manage User Profiles\n\n**When to use**: User wants to query or update user profiles in Mixpanel\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_PROFILES` - Search and filter user profiles [Required]\n2. `MIXPANEL_PROFILE_BATCH_UPDATE` - Update multiple user profiles [Optional]\n\n**Key parameters**:\n- `where`: Filter expression for profile properties (e.g., `properties[\"plan\"] == \"premium\"`)\n- `output_properties`: Array of property names to include in results\n- `page`: Page number for pagination\n- `session_id`: Session ID for consistent pagination (from first response)\n- For batch update: array of profile updates with `$distinct_id` and property operations\n\n**Pitfalls**:\n- Profile queries return paginated results; use `session_id` from first response for consistent paging\n- `where` uses Mixpanel expression syntax for profile properties\n- BATCH_UPDATE applies operations (`$set`, `$unset`, `$add`, `$append`) to profiles\n- Batch update has a maximum number of profiles per request; chunk larger updates\n- Profile property names are case-sensitive\n\n### 5. Manage Cohorts\n\n**When to use**: User wants to list or analyze user cohorts\n\n**Tool sequence**:\n1. `MIXPANEL_COHORTS_LIST` - List all saved cohorts [Required]\n\n**Key parameters**:\n- No required parameters; returns all accessible cohorts\n- Response includes cohort `id`, `name`, `description`, `count`\n\n**Pitfalls**:\n- Cohorts are created and managed in Mixpanel UI; API provides read access\n- Cohort IDs are numeric; use exact ID from list results\n- Cohort counts may be approximate for very large cohorts\n- Cohorts can be used as filters in other queries via `where` expressions\n\n### 6. Run JQL and Insight Queries\n\n**When to use**: User wants to run custom JQL queries or insight analyses\n\n**Tool sequence**:\n1. `MIXPANEL_JQL_QUERY` - Execute a custom JQL (JavaScript Query Language) query [Optional]\n2. `MIXPANEL_QUERY_INSIGHT` - Run a saved insight query [Optional]\n\n**Key parameters**:\n- For JQL: `script` containing the JQL JavaScript code\n- For Insight: `bookmark_id` of the saved insight\n- `project_id`: Project context for the query\n\n**Pitfalls**:\n- JQL uses JavaScript-like syntax specific to Mixpanel\n- JQL queries have execution time limits; optimize for efficiency\n- Insight `bookmark_id` must reference an existing saved insight\n- JQL is a legacy feature; check Mixpanel documentation for current availability\n\n## Common Patterns\n\n### ID Resolution\n\n**Project name -> Project ID**:\n```\n1. Call MIXPANEL_GET_ALL_PROJECTS\n2. Find project by name in results\n3. Extract project id\n```\n\n**Funnel name -> Funnel ID**:\n```\n1. Call MIXPANEL_LIST_FUNNELS\n2. Find funnel by name\n3. Extract funnel_id\n```\n\n### Mixpanel Expression Syntax\n\nUsed in `where` and `on` parameters:\n- Property reference: `properties[\"property_name\"]`\n- Equality: `properties[\"country\"] == \"US\"`\n- Comparison: `properties[\"age\"] > 25`\n- Boolean: `properties[\"is_premium\"] == true`\n- Contains: `\"search_term\" in properties[\"name\"]`\n- AND\u002FOR: `properties[\"country\"] == \"US\" and properties[\"plan\"] == \"pro\"`\n\n### Pagination\n\n- Event queries: Follow date-based pagination by adjusting date ranges\n- Profile queries: Use `page` number and `session_id` for consistent results\n- Funnel\u002Fcohort lists: Typically return complete results without pagination\n\n## Known Pitfalls\n\n**Date Formats**:\n- Always use 'YYYY-MM-DD' format\n- Date ranges are inclusive on both ends\n- Data freshness depends on Mixpanel ingestion delay (typically minutes)\n\n**Expression Syntax**:\n- Property references always use `properties[\"name\"]` format\n- String values must be quoted: `properties[\"status\"] == \"active\"`\n- Numeric values are unquoted: `properties[\"count\"] > 10`\n- Boolean values: `true` \u002F `false` (lowercase)\n\n**Rate Limits**:\n- Mixpanel API has rate limits per project\n- Large segmentation queries may time out; reduce date range or segments\n- Use batch operations where available to minimize API calls\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Event data is typically grouped by date and segment\n- Numeric values may be returned as strings; parse explicitly\n- Empty date ranges return empty objects, not empty arrays\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | MIXPANEL_GET_ALL_PROJECTS | (none) |\n| Aggregate events | MIXPANEL_AGGREGATE_EVENT_COUNTS | event, from_date, to_date, unit |\n| Segmentation | MIXPANEL_QUERY_SEGMENTATION | event, on, from_date, to_date |\n| List funnels | MIXPANEL_LIST_FUNNELS | (none) |\n| Query funnel | MIXPANEL_QUERY_FUNNEL | funnel_id, from_date, to_date |\n| Query profiles | MIXPANEL_QUERY_PROFILES | where, output_properties, page |\n| Batch update profiles | MIXPANEL_PROFILE_BATCH_UPDATE | (profile update objects) |\n| List cohorts | MIXPANEL_COHORTS_LIST | (none) |\n| JQL query | MIXPANEL_JQL_QUERY | script |\n| Query insight | MIXPANEL_QUERY_INSIGHT | bookmark_id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":47,"source":33,"requires":48,"description":7},"unknown",{"mcp":49},[50],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fmixpanel-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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add reikiplanet\u002Fdaoskills --skill mixpanel-automation",{"tool":65,"command":66},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill mixpanel-automation",{"tool":68,"command":69},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill mixpanel-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fmixpanel-automation\u002FSKILL.md",true,[],[74,100,112,127,147,170],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":42},"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",[],[81,82,83,84,85,86,33,87,88,89,90,91,92,93,94,95,96,97,98,99],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":42},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[107,108,98,109,110,33,88,89,90,84,111,85],"ar","vr ar","interaction","requirements","performance",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":42},"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",[],[114,119,120,121,122,123,33,124,90,125,126,84],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":42},"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",[],[134,135,136,137,138,33,139,140,141,142,124,143,144,145,146],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":42},"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",[],[154,155,156,157,158,159,160,161,33,90,84,162,85,163,164,165,166,167,168,169],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":176,"publishedAt":42},"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",[],[177,178,179,180,181,182,183,184,167,124,185,186,187,33,188,189,190,164,191,192],"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"]