New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Monitors customer health, predicts churn risk

Customer success manager

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

Customer success manager cover

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,…

---
name: "customer-success-manager"
description: 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.
license: MIT
metadata:
  version: 1.0.0
  author: Alireza Rezvani
  category: business-growth
  domain: customer-success
  updated: 2026-02-06
  python-tools: health_score_calculator.py, churn_risk_analyzer.py, expansion_opportunity_scorer.py
  tech-stack: customer-success, saas-metrics, health-scoring
---

# Customer Success Manager

Production-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.

Overview

Production-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.

What you get

  • text(default): Human-readable formatted output for terminal viewing
  • jsonMachine-readable JSON output for integrations and pipelines
Manual install (npx, ZIP)
Claude Codenpx skills add alirezarezvani/claude-skills --skill customer-success-manager -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \ | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/business-growth/skills/customer-success-manager
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/25767c2d9c5874ce1cac/customer-success-manager.zip" -OutFile "$env:TEMP\customer-success-manager.zip"; Expand-Archive "$env:TEMP\customer-success-manager.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md9.0 KB
  • assets/6 files · 37.5 KB
  • references/3 files · 27.6 KB
  • scripts/3 files · 52.1 KB
Read the files here
alirezarezvani/19392f713 files
SKILL.md
Show the full text216 lines

Customer Success Manager

Production-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.


Table of Contents


Input Requirements

All scripts accept a JSON file as positional input argument. See assets/sample_customer_data.json for complete schema examples and sample data.

Health Score Calculator

Required 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.

Churn Risk Analyzer

Required 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.

Expansion Opportunity Scorer

Required 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).


Output Formats

All scripts support two output formats via the --format flag:

  • text (default): Human-readable formatted output for terminal viewing
  • json: Machine-readable JSON output for integrations and pipelines

How to Use

Quick Start
# Health scoring
python scripts/health_score_calculator.py assets/sample_customer_data.json
python scripts/health_score_calculator.py assets/sample_customer_data.json --format json

# Churn risk analysis
python scripts/churn_risk_analyzer.py assets/sample_customer_data.json
python scripts/churn_risk_analyzer.py assets/sample_customer_data.json --format json

# Expansion opportunity scoring
python scripts/expansion_opportunity_scorer.py assets/sample_customer_data.json
python scripts/expansion_opportunity_scorer.py assets/sample_customer_data.json --format json
Workflow Integration
# 1. Score customer health across portfolio
python scripts/health_score_calculator.py customer_portfolio.json --format json > health_results.json
# Verify: confirm health_results.json contains the expected number of customer records before continuing

# 2. Identify at-risk accounts
python scripts/churn_risk_analyzer.py customer_portfolio.json --format json > risk_results.json
# Verify: confirm risk_results.json is non-empty and risk tiers are present for each customer

# 3. Find expansion opportunities in healthy accounts
python scripts/expansion_opportunity_scorer.py customer_portfolio.json --format json > expansion_results.json
# Verify: confirm expansion_results.json lists opportunities ranked by priority

# 4. Prepare QBR using templates
# Reference: assets/qbr_template.md

Error handling: If a script exits with an error, check that:

  • The input JSON matches the required schema for that script (see Input Requirements above)
  • All required fields are present and correctly typed
  • Python 3.7+ is being used (python --version)
  • Output files from prior steps are non-empty before piping into subsequent steps

Scripts

1. health_score_calculator.py

Purpose: Multi-dimensional customer health scoring with trend analysis and segment-aware benchmarking.

Dimensions and Weights:

Dimension Weight Metrics
Usage 30% Login frequency, feature adoption, DAU/MAU ratio
Engagement 25% Support ticket volume, meeting attendance, NPS/CSAT
Support 20% Open tickets, escalation rate, avg resolution time
Relationship 25% Executive sponsor engagement, multi-threading depth, renewal sentiment

Classification:

  • Green (75-100): Healthy -- customer achieving value
  • Yellow (50-74): Needs attention -- monitor closely
  • Red (0-49): At risk -- immediate intervention required

Usage:

python scripts/health_score_calculator.py customer_data.json
python scripts/health_score_calculator.py customer_data.json --format json
2. churn_risk_analyzer.py

Purpose: Identify at-risk accounts with behavioral signal detection and tier-based intervention recommendations.

