[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HPPGAX130SXVC6ZXJ2FXF":3,"skill-same:01M71HPPGAX130SXVC6ZXJ2FXF":133},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M71HPPGAX130SXVC6ZXJ2FXF","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.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"manager","customer success manager","customer","retention analysis","analyzing","at","2026","recommendations","revenue","cli","smb","upsell","across","scoring","analysis","when","opportunity","churn risk","retention","churn","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":15,"metadata":44,"description":7},{"author":45,"domain":46,"updated":47,"version":48,"category":49,"tech-stack":50,"python-tools":51},"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","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill customer-success-manager",{"tool":67,"command":68},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill customer-success-manager",{"tool":70,"command":71},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill customer-success-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002FSKILL.md",true,[75,81,87,91,95,99,103,107,111,115,119,125,129],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"_AIWF_IMPORT.json","REFERENCE","参考文档",370,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002F_AIWF_IMPORT.json",{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"assets\u002Fexecutive_business_review_template.md","ASSET","资产文件",6951,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Fassets\u002Fexecutive_business_review_template.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Fexpected_output.json",4280,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Fassets\u002Fexpected_output.json",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Fonboarding_checklist_template.md",7353,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Fassets\u002Fonboarding_checklist_template.md",{"path":96,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":97,"sourceHtmlUrl":98},"assets\u002Fqbr_template.md",4711,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Fassets\u002Fqbr_template.md",{"path":100,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":101,"sourceHtmlUrl":102},"assets\u002Fsample_customer_data.json",9231,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Fassets\u002Fsample_customer_data.json",{"path":104,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":105,"sourceHtmlUrl":106},"assets\u002Fsuccess_plan_template.md",5889,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Fassets\u002Fsuccess_plan_template.md",{"path":108,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fcs-metrics-benchmarks.md",9116,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Freferences\u002Fcs-metrics-benchmarks.md",{"path":112,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fcs-playbooks.md",10656,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Freferences\u002Fcs-playbooks.md",{"path":116,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fhealth-scoring-framework.md",8540,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Freferences\u002Fhealth-scoring-framework.md",{"path":120,"resourceType":121,"resourceTypeDesc":122,"sizeBytes":123,"sourceHtmlUrl":124},"scripts\u002Fchurn_risk_analyzer.py","SCRIPT","脚本",19540,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Fscripts\u002Fchurn_risk_analyzer.py",{"path":126,"resourceType":121,"resourceTypeDesc":122,"sizeBytes":127,"sourceHtmlUrl":128},"scripts\u002Fexpansion_opportunity_scorer.py",15734,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Fscripts\u002Fexpansion_opportunity_scorer.py",{"path":130,"resourceType":121,"resourceTypeDesc":122,"sizeBytes":131,"sourceHtmlUrl":132},"scripts\u002Fhealth_score_calculator.py",16651,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fcustomer-success-manager\u002Fscripts\u002Fhealth_score_calculator.py",[134,166,189,211,231,254],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":145,"publishedAt":165},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[140],{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[146,147,148,149,150,151,152,153,154,155,156,157,158,159,34,160,161,162,163,164],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":173,"publishedAt":165},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[172],{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},[146,174,175,150,176,177,178,179,159,180,34,181,160,182,183,184,185,186,187,188],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":165},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[195],{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},[146,197,198,150,199,179,200,34,201,181,160,202,203,204,205,206,207,208,209,210],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":218,"publishedAt":165},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[217],{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},[219,150,220,207,221,222,223,224,210,225,226,227,34,228,181,160,229,230,161,146],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":240,"publishedAt":165},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[237],{"categoryNo":238,"categoryName":239,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000010","后端与接口",[241,242,243,244,199,245,246,247,188,208,179,248,249,200,250,227,251,252,253,34],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":255,"name":256,"nameZh":6,"description":257,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":258,"categories":259,"keywords":261,"publishedAt":277},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[260],{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},[262,263,264,265,266,156,267,224,268,159,269,270,34,146,271,272,273,274,275,276],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]