granola-upgrade-migration
Upgrade Granola app versions and migrate between subscription plans. Use when upgrading the desktop app, changing from free to paid plans, downgrading with data preservation, or resolving update issues. Trigger: "upgrade granola", "granola update", "change granola plan", "granola new version", "granola downgrade".
71
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 identifies the specific product (Granola), lists concrete actions (upgrading, migrating plans, downgrading, resolving update issues), and provides explicit trigger guidance with natural user phrases. The description is concise, uses third person voice, and covers both the 'what' and 'when' dimensions thoroughly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: upgrading app versions, migrating between subscription plans, changing from free to paid plans, downgrading with data preservation, and resolving update issues. | 3 / 3 |
Completeness | Clearly answers both 'what' (upgrade app versions, migrate subscription plans) and 'when' (explicit 'Use when...' clause with specific scenarios plus a dedicated 'Trigger:' section with example phrases). | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger terms that users would actually say: 'upgrade granola', 'granola update', 'change granola plan', 'granola new version', 'granola downgrade'. These cover common variations of how users would phrase their requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Granola' and the narrow focus on version upgrades and plan migrations for that specific app. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 solid, actionable skill with clear workflows and executable commands for both app updates and plan migrations. Its main weakness is that it packs a lot of reference-style content (feature lists, migration matrices, seat management) inline rather than splitting it into supporting files, making it longer than ideal. The actionability and workflow clarity are strong, with good error handling and escalation paths.
Suggestions
Move the detailed plan feature comparisons and migration matrix into a separate reference file (e.g., PLANS.md) and link to it from the main skill to improve conciseness and progressive disclosure.
Trim the 'What changes on upgrade' feature lists to just the most impactful differences, since Claude can reference full plan details from a linked file or the pricing URL.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary detail that Claude would not need spelled out, such as the full feature comparison lists between plans and the detailed plan migration matrix. The step-by-step troubleshooting commands are efficient, but the overall document is longer than necessary for the actionable content it delivers. | 2 / 3 |
Actionability | The skill provides concrete, executable bash commands for version checking, cache clearing, reinstallation, and Homebrew updates. UI navigation paths are specific (e.g., 'Settings (avatar bottom-left) > Account > Subscription > Upgrade'), and the error handling table maps specific errors to specific fixes. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced from checking the current version through updating, troubleshooting, upgrading plans, downgrading with data preservation, and managing seats. The pre-downgrade checklist serves as a validation checkpoint, and the troubleshooting section provides an escalating fix sequence (clear caches → reset preferences → full reinstall) that acts as a feedback loop. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear headers and tables, but it's a monolithic document with no bundle files to offload detailed content like the full feature comparison lists, the plan migration matrix, or the team seat management instructions. The plan details and migration matrix could be split into separate reference files to keep the main skill leaner. | 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
8a9cd04
- 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.