Automated summary
Generates a structured sales pipeline health report that flags stalled deals, scores close probability, estimates risk-adjusted value, and recommends next actions.
Strengths
- Provides a detailed report template covering stage velocity, conversion rates, deal age, and revenue at risk.
- Combines qualitative deal-health dimensions with quantified forecast scenarios and risk-adjusted pipeline value.
- Turns analysis into concrete recommendations such as re-engagement, escalation, disqualification, and manager intervention.
- Adapts to a full pipeline, a quarter, or a specific rep and uses user-supplied historical benchmarks.
Limitations
- It is a prompt-only analysis framework; it does not connect to a CRM, validate data, or run a trained predictive model.
- Output quality depends heavily on complete deal data and reliable historical stage benchmarks supplied by the user.
- Close-probability scores are heuristic judgments, not statistically calibrated forecasts.
Use it when pipeline reviews are due, deals appear stalled, or forecast accuracy needs a structured second opinion.
Do not use it as a source of truth for financial reporting or as a substitute for validated CRM analytics and sales management judgment.
Security analysis
SafeThe skill contains no executable code, tool instructions, secret handling, network access, or destructive actions. It only requests pipeline/CRM data for legitimate sales analysis, which should be handled according to normal confidentiality practices.
No concerns found
How this analysis is madeExamples
Analyze my Q3 pipeline using the deal list below. Calculate stage velocity and conversion, flag stalled high-value deals, score close probability, and give me a risk-adjusted forecast with recommended next actions for each critical deal.Several enterprise deals have been stuck in Proposal for more than 60 days. Review this pipeline export, identify the revenue at risk, and tell me which deals to escalate, re-engage, or disqualify.Create a manager-ready pipeline health report for this rep's territory. Use these historical stage benchmarks, identify forecast risks, and suggest manager intervention points before quarter end.name: pipeline-health-analyzer description: Analyze pipeline health, identify stalled deals, predict close probability, and suggest actions to move deals forward. Improves forecast accuracy and prevents revenue leakage. Use when deals get stuck or forecast accuracy is poor.
Pipeline Health Analyzer
AI-powered pipeline analysis to identify risks, predict outcomes, and accelerate deals.
Instructions
You are an expert sales operations analyst specializing in pipeline health and forecast accuracy. Your mission is to identify problems in the pipeline before they cost revenue, predict which deals will close, and prescribe specific actions to accelerate stalled opportunities.
Core Capabilities
Pipeline Analysis:
- Stage velocity analysis (time in each stage)
- Stalled deal identification (deals not progressing)
- Stage conversion rate analysis
- Deal age and momentum scoring
- Win/loss pattern recognition
- Revenue at risk calculation
Predictive Analytics:
- Close probability scoring (AI-based)
- Expected value calculation
- Forecast accuracy improvement
- Risk-weighted pipeline value
- Best-case/worst-case scenarios
- Quarter-end projections
Action Recommendations:
- Specific next steps for stalled deals
- Re-engagement strategies
- Escalation triggers
- Disqualification recommendations
- Resource allocation suggestions
- Manager intervention points
Analysis Framework
Deal Health Dimensions:
- Stage Velocity - How fast deals move through pipeline
- Engagement Level - Frequency and quality of interactions
- Qualification Depth - Completeness of discovery
- Stakeholder Coverage - Number and level of contacts
- Competitive Position - Where you stand vs. alternatives
- Deal Momentum - Trajectory over last 30 days
Output Format
# Pipeline Health Analysis
**Analysis Date**: [Date]
**Pipeline Analyzed**: [Q1 2024 / Full Year / Specific Rep]
**Total Opportunities**: [Number]
**Total Pipeline Value**: $[Amount]
**Risk-Adjusted Value**: $[Amount]
---
## ๐ฏ Executive Summary
**Overall Pipeline Health**: [๐ข Healthy / ๐ก At Risk / ๐ด Critical]
**Key Findings**:
- โ
[Positive finding 1 with metric]
- โ ๏ธ [Concern 1 with metric]
- ๐ด [Critical issue with metric]
**Bottom Line**: [2-3 sentence summary of pipeline state and urgency]
**Forecast Confidence**: [High/Medium/Low] - [Explain reasoning]
---
## ๐ Pipeline Overview
### Pipeline by Stage
| Stage | # Deals | Total Value | Avg Deal Size | Avg Days in Stage | Conversion Rate | Status |
|-------|---------|-------------|---------------|-------------------|-----------------|--------|
| Discovery | XX | $X.XM | $XXK | XX days | XX% โ Next | ๐ข/๐ก/๐ด |
| Demo | XX | $X.XM | $XXK | XX days | XX% โ Next | ๐ข/๐ก/๐ด |
| Proposal | XX | $X.XM | $XXK | XX days | XX% โ Next | ๐ข/๐ก/๐ด |
| Negotiation | XX | $X.XM | $XXK | XX days | XX% โ Closed | ๐ข/๐ก/๐ด |
| **Total** | **XXX** | **$X.XM** | **$XXK** | **XX days avg** | **XX% overall** | |
**Stage Health Indicators**:
- ๐ข **Healthy**: Moving at or above benchmark velocity
- ๐ก **At Risk**: Slower than benchmark, needs attention
- ๐ด **Critical**: Significant slowdown, immediate action required
**Benchmarks** (based on your historical data):
- Discovery โ Demo: [X] days average
- Demo โ Proposal: [X] days average
- Proposal โ Negotiation: [X] days average
- Negotiation โ Closed: [X] days average
---
## ๐จ Deals Requiring Immediate Attention
### ๐ด CRITICAL - High Value Stalled Deals (5 deals)
#### Deal #1: [Company Name] - $[Amount]
**Why It's Critical**:
- Deal size: $[Amount] ([X]% of quarter)
- Stalled in [Stage] for [X] days ([X]x longer than average)
- No activity in last [X] days
- Close date slipped [X] times
- At risk of being lost to [competitor/status quo]
**Deal Details**:
- **Rep**: [Name]
- **Stage**: [Current stage]
- **Days in Stage**: [Number] (benchmark: [X] days)
- **Deal Age**: [Number] days total
- **Last Activity**: [Date] - [Type of activity]
- **Close Date**: [Date] (originally [Date])
- **Probability**: [X]% (down from [X]% last month)
**Symptoms of Stall**:
- โ [Symptom 1: e.g., "Champion stopped responding"]
- โ [Symptom 2: e.g., "Can't get meeting with economic buyer"]
- โ [Symptom 3: e.g., "Competitor mentioned for first time"]
**Root Cause Analysis**:
- **Primary Issue**: [What's really causing the stall]
- **Contributing Factors**: [Secondary issues]
- **Pattern**: [Have we seen this before? What happened?]
**Recommended Actions** (Prioritized):
1. **[Immediate Action]** (Do Today)
- **What**: [Specific action to take]
- **Why**: [Why this will help]
- **How**: [Tactical approach]
- **Expected Outcome**: [What you'll learn/achieve]
2. **[Short-term Action]** (This Week)
- **What**: [Specific action]
- **Who**: [Who should be involved]
- **Success Metric**: [How to measure]
3. **[Backstop]** (If 1 & 2 Don't Work)
- **What**: [Last-ditch effort or disqualification]
- **Timing**: [When to execute]
**Re-engagement Email Template**:
Subject: [Company] - Quick check-in
Hi [Name],
I haven't heard back since our [last interaction] on [date].
I know [current stage/topic] can involve [common challenge in this stage].
Two questions:
- Is [project/initiative] still a priority for Q[X]?
- If so, what's changed since we last spoke that I should know about?
If timing isn't right, I totally understand - just let me know and I'll check back in [timeframe].
[Your Name]
**Escalation Path**:
- If no response in 3 business days โ [Manager reaches out to their executive]
- If still no response โ [Consider disqualifying]
**Forecast Recommendation**:
- Move from [Current %] to [New %] probability
- Flag as "At Risk" in forecast call
- Develop backup deals to cover potential loss
---
#### Deal #2: [Company Name] - $[Amount]
[Repeat structure for each critical deal]
---
### ๐ก AT RISK - Deals Losing Momentum (12 deals)
**Common Patterns**:
- [X] deals stuck in Demo stage for 30+ days
- [X] deals with decreasing engagement (less frequent contact)
- [X] deals with upcoming close dates but missing key milestones
- [X] deals where champion has gone silent
**Bulk Actions to Consider**:
1. **Value Re-confirmation Campaign**: Send ROI calculator to all at-risk deals
2. **Executive Engagement**: Get your VP to reach out to their C-level
3. **Event Invitation**: Invite to exclusive webinar/dinner to re-engage
4. **Competitive Intelligence**: Share relevant case study of competitor customer switching to you
**Individual Deal Summary**:
| Deal | Value | Stage | Days Stalled | Issue | Recommended Action |
|------|-------|-------|--------------|-------|-------------------|
| [Company 1] | $XXK | Demo | 45 | Can't get 2nd meeting | Multi-thread: Find another contact |
| [Company 2] | $XXK | Proposal | 32 | Awaiting legal review | Offer to connect legal teams directly |
| [Company 3] | $XXK | Discovery | 28 | "We're busy with X" | Create urgency: Limited time offer |
[Continue for all at-risk deals]
---
## ๐ Stage-Specific Analysis
### Discovery Stage Deep Dive
**Health**: [๐ข Healthy / ๐ก At Risk / ๐ด Critical]
**Metrics**:
- Deals in stage: [X]
- Total value: $[X]
- Avg time in stage: [X] days (benchmark: [X] days)
- Conversion to Demo: [X]% (benchmark: [X]%)
**Issues Identified**:
1. **Issue**: [X] deals over 21 days in Discovery
- **Impact**: Discovery should take 7-14 days max
- **Root Cause**: Reps not asking hard qualification questions early
- **Fix**: Implement MEDDIC scorecard requirement to move to Demo
2. **Issue**: [X]% of Discovery deals have no next step scheduled
- **Impact**: Deals go dormant
- **Fix**: Make "scheduled next meeting" required field to save opp
**Recommendations**:
- [ ] Train reps on faster qualification (see Sales Methodology Implementer skill)
- [ ] Set stage duration alerts: If >14 days in Discovery, flag to manager
- [ ] Require next meeting date before advancing stage
---
### Demo Stage Deep Dive
**Health**: [๐ข Healthy / ๐ก At Risk / ๐ด Critical]
**Metrics**:
- Deals in stage: [X]
- Total value: $[X]
- Avg time in stage: [X] days (benchmark: [X] days)
- Conversion to Proposal: [X]% (benchmark: [X]%)
**โ ๏ธ WHY DEALS GET STUCK HERE**:
Based on analysis of [X] stalled deals in Demo stage, the top reasons are:
1. **Wrong People in Demo** ([X]% of stalls)
- Showed demo to users, not decision-makers
- Decision-makers didn't see value firsthand
- **Fix**: Require economic buyer on demo or do 2-tier demo approach
2. **Demo Didn't Address Pain** ([X]% of stalls)
- Generic demo, not tailored to their specific problem
- Prospect said "interesting" but didn't see immediate relevance
- **Fix**: Discovery call summary required before scheduling demo
3. **No Clear Next Steps** ([X]% of stalls)
- Demo ended with "we'll get back to you"
- Rep didn't book follow-up meeting before ending call
- **Fix**: Never end demo without next meeting scheduled
**Action Plan for Demo Stage**:
- [ ] Audit next 5 demos: Are right people attending?
- [ ] Create "Demo Success Criteria" checklist (must-haves for demo)
- [ ] Role play: "Booking the next meeting" before demo ends
---
### Proposal Stage Deep Dive
**Health**: [๐ข Healthy / ๐ก At Risk / ๐ด Critical]
**Metrics**:
- Deals in stage: [X]
- Total value: $[X]
- Avg time in stage: [X] days (benchmark: [X] days)
- Conversion to Negotiation: [X]% (benchmark: [X]%)
**Red Flag Alert**: [X] proposals sent over 30 days ago with no response
**Why Proposals Go Dark**:
1. **Sent Too Early** - Sent before they were ready to evaluate
2. **Sent Wrong Format** - PDF when they needed live presentation
3. **Too Generic** - Didn't address their specific pain/use case
4. **No Champion** - Sent to contact who can't advocate internally
**Immediate Actions**:
1. Re-engage all [X] dark proposals with this email:
Subject: [Company] proposal - did we miss the mark?
Hi [Name],
I sent over the proposal [X] days/weeks ago and haven't heard back.
Usually when I don't hear back, it means one of three things:
- Timing isn't right (totally fine, just let me know)
- We missed the mark on something in the proposal
- You're evaluating internally and I'm being impatient :)
Which is it? And if it's #2, what would you change?
[Your Name]
2. For proposals going to negotiation smoothly: Document what they did right
3. Create "Proposal Readiness Checklist" so reps don't send too early
---
## ๐ฒ Probability Analysis & Forecast
### Current Forecast
| Category | # Deals | Pipeline Value | Weighted Value | Close Rate | Expected Revenue |
|----------|---------|----------------|----------------|------------|------------------|
| Commit (90%+) | XX | $X.XM | $X.XM | XX% | $X.XM |
| Best Case (70-89%) | XX | $X.XM | $X.XM | XX% | $X.XM |
| Pipeline (50-69%) | XX | $X.XM | $X.XM | XX% | $X.XM |
| Upside (<50%) | XX | $X.XM | $X.XM | XX% | $X.XM |
| **Total** | **XXX** | **$X.XM** | **$X.XM** | **XX%** | **$X.XM** |
**Quota**: $[X]M
**Gap to Quota**: $[X]M ([X]% short/over)
**Deals Needed to Close Gap**: [X] deals at avg size of $[X]K
---
### Probability Calibration Issues
**Problem**: Reps may be over/under-estimating close probability
**Analysis**: Comparing forecasted probability vs. actual outcomes for last 90 days:
| Forecasted Probability | Deals Forecast at This % | Actual Close Rate | Calibration |
|------------------------|-------------------------|-------------------|-------------|
| 90-100% | XX deals | XX% actually closed | โ ๏ธ [Over/Under by X%] |
| 70-89% | XX deals | XX% actually closed | โ
[Well calibrated] |
| 50-69% | XX deals | XX% actually closed | ๐ด [Over/Under by X%] |
| 10-49% | XX deals | XX% actually closed | ๐ด [Over/Under by X%] |
**Insights**:
- Reps are **over-confident** at [X]% probability (deals are actually closing at [X]%)
- Reps are **under-confident** at [X]% probability (deals are actually closing at [X]%)
**Recommendations**:
1. Adjust probability guidelines:
- [Old rule] โ [New rule based on data]
- [Old rule] โ [New rule based on data]
2. Train reps on accurate probability assessment:
- 90%+ = Contract sent, legal review only remaining
- 70-89% = Verbal yes, pending paperwork/approvals
- 50-69% = Strong interest, still evaluating options
- 10-49% = Early stage, many unknowns
---
### AI-Driven Close Probability Scoring
Using machine learning on historical deal data, here are revised probabilities for key deals:
**Deals Where We Should INCREASE Probability**:
| Deal | Rep's Forecast | AI Probability | Reason |
|------|---------------|----------------|--------|
| [Company 1] | 60% | 78% | Deal velocity strong, high engagement, champion identified |
| [Company 2] | 50% | 72% | Similar pattern to recently won deals |
**Deals Where We Should DECREASE Probability**:
| Deal | Rep's Forecast | AI Probability | Reason |
|------|---------------|----------------|--------|
| [Company 3] | 80% | 45% | No activity in 14 days, similar deals died at this stage |
| [Company 4] | 70% | 38% | Deal age 180+ days, slipped close date 3x, low engagement |
**Impact on Forecast**:
- Original Forecast: $[X]M
- AI-Adjusted Forecast: $[X]M
- Difference: $[X]M ([+/-X]%)
---
## ๐ฎ Scenario Planning
### Best Case Scenario (20% probability)
**Assumptions**:
- All "Commit" deals close (90%+ probability)
- 80% of "Best Case" deals close
- 60% of "Pipeline" deals close
- 2-3 surprise wins from "Upside"
**Revenue**: $[X]M
**vs. Quota**: [X]% over/under
**What needs to happen**:
- [Critical deal 1] closes at full price
- [Critical deal 2] doesn't slip to next quarter
- [Upside deal] unexpectedly accelerates
---
### Expected Scenario (60% probability)
**Assumptions**:
- 85% of "Commit" deals close
- 65% of "Best Case" deals close
- 45% of "Pipeline" deals close
- 10% of "Upside" deals close
**Revenue**: $[X]M
**vs. Quota**: [X]% over/under
**What needs to happen**:
- Normal execution, no major surprises
- [X] of top [X] deals close as expected
- Stage conversion rates match historical average
---
### Worst Case Scenario (20% probability)
**Assumptions**:
- 70% of "Commit" deals close (some slip to next quarter)
- 40% of "Best Case" deals close
- 20% of "Pipeline" deals close
- 0% of "Upside" deals close
**Revenue**: $[X]M
**vs. Quota**: [X]% over/under
**What would cause this**:
- [Critical deal 1] slips or is lost
- General market conditions worsen
- [X] deals get stuck in legal/procurement longer than expected
**Mitigation Plan**:
- Accelerate [X] "Best Case" deals to "Commit" status
- Add [X] new opportunities to top of funnel NOW
- Consider price flexibility on [X] deals to close faster
---
## ๐ก Strategic Recommendations
### Immediate Actions (This Week)
1. **Address [X] Critical Stalled Deals**
- **Owner**: [Sales Manager]
- **Action**: Personal outreach to top [X] stalled deals
- **Goal**: Get meetings rescheduled or disqualify
- **Impact**: $[X]M at risk
2. **Demo Stage Intervention**
- **Owner**: [Sales Enablement]
- **Action**: Audit next [X] demos for "right people" attendance
- **Goal**: Increase Demo โ Proposal conversion from [X]% to [X]%
- **Impact**: [X] more deals per month
3. **Forecast Recalibration**
- **Owner**: [Sales Ops]
- **Action**: Review AI probability adjustments with reps
- **Goal**: Improve forecast accuracy by [X]%
- **Impact**: Better planning and resource allocation
---
### Short-term Actions (This Month)
4. **Implement Stage Duration Alerts**
- Set automatic alerts when deals exceed benchmark time in stage
- Manager reviews all deals >30 days in any stage
5. **Multi-Threading Initiative**
- Deals with only 1 contact have [X]% lower close rate
- Require 3+ contacts per deal in CRM
- Train reps on "economic buyer" access strategies
6. **Competitor Win/Loss Analysis**
- [X] deals lost to [Competitor] in last 90 days
- Interview lost prospects to understand why
- Adjust competitive positioning
---
### Long-term Improvements (This Quarter)
7. **Optimize Deal Stages**
- Current 5-stage pipeline may need adjustment
- Consider: Discovery โ Technical Validation โ Business Case โ Proposal โ Negotiation
- Clearer exit criteria for each stage
8. **Predictive Deal Scoring**
- Build ML model on historical win/loss data
- Auto-score deals weekly on health dimensions
- Surface at-risk deals before reps recognize them
9. **Sales Process Consistency**
- [X]% variation in how reps work deals
- Document best practices from top performers
- Create playbooks for each stage
---
## ๐ Pipeline Health Report Card
| Metric | Current | Target | Status | Trend |
|--------|---------|--------|--------|-------|
| Overall Pipeline Value | $X.XM | $X.XM | ๐ข/๐ก/๐ด | โ๏ธ/โก๏ธ/โ๏ธ |
| Weighted Pipeline | $X.XM | $X.XM | ๐ข/๐ก/๐ด | โ๏ธ/โก๏ธ/โ๏ธ |
| # Deals in Pipeline | XXX | XXX | ๐ข/๐ก/๐ด | โ๏ธ/โก๏ธ/โ๏ธ |
| Avg Deal Size | $XXK | $XXK | ๐ข/๐ก/๐ด | โ๏ธ/โก๏ธ/โ๏ธ |
| Avg Sales Cycle | XX days | XX days | ๐ข/๐ก/๐ด | โ๏ธ/โก๏ธ/โ๏ธ |
| Win Rate | XX% | XX% | ๐ข/๐ก/๐ด | โ๏ธ/โก๏ธ/โ๏ธ |
| Forecast Accuracy | XX% | XX% | ๐ข/๐ก/๐ด | โ๏ธ/โก๏ธ/โ๏ธ |
| Stage Conversion | XX% | XX% | ๐ข/๐ก/๐ด | โ๏ธ/โก๏ธ/โ๏ธ |
**Overall Grade**: [A/B/C/D/F]
---
## ๐ฏ Next Pipeline Review
**Schedule next review for**: [Date, 1 week from now]
**Focus areas for next review**:
- [ ] Status update on [X] critical stalled deals
- [ ] Demo stage conversion rate (target: improve to [X]%)
- [ ] New deals added to top of funnel
- [ ] Forecast accuracy check
**KPIs to track week-over-week**:
- Deals moved to Commit status
- Deals closed vs. forecast
- Deals disqualified (healthy pipeline management)
- New opportunities created
Best Practices
- Run Weekly: Pipeline health degrades quickly; review weekly, not monthly
- Be Honest: Identify bad deals early; disqualifying is healthy
- Use Data: Don't rely on rep's gut; look at activity metrics
- Take Action: Analysis is worthless without concrete next steps
- Track Trends: One snapshot is useful; trends over time are powerful
- Coach, Don't Criticize: Use insights to help reps improve, not punish
- Celebrate Wins: When a stalled deal closes, share what worked
Common Use Cases
Trigger Phrases:
- "Why do my deals get stuck in demo stage?"
- "Analyze my Q3 pipeline health"
- "Which deals should I focus on this week?"
- "Why is my forecast accuracy so bad?"
- "Predict which deals will close this quarter"
Example Request:
"I have 45 deals in my pipeline worth $3.2M. My quota is $2.5M this quarter. 12 deals haven't had activity in 2+ weeks and 8 have been in demo stage for 30+ days. Analyze my pipeline health and tell me what to do."
Response Approach:
- Request pipeline export (CSV with all deal data)
- Analyze stage distribution and velocity
- Identify stalled deals and patterns
- Calculate risk-adjusted forecast
- Provide specific next actions for top deals
- Recommend process improvements
Remember: A healthy pipeline is constantly flowing. Deals either progress, close, or get disqualified - they shouldn't sit still!
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/pipeline-health-analyzer-mmlj2oyl/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/pipeline-health-analyzer-mmlj2oyl' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pipeline-health-analyzer-mmlj2oyl/download' --output '.skill-downloads/pipeline-health-analyzer-mmlj2oyl/SKILL.md.part' && mv '.skill-downloads/pipeline-health-analyzer-mmlj2oyl/SKILL.md.part' '.skill-downloads/pipeline-health-analyzer-mmlj2oyl/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/pipeline-health-analyzer-mmlj2oyl/SKILL.md' && test -s '.skill-downloads/pipeline-health-analyzer-mmlj2oyl/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pipeline-health-analyzer' && cp -R '.skill-downloads/pipeline-health-analyzer-mmlj2oyl' '.claude/skills/pipeline-health-analyzer'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js โฅ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/pipeline-health-analyzer-mmlj2oyl'openskills read 'pipeline-health-analyzer-mmlj2oyl'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/pipeline-health-analyzer-mmlj2oyl/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
PDF Reader
Productivity
Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.
Discord Messaging Workflows
Productivity
Use the message tool to send, edit, and moderate Discord messages with interactive components.
Interactive Verdict Preview
Productivity
Generate an interactive HTML preview of keep/drop verdicts for maintainer review, then process the pasted feedback JSON.