Risk Signal Weights:

Signal Category Weight Indicators
Usage Decline 30% Login trend, feature adoption change, DAU/MAU change
Engagement Drop 25% Meeting cancellations, response time, NPS change
Support Issues 20% Open escalations, unresolved critical, satisfaction trend
Relationship Signals 15% Champion left, sponsor change, competitor mentions
Commercial Factors 10% Contract type, pricing complaints, budget cuts

Risk Tiers:

  • Critical (80-100): Immediate executive escalation
  • High (60-79): Urgent CSM intervention
  • Medium (40-59): Proactive outreach
  • Low (0-39): Standard monitoring

Usage:

python scripts/churn_risk_analyzer.py customer_data.json
python scripts/churn_risk_analyzer.py customer_data.json --format json
3. expansion_opportunity_scorer.py

Purpose: Identify upsell, cross-sell, and expansion opportunities with revenue estimation and priority ranking.

Expansion Types:

  • Upsell: Upgrade to higher tier or more of existing product
  • Cross-sell: Add new product modules
  • Expansion: Additional seats or departments

Usage:

python scripts/expansion_opportunity_scorer.py customer_data.json
python scripts/expansion_opportunity_scorer.py customer_data.json --format json

Reference Guides

Reference Description
references/health-scoring-framework.md Complete health scoring methodology, dimension definitions, weighting rationale, threshold calibration
references/cs-playbooks.md Intervention playbooks for each risk tier, onboarding, renewal, expansion, and escalation procedures
references/cs-metrics-benchmarks.md Industry benchmarks for NRR, GRR, churn rates, health scores, expansion rates by segment and industry

Templates

Template Purpose
assets/qbr_template.md Quarterly Business Review presentation structure
assets/success_plan_template.md Customer success plan with goals, milestones, and metrics
assets/onboarding_checklist_template.md 90-day onboarding checklist with phase gates
assets/executive_business_review_template.md Executive stakeholder review for strategic accounts

Best Practices

  1. Combine signals: Use all three scripts together for a complete customer picture
  2. Act on trends, not snapshots: A declining Green is more urgent than a stable Yellow
  3. Calibrate thresholds: Adjust segment benchmarks based on your product and industry per references/health-scoring-framework.md
  4. Prepare with data: Run scripts before every QBR and executive meeting; reference references/cs-playbooks.md for intervention guidance

Limitations

  • No real-time data: Scripts analyze point-in-time snapshots from JSON input files
  • No CRM integration: Data must be exported manually from your CRM/CS platform
  • Deterministic only: No predictive ML -- scoring is algorithmic based on weighted signals
  • Threshold tuning: Default thresholds are industry-standard but may need calibration for your business
  • Revenue estimates: Expansion revenue estimates are approximations based on usage patterns

Last Updated: February 2026 Tools: 3 Python CLI tools Dependencies: Python 3.7+ standard library only

