[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MFVVK00RTDBAFQSYEWJNXB":3,"skill-same:01M6MFVVK00RTDBAFQSYEWJNXB":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6MFVVK00RTDBAFQSYEWJNXB","customer-success-manager",null,"Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success. Use when analyzing customer accounts, reviewing retention metrics, scoring at-risk customers, or when the user mentions churn, customer health scores, upsell opportunities, expansion revenue, retention analysis, or customer analytics. Runs three Python CLI tools to produce deterministic health scores, churn risk tiers, and prioritized expansion recommendations across Enterprise, Mid-Market, and SMB segments.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-customer-success-manager-skill-01e4db57\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"customer","manager","customer success manager","expansion","cli","upsell","at","retention analysis","segments","churn","retention","revenue","recommendations","across","opportunity","scoring","analysis","smb","analyzing","analytics","2026-11-10 10:12:30",false,"---\nname: \"customer-success-manager\"\ndescription: Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success. Use when analyzing customer accounts, reviewing retention metrics, scoring at-risk customers, or when the user mentions churn, customer health scores, upsell opportunities, expansion revenue, retention analysis, or customer analytics. Runs three Python CLI tools to produce deterministic health scores, churn risk tiers, and prioritized expansion recommendations across Enterprise, Mid-Market, and SMB segments.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: business-growth\n  domain: customer-success\n  updated: 2026-02-06\n  python-tools: health_score_calculator.py, churn_risk_analyzer.py, expansion_opportunity_scorer.py\n  tech-stack: customer-success, saas-metrics, health-scoring\n---\n\n# Customer Success Manager\n\nProduction-grade customer success analytics with multi-dimensional health scoring, churn risk prediction, and expansion opportunity identification. Three Python CLI tools provide deterministic, repeatable analysis using standard library only -- no external dependencies, no API calls, no ML models.\n\n---\n\n## Table of Contents\n\n- [Input Requirements](#input-requirements)\n- [Output Formats](#output-formats)\n- [How to Use](#how-to-use)\n- [Scripts](#scripts)\n- [Reference Guides](#reference-guides)\n- [Templates](#templates)\n- [Best Practices](#best-practices)\n- [Limitations](#limitations)\n\n---\n\n## Input Requirements\n\nAll scripts accept a JSON file as positional input argument. See `assets\u002Fsample_customer_data.json` for complete schema examples and sample data.\n\n### Health Score Calculator\n\nRequired fields per customer object: `customer_id`, `name`, `segment`, `arr`, and nested objects `usage` (login_frequency, feature_adoption, dau_mau_ratio), `engagement` (support_ticket_volume, meeting_attendance, nps_score, csat_score), `support` (open_tickets, escalation_rate, avg_resolution_hours), `relationship` (executive_sponsor_engagement, multi_threading_depth, renewal_sentiment), and `previous_period` scores for trend analysis.\n\n### Churn Risk Analyzer\n\nRequired fields per customer object: `customer_id`, `name`, `segment`, `arr`, `contract_end_date`, and nested objects `usage_decline`, `engagement_drop`, `support_issues`, `relationship_signals`, and `commercial_factors`.\n\n### Expansion Opportunity Scorer\n\nRequired fields per customer object: `customer_id`, `name`, `segment`, `arr`, and nested objects `contract` (licensed_seats, active_seats, plan_tier, available_tiers), `product_usage` (per-module adoption flags and usage percentages), and `departments` (current and potential).\n\n---\n\n## Output Formats\n\nAll scripts support two output formats via the `--format` flag:\n\n- **`text`** (default): Human-readable formatted output for terminal viewing\n- **`json`**: Machine-readable JSON output for integrations and pipelines\n\n---\n\n## How to Use\n\n### Quick Start\n\n```bash\n# Health scoring\npython scripts\u002Fhealth_score_calculator.py assets\u002Fsample_customer_data.json\npython scripts\u002Fhealth_score_calculator.py assets\u002Fsample_customer_data.json --format json\n\n# Churn risk analysis\npython scripts\u002Fchurn_risk_analyzer.py assets\u002Fsample_customer_data.json\npython scripts\u002Fchurn_risk_analyzer.py assets\u002Fsample_customer_data.json --format json\n\n# Expansion opportunity scoring\npython scripts\u002Fexpansion_opportunity_scorer.py assets\u002Fsample_customer_data.json\npython scripts\u002Fexpansion_opportunity_scorer.py assets\u002Fsample_customer_data.json --format json\n```\n\n### Workflow Integration\n\n```bash\n# 1. Score customer health across portfolio\npython scripts\u002Fhealth_score_calculator.py customer_portfolio.json --format json > health_results.json\n# Verify: confirm health_results.json contains the expected number of customer records before continuing\n\n# 2. Identify at-risk accounts\npython scripts\u002Fchurn_risk_analyzer.py customer_portfolio.json --format json > risk_results.json\n# Verify: confirm risk_results.json is non-empty and risk tiers are present for each customer\n\n# 3. Find expansion opportunities in healthy accounts\npython scripts\u002Fexpansion_opportunity_scorer.py customer_portfolio.json --format json > expansion_results.json\n# Verify: confirm expansion_results.json lists opportunities ranked by priority\n\n# 4. Prepare QBR using templates\n# Reference: assets\u002Fqbr_template.md\n```\n\n**Error handling:** If a script exits with an error, check that:\n- The input JSON matches the required schema for that script (see Input Requirements above)\n- All required fields are present and correctly typed\n- Python 3.7+ is being used (`python --version`)\n- Output files from prior steps are non-empty before piping into subsequent steps\n\n---\n\n## Scripts\n\n### 1. health_score_calculator.py\n\n**Purpose:** Multi-dimensional customer health scoring with trend analysis and segment-aware benchmarking.\n\n**Dimensions and Weights:**\n| Dimension | Weight | Metrics |\n|-----------|--------|---------|\n| Usage | 30% | Login frequency, feature adoption, DAU\u002FMAU ratio |\n| Engagement | 25% | Support ticket volume, meeting attendance, NPS\u002FCSAT |\n| Support | 20% | Open tickets, escalation rate, avg resolution time |\n| Relationship | 25% | Executive sponsor engagement, multi-threading depth, renewal sentiment |\n\n**Classification:**\n- Green (75-100): Healthy -- customer achieving value\n- Yellow (50-74): Needs attention -- monitor closely\n- Red (0-49): At risk -- immediate intervention required\n\n**Usage:**\n```bash\npython scripts\u002Fhealth_score_calculator.py customer_data.json\npython scripts\u002Fhealth_score_calculator.py customer_data.json --format json\n```\n\n### 2. churn_risk_analyzer.py\n\n**Purpose:** Identify at-risk accounts with behavioral signal detection and tier-based intervention recommendations.\n\n**Risk Signal Weights:**\n| Signal Category | Weight | Indicators |\n|----------------|--------|------------|\n| Usage Decline | 30% | Login trend, feature adoption change, DAU\u002FMAU change |\n| Engagement Drop | 25% | Meeting cancellations, response time, NPS change |\n| Support Issues | 20% | Open escalations, unresolved critical, satisfaction trend |\n| Relationship Signals | 15% | Champion left, sponsor change, competitor mentions |\n| Commercial Factors | 10% | Contract type, pricing complaints, budget cuts |\n\n**Risk Tiers:**\n- Critical (80-100): Immediate executive escalation\n- High (60-79): Urgent CSM intervention\n- Medium (40-59): Proactive outreach\n- Low (0-39): Standard monitoring\n\n**Usage:**\n```bash\npython scripts\u002Fchurn_risk_analyzer.py customer_data.json\npython scripts\u002Fchurn_risk_analyzer.py customer_data.json --format json\n```\n\n### 3. expansion_opportunity_scorer.py\n\n**Purpose:** Identify upsell, cross-sell, and expansion opportunities with revenue estimation and priority ranking.\n\n**Expansion Types:**\n- **Upsell**: Upgrade to higher tier or more of existing product\n- **Cross-sell**: Add new product modules\n- **Expansion**: Additional seats or departments\n\n**Usage:**\n```bash\npython scripts\u002Fexpansion_opportunity_scorer.py customer_data.json\npython scripts\u002Fexpansion_opportunity_scorer.py customer_data.json --format json\n```\n\n---\n\n## Reference Guides\n\n| Reference | Description |\n|-----------|-------------|\n| `references\u002Fhealth-scoring-framework.md` | Complete health scoring methodology, dimension definitions, weighting rationale, threshold calibration |\n| `references\u002Fcs-playbooks.md` | Intervention playbooks for each risk tier, onboarding, renewal, expansion, and escalation procedures |\n| `references\u002Fcs-metrics-benchmarks.md` | Industry benchmarks for NRR, GRR, churn rates, health scores, expansion rates by segment and industry |\n\n---\n\n## Templates\n\n| Template | Purpose |\n|----------|---------|\n| `assets\u002Fqbr_template.md` | Quarterly Business Review presentation structure |\n| `assets\u002Fsuccess_plan_template.md` | Customer success plan with goals, milestones, and metrics |\n| `assets\u002Fonboarding_checklist_template.md` | 90-day onboarding checklist with phase gates |\n| `assets\u002Fexecutive_business_review_template.md` | Executive stakeholder review for strategic accounts |\n\n---\n\n## Best Practices\n\n1. **Combine signals**: Use all three scripts together for a complete customer picture\n2. **Act on trends, not snapshots**: A declining Green is more urgent than a stable Yellow\n3. **Calibrate thresholds**: Adjust segment benchmarks based on your product and industry per `references\u002Fhealth-scoring-framework.md`\n4. **Prepare with data**: Run scripts before every QBR and executive meeting; reference `references\u002Fcs-playbooks.md` for intervention guidance\n\n---\n\n## Limitations\n\n- **No real-time data**: Scripts analyze point-in-time snapshots from JSON input files\n- **No CRM integration**: Data must be exported manually from your CRM\u002FCS platform\n- **Deterministic only**: No predictive ML -- scoring is algorithmic based on weighted signals\n- **Threshold tuning**: Default thresholds are industry-standard but may need calibration for your business\n- **Revenue estimates**: Expansion revenue estimates are approximations based on usage patterns\n\n---\n\n**Last Updated:** February 2026\n**Tools:** 3 Python CLI tools\n**Dependencies:** Python 3.7+ standard library only\n","# Customer Success Manager\n\nProduction-grade customer success analytics with multi-dimensional health scoring, churn risk prediction, and expansion opportunity identification. Three Python CLI tools provide deterministic, repeatable analysis using standard library only -- no external dependencies, no API calls, no ML models.\n\n---\n\n## Table of Contents\n\n- [Input Requirements](#input-requirements)\n- [Output Formats](#output-formats)\n- [How to Use](#how-to-use)\n- [Scripts](#scripts)\n- [Reference Guides](#reference-guides)\n- [Templates](#templates)\n- [Best Practices](#best-practices)\n- [Limitations](#limitations)\n\n---\n\n## Input Requirements\n\nAll scripts accept a JSON file as positional input argument. See `assets\u002Fsample_customer_data.json` for complete schema examples and sample data.\n\n### Health Score Calculator\n\nRequired fields per customer object: `customer_id`, `name`, `segment`, `arr`, and nested objects `usage` (login_frequency, feature_adoption, dau_mau_ratio), `engagement` (support_ticket_volume, meeting_attendance, nps_score, csat_score), `support` (open_tickets, escalation_rate, avg_resolution_hours), `relationship` (executive_sponsor_engagement, multi_threading_depth, renewal_sentiment), and `previous_period` scores for trend analysis.\n\n### Churn Risk Analyzer\n\nRequired fields per customer object: `customer_id`, `name`, `segment`, `arr`, `contract_end_date`, and nested objects `usage_decline`, `engagement_drop`, `support_issues`, `relationship_signals`, and `commercial_factors`.\n\n### Expansion Opportunity Scorer\n\nRequired fields per customer object: `customer_id`, `name`, `segment`, `arr`, and nested objects `contract` (licensed_seats, active_seats, plan_tier, available_tiers), `product_usage` (per-module adoption flags and usage percentages), and `departments` (current and potential).\n\n---\n\n## Output Formats\n\nAll scripts support two output formats via the `--format` flag:\n\n- **`text`** (default): Human-readable formatted output for terminal viewing\n- **`json`**: Machine-readable JSON output for integrations and pipelines\n\n---\n\n## How to Use\n\n### Quick Start\n\n```bash\n# Health scoring\npython scripts\u002Fhealth_score_calculator.py assets\u002Fsample_customer_data.json\npython scripts\u002Fhealth_score_calculator.py assets\u002Fsample_customer_data.json --format json\n\n# Churn risk analysis\npython scripts\u002Fchurn_risk_analyzer.py assets\u002Fsample_customer_data.json\npython scripts\u002Fchurn_risk_analyzer.py assets\u002Fsample_customer_data.json --format json\n\n# Expansion opportunity scoring\npython scripts\u002Fexpansion_opportunity_scorer.py assets\u002Fsample_customer_data.json\npython scripts\u002Fexpansion_opportunity_scorer.py assets\u002Fsample_customer_data.json --format json\n```\n\n### Workflow Integration\n\n```bash\n# 1. Score customer health across portfolio\npython scripts\u002Fhealth_score_calculator.py customer_portfolio.json --format json > health_results.json\n# Verify: confirm health_results.json contains the expected number of customer records before continuing\n\n# 2. Identify at-risk accounts\npython scripts\u002Fchurn_risk_analyzer.py customer_portfolio.json --format json > risk_results.json\n# Verify: confirm risk_results.json is non-empty and risk tiers are present for each customer\n\n# 3. Find expansion opportunities in healthy accounts\npython scripts\u002Fexpansion_opportunity_scorer.py customer_portfolio.json --format json > expansion_results.json\n# Verify: confirm expansion_results.json lists opportunities ranked by priority\n\n# 4. Prepare QBR using templates\n# Reference: assets\u002Fqbr_template.md\n```\n\n**Error handling:** If a script exits with an error, check that:\n- The input JSON matches the required schema for that script (see Input Requirements above)\n- All required fields are present and correctly typed\n- Python 3.7+ is being used (`python --version`)\n- Output files from prior steps are non-empty before piping into subsequent steps\n\n---\n\n## Scripts\n\n### 1. health_score_calculator.py\n\n**Purpose:** Multi-dimensional customer health scoring with trend analysis and segment-aware benchmarking.\n\n**Dimensions and Weights:**\n| Dimension | Weight | Metrics |\n|-----------|--------|---------|\n| Usage | 30% | Login frequency, feature adoption, DAU\u002FMAU ratio |\n| Engagement | 25% | Support ticket volume, meeting attendance, NPS\u002FCSAT |\n| Support | 20% | Open tickets, escalation rate, avg resolution time |\n| Relationship | 25% | Executive sponsor engagement, multi-threading depth, renewal sentiment |\n\n**Classification:**\n- Green (75-100): Healthy -- customer achieving value\n- Yellow (50-74): Needs attention -- monitor closely\n- Red (0-49): At risk -- immediate intervention required\n\n**Usage:**\n```bash\npython scripts\u002Fhealth_score_calculator.py customer_data.json\npython scripts\u002Fhealth_score_calculator.py customer_data.json --format json\n```\n\n### 2. churn_risk_analyzer.py\n\n**Purpose:** Identify at-risk accounts with behavioral signal detection and tier-based intervention recommendations.\n\n**Risk Signal Weights:**\n| Signal Category | Weight | Indicators |\n|----------------|--------|------------|\n| Usage Decline | 30% | Login trend, feature adoption change, DAU\u002FMAU change |\n| Engagement Drop | 25% | Meeting cancellations, response time, NPS change |\n| Support Issues | 20% | Open escalations, unresolved critical, satisfaction trend |\n| Relationship Signals | 15% | Champion left, sponsor change, competitor mentions |\n| Commercial Factors | 10% | Contract type, pricing complaints, budget cuts |\n\n**Risk Tiers:**\n- Critical (80-100): Immediate executive escalation\n- High (60-79): Urgent CSM intervention\n- Medium (40-59): Proactive outreach\n- Low (0-39): Standard monitoring\n\n**Usage:**\n```bash\npython scripts\u002Fchurn_risk_analyzer.py customer_data.json\npython scripts\u002Fchurn_risk_analyzer.py customer_data.json --format json\n```\n\n### 3. expansion_opportunity_scorer.py\n\n**Purpose:** Identify upsell, cross-sell, and expansion opportunities with revenue estimation and priority ranking.\n\n**Expansion Types:**\n- **Upsell**: Upgrade to higher tier or more of existing product\n- **Cross-sell**: Add new product modules\n- **Expansion**: Additional seats or departments\n\n**Usage:**\n```bash\npython scripts\u002Fexpansion_opportunity_scorer.py customer_data.json\npython scripts\u002Fexpansion_opportunity_scorer.py customer_data.json --format json\n```\n\n---\n\n## Reference Guides\n\n| Reference | Description |\n|-----------|-------------|\n| `references\u002Fhealth-scoring-framework.md` | Complete health scoring methodology, dimension definitions, weighting rationale, threshold calibration |\n| `references\u002Fcs-playbooks.md` | Intervention playbooks for each risk tier, onboarding, renewal, expansion, and escalation procedures |\n| `references\u002Fcs-metrics-benchmarks.md` | Industry benchmarks for NRR, GRR, churn rates, health scores, expansion rates by segment and industry |\n\n---\n\n## Templates\n\n| Template | Purpose |\n|----------|---------|\n| `assets\u002Fqbr_template.md` | Quarterly Business Review presentation structure |\n| `assets\u002Fsuccess_plan_template.md` | Customer success plan with goals, milestones, and metrics |\n| `assets\u002Fonboarding_checklist_template.md` | 90-day onboarding checklist with phase gates |\n| `assets\u002Fexecutive_business_review_template.md` | Executive stakeholder review for strategic accounts |\n\n---\n\n## Best Practices\n\n1. **Combine signals**: Use all three scripts together for a complete customer picture\n2. **Act on trends, not snapshots**: A declining Green is more urgent than a stable Yellow\n3. **Calibrate thresholds**: Adjust segment benchmarks based on your product and industry per `references\u002Fhealth-scoring-framework.md`\n4. **Prepare with data**: Run scripts before every QBR and executive meeting; reference `references\u002Fcs-playbooks.md` for intervention guidance\n\n---\n\n## Limitations\n\n- **No real-time data**: Scripts analyze point-in-time snapshots from JSON input files\n- **No CRM integration**: Data must be exported manually from your CRM\u002FCS platform\n- **Deterministic only**: No predictive ML -- scoring is algorithmic based on weighted signals\n- **Threshold tuning**: Default thresholds are industry-standard but may need calibration for your business\n- **Revenue estimates**: Expansion revenue estimates are approximations based on usage patterns\n\n---\n\n**Last Updated:** February 2026\n**Tools:** 3 Python CLI tools\n**Dependencies:** Python 3.7+ standard library only\n",{"name":5,"license":14,"metadata":43,"description":7},{"author":44,"domain":45,"updated":46,"version":47,"category":48,"tech-stack":49,"python-tools":50},"Alireza Rezvani","customer-success",1770336000000,"1.0.0","business-growth","customer-success, saas-metrics, health-scoring","health_score_calculator.py, churn_risk_analyzer.py, expansion_opportunity_scorer.py","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-customer-success-manager-skill-01e4db57","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill customer-success-manager",{"tool":63,"command":64},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill customer-success-manager",{"tool":66,"command":67},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill customer-success-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-customer-success-manager-skill-01e4db57\u002FSKILL.md",true,[],[72,98,124,157,185,220],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":38},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[74,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","use","ready","unrelated","app","scope","for","webmcp",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":102,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":38},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[106,107,108,22,109,110,111,112,113,114,115,116,117,118,119,120,121,122,24,123],"vardoger analyze","analyze","directory","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","copilot instructions",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":138,"publishedAt":38},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[130,135],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":136,"categoryName":137,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000023","Skill与智能体开发",[139,140,141,142,143,144,145,146,147,148,149,150,151,91,152,153,154,155,96,156],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":166,"publishedAt":38},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000011","运维与部署",[167,168,169,170,171,172,173,174,175,91,176,177,178,179,180,181,182,183,184,96],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":202,"publishedAt":38},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[191,194,199],{"categoryNo":192,"categoryName":193,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":195,"categoryName":196,"taxonomyType":197,"taxonomyTypeDesc":198},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":200,"categoryName":201,"taxonomyType":197,"taxonomyTypeDesc":198},"01JBSEEDCAT000000000000038","人力资源",[203,204,205,206,207,208,209,210,107,211,91,212,213,214,215,216,217,218,96,219],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":226,"publishedAt":38},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[227,228,18,229,230,206,231,91,216,232,233,234,235,236,237,238,239,240,96,241],"steno mode","mode","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]