Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured prompt template for churn analysis with clear thematic categories and a useful ARR-weighted ranking approach. Its main weaknesses are the lack of concrete tool invocations (no MCP tool calls, API examples, or executable code), missing validation checkpoints in the workflow, and some unnecessary introductory context. It reads more like a prompt recipe than an actionable skill with verifiable steps.
Suggestions
Add concrete MCP tool invocation examples (e.g., specific HubSpot MCP calls to fetch lost deals, Google Drive MCP calls to write the output file) instead of relying on natural language instructions.
Add validation checkpoints: verify CRM data was retrieved (e.g., 'If 0 records returned, check filter criteria and report to user'), verify clustering produced at least N themes before proceeding to ranking, and confirm file was written successfully.
Remove the introductory paragraph explaining what lost deal notes are — Claude already understands this context. Start directly with the prompt template or a brief one-line purpose statement.
Consider providing a concrete example output snippet showing what the final ChurnAnalysis markdown file should look like, so Claude has a clear target format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what lost deal notes are and why they matter — context Claude doesn't need. The prompt template itself is reasonably efficient, but the introductory framing and some tips are padding. Could be tightened by ~30%. | 2 / 3 |
Actionability | The prompt template provides a structured multi-step workflow with specific fields to collect and output formats, which is good. However, there are no concrete code snippets, API calls, or MCP tool invocations — it's a natural language prompt template rather than executable guidance. Claude would need to figure out how to actually query HubSpot/Attio/Salesforce and write to Google Drive. | 2 / 3 |
Workflow Clarity | The five steps are clearly sequenced and logically ordered. However, there are no validation checkpoints — no step to verify CRM data was actually retrieved, no check that the clustering is reasonable, no validation before writing the final report. For a batch data-processing workflow writing output files, this lack of verification caps the score. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with sections (Prompt Template, Setup, Placeholders, Tips) and references competitor-monitoring as a related skill. However, there are no bundle files and no external references for advanced topics like CRM-specific query patterns or output format templates. The prompt template itself is quite long and could benefit from being split or having detailed sections referenced externally. | 2 / 3 |
Total | 8 / 12 Passed |