1---
2name: "customer-success-manager"
3description: 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.
4license: MIT
5metadata:
6 version: 1.0.0
7 author: Alireza Rezvani
8 category: business-growth
9 domain: customer-success
10 updated: 2026-02-06
11 python-tools: health_score_calculator.py, churn_risk_analyzer.py, expansion_opportunity_scorer.py
12 tech-stack: customer-success, saas-metrics, health-scoring
13---
14 
15# Customer Success Manager
16 
17Production-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.
18 
19---
20 
21## Table of Contents
22 
23- [Input Requirements](#input-requirements)
24- [Output Formats](#output-formats)
25- [How to Use](#how-to-use)
26- [Scripts](#scripts)
27- [Reference Guides](#reference-guides)
28- [Templates](#templates)
29- [Best Practices](#best-practices)
30- [Limitations](#limitations)
31 
32---
33 
34## Input Requirements
35 
36All scripts accept a JSON file as positional input argument. See `assets/sample_customer_data.json` for complete schema examples and sample data.
37 
38### Health Score Calculator
39 
40Required 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.
41 
42### Churn Risk Analyzer
43 
44Required 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`.
45 
46### Expansion Opportunity Scorer
47 
48Required 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).
49 
50---
51 
52## Output Formats
53 
54All scripts support two output formats via the `--format` flag:
55 
56- **`text`** (default): Human-readable formatted output for terminal viewing
57- **`json`**: Machine-readable JSON output for integrations and pipelines
58 
59---
60 
61## How to Use
62 
63### Quick Start
64 
65```bash
66# Health scoring
67python scripts/health_score_calculator.py assets/sample_customer_data.json
68python scripts/health_score_calculator.py assets/sample_customer_data.json --format json
69 
70# Churn risk analysis
71python scripts/churn_risk_analyzer.py assets/sample_customer_data.json
72python scripts/churn_risk_analyzer.py assets/sample_customer_data.json --format json
73 
74# Expansion opportunity scoring
75python scripts/expansion_opportunity_scorer.py assets/sample_customer_data.json
76python scripts/expansion_opportunity_scorer.py assets/sample_customer_data.json --format json
77```
78 
79### Workflow Integration
80 
81```bash
82# 1. Score customer health across portfolio
83python scripts/health_score_calculator.py customer_portfolio.json --format json > health_results.json
84# Verify: confirm health_results.json contains the expected number of customer records before continuing
85 
86# 2. Identify at-risk accounts
87python scripts/churn_risk_analyzer.py customer_portfolio.json --format json > risk_results.json
88# Verify: confirm risk_results.json is non-empty and risk tiers are present for each customer
89 
90# 3. Find expansion opportunities in healthy accounts
91python scripts/expansion_opportunity_scorer.py customer_portfolio.json --format json > expansion_results.json
92# Verify: confirm expansion_results.json lists opportunities ranked by priority
93 
94# 4. Prepare QBR using templates
95# Reference: assets/qbr_template.md
96```
97 
98**Error handling:** If a script exits with an error, check that:
99- The input JSON matches the required schema for that script (see Input Requirements above)
100- All required fields are present and correctly typed
101- Python 3.7+ is being used (`python --version`)
102- Output files from prior steps are non-empty before piping into subsequent steps
103 
104---
105 
106## Scripts
107 
108### 1. health_score_calculator.py
109 
110**Purpose:** Multi-dimensional customer health scoring with trend analysis and segment-aware benchmarking.
111 
112**Dimensions and Weights:**
113| Dimension | Weight | Metrics |
114|-----------|--------|---------|
115| Usage | 30% | Login frequency, feature adoption, DAU/MAU ratio |
116| Engagement | 25% | Support ticket volume, meeting attendance, NPS/CSAT |
117| Support | 20% | Open tickets, escalation rate, avg resolution time |
118| Relationship | 25% | Executive sponsor engagement, multi-threading depth, renewal sentiment |
119 
120**Classification:**
121- Green (75-100): Healthy -- customer achieving value
122- Yellow (50-74): Needs attention -- monitor closely
123- Red (0-49): At risk -- immediate intervention required
124 
125**Usage:**
126```bash
127python scripts/health_score_calculator.py customer_data.json
128python scripts/health_score_calculator.py customer_data.json --format json
129```
130 
131### 2. churn_risk_analyzer.py
132 
133**Purpose:** Identify at-risk accounts with behavioral signal detection and tier-based intervention recommendations.
134 
135**Risk Signal Weights:**
136| Signal Category | Weight | Indicators |
137|----------------|--------|------------|
138| Usage Decline | 30% | Login trend, feature adoption change, DAU/MAU change |
139| Engagement Drop | 25% | Meeting cancellations, response time, NPS change |
140| Support Issues | 20% | Open escalations, unresolved critical, satisfaction trend |
141| Relationship Signals | 15% | Champion left, sponsor change, competitor mentions |
142| Commercial Factors | 10% | Contract type, pricing complaints, budget cuts |
143 
144**Risk Tiers:**
145- Critical (80-100): Immediate executive escalation
146- High (60-79): Urgent CSM intervention
147- Medium (40-59): Proactive outreach
148- Low (0-39): Standard monitoring
149 
150**Usage:**
151```bash
152python scripts/churn_risk_analyzer.py customer_data.json
153python scripts/churn_risk_analyzer.py customer_data.json --format json
154```
155 
156### 3. expansion_opportunity_scorer.py
157 
158**Purpose:** Identify upsell, cross-sell, and expansion opportunities with revenue estimation and priority ranking.
159 
160**Expansion Types:**
161- **Upsell**: Upgrade to higher tier or more of existing product
162- **Cross-sell**: Add new product modules
163- **Expansion**: Additional seats or departments
164 
165**Usage:**
166```bash
167python scripts/expansion_opportunity_scorer.py customer_data.json
168python scripts/expansion_opportunity_scorer.py customer_data.json --format json
169```
170 
171---
172 
173## Reference Guides
174 
175| Reference | Description |
176|-----------|-------------|
177| `references/health-scoring-framework.md` | Complete health scoring methodology, dimension definitions, weighting rationale, threshold calibration |
178| `references/cs-playbooks.md` | Intervention playbooks for each risk tier, onboarding, renewal, expansion, and escalation procedures |
179| `references/cs-metrics-benchmarks.md` | Industry benchmarks for NRR, GRR, churn rates, health scores, expansion rates by segment and industry |
180 
181---
182 
183## Templates
184 
185| Template | Purpose |
186|----------|---------|
187| `assets/qbr_template.md` | Quarterly Business Review presentation structure |
188| `assets/success_plan_template.md` | Customer success plan with goals, milestones, and metrics |
189| `assets/onboarding_checklist_template.md` | 90-day onboarding checklist with phase gates |
190| `assets/executive_business_review_template.md` | Executive stakeholder review for strategic accounts |
191 
192---
193 
194## Best Practices
195 
1961. **Combine signals**: Use all three scripts together for a complete customer picture
1972. **Act on trends, not snapshots**: A declining Green is more urgent than a stable Yellow
1983. **Calibrate thresholds**: Adjust segment benchmarks based on your product and industry per `references/health-scoring-framework.md`
1994. **Prepare with data**: Run scripts before every QBR and executive meeting; reference `references/cs-playbooks.md` for intervention guidance
200 
201---
202 
203## Limitations
204 
205- **No real-time data**: Scripts analyze point-in-time snapshots from JSON input files
206- **No CRM integration**: Data must be exported manually from your CRM/CS platform
207- **Deterministic only**: No predictive ML -- scoring is algorithmic based on weighted signals
208- **Threshold tuning**: Default thresholds are industry-standard but may need calibration for your business
209- **Revenue estimates**: Expansion revenue estimates are approximations based on usage patterns
210 
211---
212 
213**Last Updated:** February 2026
214**Tools:** 3 Python CLI tools
215**Dependencies:** Python 3.7+ standard library only
216 
View all files on GitHub →

Details

Updated
Aug 30, 2026
License
MIT
Stars on the repo
★ 26,349
Checked
Source
alirezarezvani/claude-skills ↗
Creator
alirezarezvani · 363 listings
View creator

Similar skills

See all →
SkillOptimize their subscription business end-to-endSubscription Lifecycle: Trial, Churn, Win-backappeeky/aso-skills · by appeekyWhen the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.★ 2.2k GitHub starsSkillTell us about your subscription business and why people quitWin back customers before they cancelcoreyhaines31/marketingskills · by coreyhaines31Tell us about your subscription business and why people quit. Get back a ready-to-use plan to keep more customers and recover failed payments.★ 51.1k GitHub starsMCPYou need to assess customer healthCustomer success managerdavila7/claude-code-templates · by davila7Use this agent when you need to assess customer health, develop retention strategies, identify upsell opportunities, or maximize customer lifetime value. Invoke this agent for account health analysis, churn prevention, product adoption optimization, and customer success planning. Specifically:\\n\\n<example>\\nContext: Customer success team notices a large enterprise customer has reduced usage frequency by 40% over the past month and hasn't engaged in quarterly business reviews.\\nuser: "We're concerned about TechCorp's engagement. Usage is down significantly. Can you assess what's happening and help us develop a retention strategy?"\\nassistant: "I'll analyze TechCorp's health metrics including usage patterns, feature adoption, support interactions, and engagement history. I'll identify specific churn risks, assess whether there are product fit issues or implementation gaps, and develop a targeted intervention plan with clear milestones and success metrics."\\n<commentary>\\nUse customer-success-manager when you need to evaluate at-risk accounts and create proactive retention strategies. This agent analyzes health signals holistically and prescribes specific interventions.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Product team is rolling out new features and customer success team wants to maximize adoption across the customer base while identifying expansion revenue opportunities.\\nuser: "We're launching three new features next month. How do we ensure our customers actually adopt them? And which customers might be willing to upgrade to higher tiers?"\\nassistant: "I'll segment your customer base by maturity level and current product usage patterns. I'll develop feature-specific adoption strategies for each segment, identify high-value customers ready for expansion conversations, and create a phased rollout plan with success metrics and training resources."\\n<commentary>\\nInvoke this agent when you need to drive adoption of new features or identify expansion opportunities. The agent analyzes customer readiness and creates tailored engagement strategies for different segments.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Quarterly renewal period is approaching and customer success team wants to prepare for renewal conversations with key accounts and identify which customers are at risk of non-renewal.\\nuser: "We have 40 accounts up for renewal in the next 90 days. Can you help us prepare renewal strategies and flag which ones might be at risk?"\\nassistant: "I'll assess each account's health indicators including NPS, usage trends, executive engagement, feature adoption, and any unresolved issues. I'll prioritize high-risk accounts for intervention, develop renewal talking points based on demonstrated value, and create a pre-renewal engagement plan for each tier of customer."\\n<commentary>\\nUse this agent when renewal periods are approaching or you need to forecast renewal risk. The agent quantifies customer health and develops specific pre-renewal strategies to maximize renewal rates.\\n</commentary>\\n</example>\\n\\nDoes not handle individual support tickets or FAQ/help-center content — hand those to customer-support. Does not own pre-sale technical POC/RFP work — hand that to sales-engineer. Does not finalize pricing or discount decisions — route to the account/deal team. Does not review or negotiate contract/legal terms — route to legal-advisor.★ 32.3k GitHub starsSkill/cs:cco-review <plan/cs:cco-review — CCO Forcing Questionsalirezarezvani/claude-skills · by alirezarezvani/cs:cco-review <plan> — Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring. Use when gross retention is slipping, before approving CSM headcount, or when deciding which customer segments to keep or fire.★ 26.3k GitHub starsSkillReduce voluntary and involuntary churn through cancel flowChurn preventionalirezarezvani/claude-skills · by alirezarezvaniReduce voluntary and involuntary churn through cancel flow design, save offers, exit surveys, and dunning sequences. Use when designing or optimizing a cancel flow, building save offers, setting up dunning emails, or reducing failed-payment churn. Trigger keywords: cancel flow, churn reduction, save offers, dunning, exit survey, payment recovery, win-back, involuntary churn, failed payments, cancel page. NOT for customer health scoring or expansion revenue — use customer-success-manager for that.★ 26.3k GitHub starsSkillGuided journey from an app people sign up forGrow an Appwondelai/skills · by wondelaiGuided journey from an app people sign up for and then quietly abandon to a sealed retention engine with a habit loop, an activated first run, and one metric the whole team trusts. Orchestrates eight skills phase by phase - hooked-ux, improve-retention, continuous-discovery, lean-ux, inspired-product, lean-analytics, microinteractions, drive-motivation - asking the user questions at every decision point and recording results in the project docs/ folder (PRODUCT.md, METRICS.md, GROW-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to lift activation and retention, design a habit loop, fix a leaky onboarding funnel, or says ''users sign up then disappear''. Do not use to fix broken UX or performance that no engagement mechanic can paper over - run improve-app first; if there is no app yet, use create-app. For one framework in isolation, invoke that skill directly.★ 2.2k GitHub stars

More from alirezarezvani

SkillResume a paused experiment/ar:ar-resume — Resume Experimentalirezarezvani/claude-skills · by alirezarezvaniResume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment.★ 26.3k GitHub starsSkillShow experiment dashboard with results, active loops/ar:ar-status — Experiment Dashboardalirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub starsSkillStart an autonomous experiment loop with user-selected/ar:loop — Autonomous Experiment Loopalirezarezvani/claude-skills · by alirezarezvaniStart an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.★ 26.3k GitHub starsSkillRun a single experiment iteration/ar:run — Single Experiment Iterationalirezarezvani/claude-skills · by alirezarezvaniRun a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration.★ 26.3k GitHub starsSkillSet up a new autoresearch experiment interactively/ar:setup — Create New Experimentalirezarezvani/claude-skills · by alirezarezvaniSet up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop.★ 26.3k GitHub starsSkill/cs:boardroom <brief/cs:boardroom — Multi-Role Boardroom Deliberationalirezarezvani/claude-skills · by alirezarezvani/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.★ 26.3k GitHub stars