analyze-account-health
Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.
85
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly defines its domain (B2B account health), lists specific analytical capabilities, and provides explicit 'Use for' triggers with natural terms a customer success professional would use. It uses proper third-person voice and is concise without being vague. The description effectively differentiates itself through domain-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Also names specific outputs like account health summaries. | 3 / 3 |
Completeness | Clearly answers both what ('Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities') and when ('Use for customer success reviews, renewal preparation, QBRs, or account prioritization') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'account health', 'customer success reviews', 'renewal preparation', 'QBRs', 'account prioritization', 'usage patterns', 'risk signals', 'expansion opportunities'. These are terms a B2B customer success professional would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche in B2B customer success / account health analysis. The combination of B2B-specific terminology (QBRs, renewal preparation, account prioritization) makes it highly distinctive and unlikely to conflict with general analytics or reporting skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill that provides specific API calls, concrete thresholds, and a detailed output template for B2B account health analysis. Its main weaknesses are the lack of validation/error-handling steps in the workflow (e.g., handling missing data or low-volume accounts) and the monolithic structure that could benefit from splitting the report template and common patterns into separate files. Some best practices like 'show trends, not snapshots' are things Claude can infer.
Suggestions
Add explicit validation checkpoints: what to do when queries return no data, when account history is too short, or when feedback sources are empty — this is critical for a multi-step analytical workflow.
Extract the detailed report template and 'Common Patterns' section into separate referenced files (e.g., REPORT_TEMPLATE.md, PATTERNS.md) to reduce the main skill's token footprint.
Trim 'Best Practices' to only non-obvious guidance — items like 'be specific in recommendations' and 'show trends, not snapshots' are things Claude already understands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient for its complexity, but the extensive output template is verbose and could be condensed. The 'Common Patterns' and 'Best Practices' sections contain guidance Claude could largely infer. The report template takes up significant token space that could be more compact. | 2 / 3 |
Actionability | Each step specifies exact Amplitude API calls (e.g., `Amplitude:query_dataset`, `Amplitude:get_feedback_sources`, `Amplitude:get_feedback_insights`), concrete metrics to compute (DAU/MAU ratio, WoW changes), specific thresholds for classification (DAU/MAU >40% = Healthy), and a detailed output template. This is highly actionable and specific. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (0-5) with logical progression from discovery to reporting. However, there are no explicit validation checkpoints or error recovery steps — e.g., what to do if queries return no data, if the account has insufficient history, or if feedback sources are empty. For a multi-step analytical workflow, these gaps matter. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a monolithic document with no references to supporting files. The detailed report template and common patterns sections could be split into separate reference files. For a skill of this length (~150+ lines), some content decomposition would improve navigability. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- amplitude/builder-skills
- Commit
221ffaa
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.