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".
85
83%
Does it follow best practices?
Impact
Pending
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 highly distinguishable. Its main weakness is the lack of specific concrete actions—it says 'checklist' but doesn't enumerate what the checklist covers (e.g., SSO setup, data migration, monitoring configuration). Adding 2-3 specific checklist items would strengthen the specificity dimension.
Suggestions
Add specific concrete actions the checklist covers, e.g., 'Covers SSO/SAML configuration, data retention policies, API key rotation, monitoring setup, and user provisioning.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Granola production readiness) and a general action (checklist for team/enterprise deployment), but does not list specific concrete actions like 'verify SSO configuration, check API rate limits, validate backup settings'. The description stays at a high level. | 2 / 3 |
Completeness | 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 | 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 the use case. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Granola' combined with production/deployment context. Very unlikely to conflict with other skills given the narrow, product-specific niche. | 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 seven deployment phases. The main weaknesses are moderate verbosity (some sections like Overview and Output are redundant) and the monolithic structure that could benefit from splitting detailed tables into referenced files. Overall it serves its purpose well as a deployment guide with concrete steps, metrics, and troubleshooting.
Suggestions
Remove the Overview and Output sections — the checklist phases themselves communicate the scope and expected outcomes clearly enough.
Consider extracting the integration configuration table and pilot metrics into a referenced file to reduce the main skill's length and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably well-structured but includes some unnecessary padding like the Overview section restating what the skill does, the Prerequisites section listing things Claude would infer, and the Output section which is redundant. The pilot metrics table and error handling table add value but could be tighter. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable checklists with specific plan prices, configuration paths (Settings > Calendar > Connect), verification steps for each integration, specific metrics with targets, and troubleshooting steps with specific fixes. This is copy-paste ready for deployment planning. | 3 / 3 |
Workflow Clarity | The seven-phase workflow is clearly sequenced with logical dependencies (plan before security, security before integrations, pilot before go-live). Each phase has explicit verification checkpoints — the integration table includes a Verification column, the pilot has defined success metrics, and go-live has monitoring steps. The pilot phase includes a feedback loop for fixing issues. | 3 / 3 |
Progressive Disclosure | The skill references external resources and other skills (granola-install-auth, granola-hello-world, granola-upgrade-migration) which is good, but the main content is quite long and monolithic. The integration table and pilot metrics could potentially be split into referenced files, and the error handling section could be a separate troubleshooting reference. | 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
c8a915c
- 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.