business-health-diagnostic
by deanpetersbusiness-health-diagnostic helps Finance, founders, and operators assess SaaS health across growth, retention, unit economics, and capital efficiency for board-ready decisions. Use it to spot red flags, prioritize fixes, and turn raw metrics into an actionable diagnostic.
This skill scores 78/100, which means it is a solid listing candidate for directory users: it appears triggerable and materially useful for SaaS business reviews, but users should expect a few adoption gaps because the repository shows no companion scripts or reference files to further reduce guesswork.
- Clear, specific trigger for SaaS health diagnostics across growth, retention, unit economics, and capital efficiency.
- Substantial SKILL.md content with explicit intent, best-for cases, scenarios, and estimated time, which improves agent understanding.
- Workflow-oriented and non-placeholder content with multiple constraints and repo/file references, suggesting real operational guidance rather than a demo stub.
- No install command, scripts, or reference assets, so execution may rely entirely on the text prompt in SKILL.md.
- The repository evidence shows strong documentation but limited supporting tooling, which may reduce consistency for agents on complex diagnostics.
Overview of business-health-diagnostic skill
The business-health-diagnostic skill helps you assess SaaS business health across growth, retention, unit economics, and capital efficiency in one pass. It is best for Finance, operators, and founders who need a board-ready view, not a vanity-metric snapshot. If you are trying to decide whether the business is healthy, where the biggest risk sits, or what to fix first, this skill is a strong fit.
What this skill is for
Use the business-health-diagnostic skill when you need to turn raw business metrics into an actionable health readout: what is improving, what is weakening, and which issues deserve attention now. It is especially useful before board meetings, quarterly reviews, and fundraising prep.
Where it adds real value
The main value of business-health-diagnostic for Finance is that it connects metrics that are often reviewed separately. Instead of looking at growth, churn, burn, and cash runway in isolation, it frames them as a linked system so you can spot tradeoffs and hidden fragility earlier.
When it is the right fit
This skill fits best when you already have some operating data and need judgment, prioritization, and a structured diagnostic. It is less useful if you only want a quick KPI summary or if your business model is too early, too bespoke, or too data-poor to support meaningful benchmarking.
How to Use business-health-diagnostic skill
Install the skill in your workflow
For a standard business-health-diagnostic install, add the skill from the repository and then work from the skill file in context. The skill lives at skills/business-health-diagnostic/SKILL.md, and the repo currently does not rely on helper scripts or supporting folders, so the core guidance is concentrated in that file.
Start with the minimum input it needs
The business-health-diagnostic usage pattern works best when you provide a compact but complete operating picture: revenue or ARR trend, customer retention or churn, gross margin, CAC or payback if available, burn, runway, and the business stage. If you omit those inputs, the diagnostic becomes more generic and less decision-useful.
Turn a rough ask into a better prompt
A weak request sounds like: “Review our SaaS metrics.” A stronger request sounds like: “Run a business-health-diagnostic on our SaaS with ARR of $4.2M, 8% MoM growth, 92% gross retention, 118% net revenue retention, $140k monthly burn, and 11 months runway. Focus on what is most likely to break first and what I should say in the board deck.” Specific stage, numbers, and decision context dramatically improve output quality.
Read the file in this order
For the fastest ramp, read SKILL.md first, then inspect the sections that define the diagnostic logic and any benchmark guidance embedded in the file. Because there are no separate reference folders here, the install decision depends mostly on how clearly you can map your own metrics into the skill’s framework.
business-health-diagnostic skill FAQ
Is this only for Finance teams?
No. The business-health-diagnostic skill is useful for Finance, founders, and product or operations leaders who need a financially grounded view of business health. Finance teams will usually get the most repeatable value because they already own the underlying metrics.
How is this different from a generic prompt?
A generic prompt often produces a loose narrative. This skill is designed to force a more disciplined business-health-diagnostic guide: it ties metrics together, pushes toward prioritization, and is better suited to board, investor, and management-review contexts where judgment quality matters more than prose.
Is it beginner-friendly?
Yes, if you can provide basic SaaS metrics and explain your goal. You do not need advanced finance modeling to use it well. What matters most is that you supply consistent numbers, the right time window, and the decision you are trying to make.
When should I not use it?
Do not use it when you need deep cohort analysis, detailed forecasting, or a narrow one-metric investigation. If your goal is only CAC payback, churn diagnostics, or runway math, a more specialized workflow may be faster and more precise.
How to Improve business-health-diagnostic skill
Give the skill the right slice of data
The biggest quality gain comes from cleaner inputs. Include stage, date range, core revenue metric, retention, burn, runway, and any known anomalies such as a recent price change, one-time churn event, or hiring spike. Those details help the business-health-diagnostic skill separate structural issues from temporary noise.
Ask for prioritization, not just commentary
If you want better output, explicitly ask for the top risks, the most likely cause, and the next action by urgency. The skill is most valuable when it ranks problems instead of merely describing them. That is the difference between a report and a decision tool.
Iterate with follow-up questions
After the first pass, tighten the brief around the weakest area. For example: “Now isolate whether the weakness is acquisition efficiency or retention,” or “Re-run the business-health-diagnostic with board language and a 3-bullet action plan.” Iteration helps convert a broad health read into a sharper operating agenda.
Watch for the common failure mode
The most common failure mode is overconfidence from incomplete data. If your metrics are partial, inconsistent, or from different time windows, the output can look precise without being reliable. Improve the input first; then re-run the diagnostic for a cleaner, more defensible result.