granola-prod-checklist
Production readiness checklist for Granola team and enterprise deployment. Use when rolling out Granola to a team, planning enterprise deployment, or verifying all configuration is production-ready. Trigger: "granola production", "granola rollout", "granola deployment", "granola checklist", "granola go-live".
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 solid description with excellent trigger terms and clear 'when' guidance, making it easy for Claude to select appropriately. Its main weakness is the lack of specificity about what concrete actions the checklist covers—listing 2-3 specific checklist items would help Claude understand the skill's scope better. The product-specific trigger terms ensure low conflict risk.
Suggestions
Add 2-3 specific concrete actions the checklist covers, e.g., 'Covers SSO/SAML configuration, data retention policies, API key rotation, and network security verification' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Granola team/enterprise deployment) and a general action (production readiness checklist), but does not list multiple specific concrete actions like 'verify SSO configuration, check API rate limits, validate data retention policies'. It stays at the level of 'checklist' without detailing what the checklist covers. | 2 / 3 |
Completeness | The description clearly answers both 'what' (production readiness checklist for Granola team and enterprise deployment) and 'when' (rolling out Granola to a team, planning enterprise deployment, verifying production-ready configuration), with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | The description includes explicit trigger terms that users would naturally say: 'granola production', 'granola rollout', 'granola deployment', 'granola checklist', 'granola go-live'. These are natural phrases covering common variations of how a user might request this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Granola production/enterprise deployment, which is a clear niche. The 'granola' prefix on all trigger terms makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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 production checklist with strong actionability and clear workflow sequencing across 7 phases. The checklist format with specific configuration paths, verification steps, and metrics targets makes it highly executable. Minor weaknesses include some verbosity that could be trimmed and the monolithic structure that could benefit from splitting detailed sections into referenced files.
Suggestions
Trim the Overview section and Prerequisites — these restate obvious context that Claude can infer from the title and phase structure.
Consider extracting the integration configuration table and error handling table into separate referenced files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-structured but includes some unnecessary verbosity. The 'Overview' section restates what the title already conveys, and some items (like explaining what SOC 2 is or what DPA means) could be trimmed. The checklist format is efficient, but the overall length (~120 lines) could be tightened given that much of this is standard deployment knowledge. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific pricing, exact configuration paths (Settings > Calendar > Connect), verification steps for each integration, specific metrics with targets, and troubleshooting tables with cause/fix pairs. The checklist format makes every item directly executable. | 3 / 3 |
Workflow Clarity | The 7-phase workflow is clearly sequenced with logical dependencies (plan → security → integrations → workspace → pilot → go-live → post-launch). The pilot phase includes explicit success metrics and feedback loops, Phase 6 includes monitoring checkpoints, and the error handling table provides recovery guidance for common failures. | 3 / 3 |
Progressive Disclosure | The skill references external resources (docs links, other skills like 'granola-install-auth', 'granola-hello-world', 'granola-upgrade-migration') which is good, but all content is inline in a single long file. The integration table, pilot metrics, and error handling could potentially be split into referenced files. However, with no bundle files provided, the inline approach is acceptable though not optimal. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
a04d1a2
- 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.