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".

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/granola-pack/skills/granola-upgrade-migration/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable body with concrete commands and useful tables, but two structural issues hold it back: destructive update workflows lack validation checkpoints, and the provided reference bundle file is orphaned (never referenced from the body).

Suggestions

Add validation checkpoints to Step 3's destructive escalation: after clearing caches or resetting preferences, verify Granola launches and the issue is resolved before proceeding to the 'nuclear' full reinstall.

Link references/migration-procedures.md from the body (e.g. a 'See migration-procedures.md for detailed rollback, export, and enterprise-migration procedures' note) so the bundle file is discoverable and well-signaled.

Move the large feature-difference lists and the Plan Migration Matrix into the reference file, keeping the SKILL.md body as a lean overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable snippets and tables rather than padded concept explanations, though prose like 'Granola checks for updates automatically and downloads in the background' and inline feature lists could be trimmed slightly.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands ('brew update && brew upgrade --cask granola', 'rm -rf ~/Library/Caches/Granola', 'defaults read ...') plus specific UI paths and an error table, but some flows are macOS-only without platform notes, a minor gap below fully executable.	4 / 5
Workflow Clarity	The six-step sequence is clearly ordered, but Step 3 runs destructive operations (cache deletion, 'defaults delete', full reinstall) with no validation/verification checkpoints between them, which caps workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Sections are organized and the body has structure, but the bundle file references/migration-procedures.md is never linked or signaled from the body (Resources only lists external URLs), and substantial detail (feature lists, the Plan Migration Matrix) is inlined that belongs in the reference.	3 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit 'Use when' clause, dedicated trigger phrases, and concrete domain-specific actions. Minor specificity gaps (e.g. 'resolving update issues') and a few missing trigger synonyms keep two dimensions at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Upgrade Granola app versions and migrate between subscription plans', 'downgrading with data preservation', 'resolving update issues'), but 'resolving update issues' is generic and plan-migration actions are not fully enumerated, leaving minor gaps below a comprehensive 5.	4 / 5
Completeness	It explicitly answers both what ('Upgrade Granola app versions and migrate between subscription plans') and when ('Use when upgrading the desktop app, changing from free to paid plans, downgrading with data preservation, or resolving update issues') with concrete enumerated trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	The dedicated Trigger line supplies natural phrases users would say ('upgrade granola', 'granola update', 'change granola plan', 'granola new version', 'granola downgrade') with good synonym coverage, though a few natural variants (e.g. 'granola subscription', 'granola reinstall') are missing.	4 / 5
Distinctiveness Conflict Risk	The Granola-specific brand triggers and narrow subscription/version niche make it clearly distinguishable from other skills with minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/granola-pack/skills/granola-upgrade-migration/SKILL.md
Commit: 8585d6d

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.