[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73PB7GJ8PNV6EXV7DB5EDA5":3,"skill-same:01M73PB7GJ8PNV6EXV7DB5EDA5":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M73PB7GJ8PNV6EXV7DB5EDA5","azure-kusto",null,"Query and analyze data in Azure Data Explorer (Kusto\u002FADX) using KQL for log analytics, telemetry, and time series analysis. WHEN: KQL queries, Kusto database queries, Azure Data Explorer, ADX clusters, log analytics, time series data, IoT telemetry, anomaly detection.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fazure-kusto\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: azure-kusto\ndescription: \"Query and analyze data in Azure Data Explorer (Kusto\u002FADX) using KQL for log analytics, telemetry, and time series analysis. WHEN: KQL queries, Kusto database queries, Azure Data Explorer, ADX clusters, log analytics, time series data, IoT telemetry, anomaly detection.\"\nlicense: MIT\nmetadata:\n  author: Microsoft\n  version: \"0.0.0-placeholder\"\n---\n\n# Azure Data Explorer (Kusto) Query & Analytics\n\nExecute KQL queries and manage Azure Data Explorer resources for fast, scalable big data analytics on log, telemetry, and time series data.\n\n## Skill Activation Triggers\n\n**Use this skill immediately when the user asks to:**\n- \"Query my Kusto database for [data pattern]\"\n- \"Show me events in the last hour from Azure Data Explorer\"\n- \"Analyze logs in my ADX cluster\"\n- \"Run a KQL query on [database]\"\n- \"What tables are in my Kusto database?\"\n- \"Show me the schema for [table]\"\n- \"List my Azure Data Explorer clusters\"\n- \"Aggregate telemetry data by [dimension]\"\n- \"Create a time series chart from my logs\"\n\n**Key Indicators:**\n- Mentions \"Kusto\", \"Azure Data Explorer\", \"ADX\", or \"KQL\"\n- Log analytics or telemetry analysis requests\n- Time series data exploration\n- IoT data analysis queries\n- SIEM or security analytics tasks\n- Requests for data aggregation on large datasets\n- Performance monitoring or APM queries\n\n## Overview\n\nThis skill enables querying and managing Azure Data Explorer (Kusto), a fast and highly scalable data exploration service optimized for log and telemetry data. Azure Data Explorer provides sub-second query performance on billions of records using the Kusto Query Language (KQL).\n\nKey capabilities:\n- **Query Execution**: Run KQL queries against massive datasets\n- **Schema Exploration**: Discover tables, columns, and data types\n- **Resource Management**: List clusters and databases\n- **Analytics**: Aggregations, time series, anomaly detection, machine learning\n\n## Core Workflow\n\n1. **Discover Resources**: List available clusters and databases in subscription\n2. **Explore Schema**: Retrieve table structures to understand data model\n3. **Query Data**: Execute KQL queries for analysis, filtering, aggregation\n4. **Analyze Results**: Process query output for insights and reporting\n\n## Query Patterns\n\n### Pattern 1: Basic Data Retrieval\nFetch recent records from a table with simple filtering.\n\n**Example KQL**:\n```kql\nEvents\n| where Timestamp > ago(1h)\n| take 100\n```\n\n**Use for**: Quick data inspection, recent event retrieval\n\n### Pattern 2: Aggregation Analysis\nSummarize data by dimensions for insights and reporting.\n\n**Example KQL**:\n```kql\nEvents\n| summarize count() by EventType, bin(Timestamp, 1h)\n| order by count_ desc\n```\n\n**Use for**: Event counting, distribution analysis, top-N queries\n\n### Pattern 3: Time Series Analytics\nAnalyze data over time windows for trends and patterns.\n\n**Example KQL**:\n```kql\nTelemetry\n| where Timestamp > ago(24h)\n| summarize avg(ResponseTime), percentiles(ResponseTime, 50, 95, 99) by bin(Timestamp, 5m)\n| render timechart\n```\n\n**Use for**: Performance monitoring, trend analysis, anomaly detection\n\n### Pattern 4: Join and Correlation\nCombine multiple tables for cross-dataset analysis.\n\n**Example KQL**:\n```kql\nEvents\n| where EventType == \"Error\"\n| join kind=inner (\n    Logs\n    | where Severity == \"Critical\"\n) on CorrelationId\n| project Timestamp, EventType, LogMessage, Severity\n```\n\n**Use for**: Root cause analysis, correlated event tracking\n\n### Pattern 5: Schema Discovery\nExplore table structure before querying.\n\n**Tools**: `kusto_table_schema_get`\n\n**Use for**: Understanding data model, query planning\n\n## Key Data Fields\n\nWhen executing queries, common field patterns:\n- **Timestamp**: Time of event (datetime) - use `ago()`, `between()`, `bin()` for time filtering\n- **EventType\u002FCategory**: Classification field for grouping\n- **CorrelationId\u002FSessionId**: For tracing related events\n- **Severity\u002FLevel**: For filtering by importance\n- **Dimensions**: Custom properties for grouping and filtering\n\n## Result Format\n\nQuery results include:\n- **Columns**: Field names and data types\n- **Rows**: Data records matching query\n- **Statistics**: Row count, execution time, resource utilization\n- **Visualization**: Chart rendering hints (timechart, barchart, etc.)\n\n## KQL Best Practices\n\n**🟢 Performance Optimized:**\n- Filter early: Use `where` before joins and aggregations\n- Limit result size: Use `take` or `limit` to reduce data transfer\n- Time filters: Always filter by time range for time series data\n- Indexed columns: Filter on indexed columns first\n\n**🔵 Query Patterns:**\n- Use `summarize` for aggregations instead of `count()` alone\n- Use `bin()` for time bucketing in time series\n- Use `project` to select only needed columns\n- Use `extend` to add calculated fields\n\n**🟡 Common Functions:**\n- `ago(timespan)`: Relative time (ago(1h), ago(7d))\n- `between(start .. end)`: Range filtering\n- `startswith()`, `contains()`, `matches regex`: String filtering\n- `parse`, `extract`: Extract values from strings\n- `percentiles()`, `avg()`, `sum()`, `max()`, `min()`: Aggregations\n\n## Best Practices\n\n- Always include time range filters to optimize query performance\n- Use `take` or `limit` for exploratory queries to avoid large result sets\n- Leverage `summarize` for aggregations instead of client-side processing\n- Store frequently-used queries as functions in the database\n- Use materialized views for repeated aggregations\n- Monitor query performance and resource consumption\n- Apply data retention policies to manage storage costs\n- Use streaming ingestion for real-time analytics (\u003C 1 second latency)\n- Integrate with Azure Monitor for operational insights\n\n## MCP Tools Used\n\n| Tool | Purpose |\n|------|---------|\n| `kusto_cluster_list` | List all Azure Data Explorer clusters in a subscription |\n| `kusto_database_list` | List all databases in a specific Kusto cluster |\n| `kusto_query` | Execute KQL queries against a Kusto database |\n| `kusto_table_schema_get` | Retrieve schema information for a specific table |\n\n**Required Parameters**:\n- `subscription`: Azure subscription ID or display name\n- `cluster`: Kusto cluster name (e.g., \"mycluster\")\n- `database`: Database name\n- `query`: KQL query string (for query operations)\n- `table`: Table name (for schema operations)\n\n**Optional Parameters**:\n- `resource-group`: Resource group name (for listing operations)\n- `tenant`: Azure AD tenant ID\n\n## Fallback Strategy: Azure CLI Commands\n\nIf Azure MCP Kusto tools fail, timeout, or are unavailable, use Azure CLI commands as fallback.\n\n### CLI Command Reference\n\n| Operation | Azure CLI Command |\n|-----------|-------------------|\n| List clusters | `az kusto cluster list --resource-group \u003Crg-name>` |\n| List databases | `az kusto database list --cluster-name \u003Ccluster> --resource-group \u003Crg-name>` |\n| Show cluster | `az kusto cluster show --name \u003Ccluster> --resource-group \u003Crg-name>` |\n| Show database | `az kusto database show --cluster-name \u003Ccluster> --database-name \u003Cdb> --resource-group \u003Crg-name>` |\n\n### KQL Query via Azure CLI\n\nFor queries, use the Kusto REST API or direct cluster URL:\n```bash\naz rest --method post \\\n  --url \"https:\u002F\u002F\u003Ccluster>.\u003Cregion>.kusto.windows.net\u002Fv1\u002Frest\u002Fquery\" \\\n  --body \"{ \\\"db\\\": \\\"\u003Cdatabase>\\\", \\\"csl\\\": \\\"\u003Ckql-query>\\\" }\"\n```\n\n### When to Fallback\n\nSwitch to Azure CLI when:\n- MCP tool returns timeout error (queries > 60 seconds)\n- MCP tool returns \"service unavailable\" or connection errors\n- Authentication failures with MCP tools\n- Empty response when database is known to have data\n\n## Common Issues\n\n- **Access Denied**: Verify database permissions (Viewer role minimum for queries)\n- **Query Timeout**: Optimize query with time filters, reduce result set, or increase timeout\n- **Syntax Error**: Validate KQL syntax - common issues: missing pipes, incorrect operators\n- **Empty Results**: Check time range filters (may be too restrictive), verify table name\n- **Cluster Not Found**: Check cluster name format (exclude \".kusto.windows.net\" suffix)\n- **High CPU Usage**: Query too broad - add filters, reduce time range, limit aggregations\n- **Ingestion Lag**: Streaming data may have 1-30 second delay depending on ingestion method\n\n## Use Cases\n\n- **Log Analytics**: Application logs, system logs, audit logs\n- **IoT Analytics**: Sensor data, device telemetry, real-time monitoring\n- **Security Analytics**: SIEM data, threat detection, security event correlation\n- **APM**: Application performance metrics, user behavior, error tracking\n- **Business Intelligence**: Clickstream analysis, user analytics, operational KPIs","# Azure Data Explorer (Kusto) Query & Analytics\n\nExecute KQL queries and manage Azure Data Explorer resources for fast, scalable big data analytics on log, telemetry, and time series data.\n\n## Skill Activation Triggers\n\n**Use this skill immediately when the user asks to:**\n- \"Query my Kusto database for [data pattern]\"\n- \"Show me events in the last hour from Azure Data Explorer\"\n- \"Analyze logs in my ADX cluster\"\n- \"Run a KQL query on [database]\"\n- \"What tables are in my Kusto database?\"\n- \"Show me the schema for [table]\"\n- \"List my Azure Data Explorer clusters\"\n- \"Aggregate telemetry data by [dimension]\"\n- \"Create a time series chart from my logs\"\n\n**Key Indicators:**\n- Mentions \"Kusto\", \"Azure Data Explorer\", \"ADX\", or \"KQL\"\n- Log analytics or telemetry analysis requests\n- Time series data exploration\n- IoT data analysis queries\n- SIEM or security analytics tasks\n- Requests for data aggregation on large datasets\n- Performance monitoring or APM queries\n\n## Overview\n\nThis skill enables querying and managing Azure Data Explorer (Kusto), a fast and highly scalable data exploration service optimized for log and telemetry data. Azure Data Explorer provides sub-second query performance on billions of records using the Kusto Query Language (KQL).\n\nKey capabilities:\n- **Query Execution**: Run KQL queries against massive datasets\n- **Schema Exploration**: Discover tables, columns, and data types\n- **Resource Management**: List clusters and databases\n- **Analytics**: Aggregations, time series, anomaly detection, machine learning\n\n## Core Workflow\n\n1. **Discover Resources**: List available clusters and databases in subscription\n2. **Explore Schema**: Retrieve table structures to understand data model\n3. **Query Data**: Execute KQL queries for analysis, filtering, aggregation\n4. **Analyze Results**: Process query output for insights and reporting\n\n## Query Patterns\n\n### Pattern 1: Basic Data Retrieval\nFetch recent records from a table with simple filtering.\n\n**Example KQL**:\n```kql\nEvents\n| where Timestamp > ago(1h)\n| take 100\n```\n\n**Use for**: Quick data inspection, recent event retrieval\n\n### Pattern 2: Aggregation Analysis\nSummarize data by dimensions for insights and reporting.\n\n**Example KQL**:\n```kql\nEvents\n| summarize count() by EventType, bin(Timestamp, 1h)\n| order by count_ desc\n```\n\n**Use for**: Event counting, distribution analysis, top-N queries\n\n### Pattern 3: Time Series Analytics\nAnalyze data over time windows for trends and patterns.\n\n**Example KQL**:\n```kql\nTelemetry\n| where Timestamp > ago(24h)\n| summarize avg(ResponseTime), percentiles(ResponseTime, 50, 95, 99) by bin(Timestamp, 5m)\n| render timechart\n```\n\n**Use for**: Performance monitoring, trend analysis, anomaly detection\n\n### Pattern 4: Join and Correlation\nCombine multiple tables for cross-dataset analysis.\n\n**Example KQL**:\n```kql\nEvents\n| where EventType == \"Error\"\n| join kind=inner (\n    Logs\n    | where Severity == \"Critical\"\n) on CorrelationId\n| project Timestamp, EventType, LogMessage, Severity\n```\n\n**Use for**: Root cause analysis, correlated event tracking\n\n### Pattern 5: Schema Discovery\nExplore table structure before querying.\n\n**Tools**: `kusto_table_schema_get`\n\n**Use for**: Understanding data model, query planning\n\n## Key Data Fields\n\nWhen executing queries, common field patterns:\n- **Timestamp**: Time of event (datetime) - use `ago()`, `between()`, `bin()` for time filtering\n- **EventType\u002FCategory**: Classification field for grouping\n- **CorrelationId\u002FSessionId**: For tracing related events\n- **Severity\u002FLevel**: For filtering by importance\n- **Dimensions**: Custom properties for grouping and filtering\n\n## Result Format\n\nQuery results include:\n- **Columns**: Field names and data types\n- **Rows**: Data records matching query\n- **Statistics**: Row count, execution time, resource utilization\n- **Visualization**: Chart rendering hints (timechart, barchart, etc.)\n\n## KQL Best Practices\n\n**🟢 Performance Optimized:**\n- Filter early: Use `where` before joins and aggregations\n- Limit result size: Use `take` or `limit` to reduce data transfer\n- Time filters: Always filter by time range for time series data\n- Indexed columns: Filter on indexed columns first\n\n**🔵 Query Patterns:**\n- Use `summarize` for aggregations instead of `count()` alone\n- Use `bin()` for time bucketing in time series\n- Use `project` to select only needed columns\n- Use `extend` to add calculated fields\n\n**🟡 Common Functions:**\n- `ago(timespan)`: Relative time (ago(1h), ago(7d))\n- `between(start .. end)`: Range filtering\n- `startswith()`, `contains()`, `matches regex`: String filtering\n- `parse`, `extract`: Extract values from strings\n- `percentiles()`, `avg()`, `sum()`, `max()`, `min()`: Aggregations\n\n## Best Practices\n\n- Always include time range filters to optimize query performance\n- Use `take` or `limit` for exploratory queries to avoid large result sets\n- Leverage `summarize` for aggregations instead of client-side processing\n- Store frequently-used queries as functions in the database\n- Use materialized views for repeated aggregations\n- Monitor query performance and resource consumption\n- Apply data retention policies to manage storage costs\n- Use streaming ingestion for real-time analytics (\u003C 1 second latency)\n- Integrate with Azure Monitor for operational insights\n\n## MCP Tools Used\n\n| Tool | Purpose |\n|------|---------|\n| `kusto_cluster_list` | List all Azure Data Explorer clusters in a subscription |\n| `kusto_database_list` | List all databases in a specific Kusto cluster |\n| `kusto_query` | Execute KQL queries against a Kusto database |\n| `kusto_table_schema_get` | Retrieve schema information for a specific table |\n\n**Required Parameters**:\n- `subscription`: Azure subscription ID or display name\n- `cluster`: Kusto cluster name (e.g., \"mycluster\")\n- `database`: Database name\n- `query`: KQL query string (for query operations)\n- `table`: Table name (for schema operations)\n\n**Optional Parameters**:\n- `resource-group`: Resource group name (for listing operations)\n- `tenant`: Azure AD tenant ID\n\n## Fallback Strategy: Azure CLI Commands\n\nIf Azure MCP Kusto tools fail, timeout, or are unavailable, use Azure CLI commands as fallback.\n\n### CLI Command Reference\n\n| Operation | Azure CLI Command |\n|-----------|-------------------|\n| List clusters | `az kusto cluster list --resource-group \u003Crg-name>` |\n| List databases | `az kusto database list --cluster-name \u003Ccluster> --resource-group \u003Crg-name>` |\n| Show cluster | `az kusto cluster show --name \u003Ccluster> --resource-group \u003Crg-name>` |\n| Show database | `az kusto database show --cluster-name \u003Ccluster> --database-name \u003Cdb> --resource-group \u003Crg-name>` |\n\n### KQL Query via Azure CLI\n\nFor queries, use the Kusto REST API or direct cluster URL:\n```bash\naz rest --method post \\\n  --url \"https:\u002F\u002F\u003Ccluster>.\u003Cregion>.kusto.windows.net\u002Fv1\u002Frest\u002Fquery\" \\\n  --body \"{ \\\"db\\\": \\\"\u003Cdatabase>\\\", \\\"csl\\\": \\\"\u003Ckql-query>\\\" }\"\n```\n\n### When to Fallback\n\nSwitch to Azure CLI when:\n- MCP tool returns timeout error (queries > 60 seconds)\n- MCP tool returns \"service unavailable\" or connection errors\n- Authentication failures with MCP tools\n- Empty response when database is known to have data\n\n## Common Issues\n\n- **Access Denied**: Verify database permissions (Viewer role minimum for queries)\n- **Query Timeout**: Optimize query with time filters, reduce result set, or increase timeout\n- **Syntax Error**: Validate KQL syntax - common issues: missing pipes, incorrect operators\n- **Empty Results**: Check time range filters (may be too restrictive), verify table name\n- **Cluster Not Found**: Check cluster name format (exclude \".kusto.windows.net\" suffix)\n- **High CPU Usage**: Query too broad - add filters, reduce time range, limit aggregations\n- **Ingestion Lag**: Streaming data may have 1-30 second delay depending on ingestion method\n\n## Use Cases\n\n- **Log Analytics**: Application logs, system logs, audit logs\n- **IoT Analytics**: Sensor data, device telemetry, real-time monitoring\n- **Security Analytics**: SIEM data, threat detection, security event correlation\n- **APM**: Application performance metrics, user behavior, error tracking\n- **Business Intelligence**: Clickstream analysis, user analytics, operational KPIs",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"Microsoft","0.0.0-placeholder","master","63f17866001c5ca854bf2fa0b678ce277133de5b","skills\u002Fmarketplace\u002Fazure-kusto",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill azure-kusto",{"tool":43,"command":44},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill azure-kusto",{"tool":46,"command":47},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill azure-kusto","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fazure-kusto\u002FSKILL.md",true,[51,57],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"skill-report.json","REFERENCE","参考文档",47589,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fazure-kusto\u002Fskill-report.json",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"version.json",55,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fazure-kusto\u002Fversion.json",[62,70,77,84,91,98],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":69},"01M7DXW9N826PKXK174PVW3038","serpmaven","Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":69},"01M7DXVHSTWDV65475QEQ915M7","revnu-landing-page-audit","Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: \"audit my landing page\", \"why isn't this page converting\", \"review my homepage\", \"my ads get clicks but no signups\", \"people bounce from the pricing page\", \"CRO review\", \"improve conversion rate\", \"is my hero section clear\", \"roast my landing page\", \"rewrite my headline\", \"what's wrong with this page\", \"landing page feedback\", \"make the signup page convert better\". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":69},"01M7DXV8X2D7B3VTD4HHYYHTGR","revnu-growth-context","Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents\u002Frevnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says \"set up our marketing context\", \"who is our ideal customer\", \"write our ICP\", \"describe the product for marketing\", \"positioning doc\", \"what's our brand voice\", \"remember this about our customers\", \"log what we tried\", \"what have we learned from marketing\", \"we changed pricing, update the context\", \"update our growth notes\", \"summarize the business for the agent\", \"import my product-marketing.md\", \"start a growth doc\", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":69},"01M7DXV0DGJ1G0A60PAHC6J3C5","revnu-get-listed","Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: \"best X\" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says \"get us listed\", \"which directories should we submit to\", \"how do we get into best-of lists\", \"why does ChatGPT recommend competitors and not us\", \"get mentioned in AI answers\", \"submit to awesome lists\", \"get on G2\", \"where are our competitors listed\", \"pitch listicle authors\", \"find backlink opportunities\", \"launch directories\", \"get into roundups\", \"Product Hunt alternatives\", \"where should we be listed\", \"get cited by Perplexity\". Never submits, pays or posts without a yes. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":69},"01M7DXTSPMGT9D6DSS0HP9BSTA","revnu-ai-readiness-audit","Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks \"is my site ready for AI search\", \"audit my site for AI answers\", \"AEO audit\", \"GEO audit\", \"why doesn't ChatGPT quote our pricing\", \"make our pages citable by AI\", \"do I need llms.txt\", \"does schema help with ChatGPT\", \"check our structured data\", \"is our content visible without JavaScript\", \"AI SEO audit\", \"optimize our homepage for AI answers\", \"LLM SEO check\", \"why does AI get our product wrong\", \"fix our site for AI Overviews\". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":69},"01M7DXSZHCVTRS620GC3S97JZV","proxy-troubleshooting","Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]