granola-migration-deep-dive
Migrate to Granola from Otter.ai, Fireflies, Fathom, tl;dv, or manual note-taking. Covers data export from source tools, parallel-run strategy, team transition, and historical data preservation. Trigger: "migrate to granola", "switch to granola", "granola from otter", "granola from fireflies", "replace meeting tool with granola".
89
88%
Does it follow best practices?
Impact
Pending
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 strong skill description that clearly defines a narrow, specific use case—migrating to Granola from competing meeting note tools. It names concrete actions (data export, parallel-run strategy, team transition, historical data preservation), lists specific competing tools by name, and provides explicit trigger phrases that users would naturally use. The description is concise and well-structured.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: data export from source tools, parallel-run strategy, team transition, and historical data preservation. These are clear, actionable migration steps rather than vague language. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate to Granola covering data export, parallel-run strategy, team transition, historical data preservation) and 'when' (explicit trigger phrases provided). The trigger section serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Includes highly natural trigger phrases users would actually say: 'migrate to granola', 'switch to granola', 'granola from otter', 'granola from fireflies', 'replace meeting tool with granola'. Also names specific competing tools (Otter.ai, Fireflies, Fathom, tl;dv) which users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely specific niche: migration to one particular tool (Granola) from named competitors. Very unlikely to conflict with other skills given the highly specific product names and migration context. | 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 well-structured migration guide with strong actionability and clear workflow sequencing. Its main weakness is length — the document tries to be both an overview and a comprehensive reference, resulting in a monolithic file that could benefit from splitting source-specific details and reference tables into separate files. The content is practical and specific but could be more concise by trimming explanatory text and the comparison table.
Suggestions
Move source-specific export details (Step 2) into a separate MIGRATION-SOURCES.md reference file, keeping only a summary table in the main skill
Remove or significantly trim the 'Key Differences from Bot-Based Tools' comparison table — this is general product knowledge that doesn't directly support the migration workflow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity — the overview paragraph restates what the description already covers, the comparison table at the end rehashes known differences, and some sections (like the team announcement email template) are padded. The archival Python script and parallel-run tables add value but the overall document could be tightened by ~30%. | 2 / 3 |
Actionability | The skill provides concrete, executable guidance throughout: source-specific export paths with exact menu locations, a working Python archival script, comparison tables with specific metrics to fill in, a cutover checklist with actionable items, and a ready-to-send team announcement template. The guidance is specific enough to follow step-by-step. | 3 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with logical progression from assessment through post-migration optimization. It includes explicit validation checkpoints (parallel run quality comparison, cutover day checklist with monitoring period, post-migration verification items) and a feedback loop in the parallel run phase where issues discovered in Week 1 inform Week 2 decisions. | 3 / 3 |
Progressive Disclosure | The skill references other skills appropriately (granola-install-auth, granola-core-workflow-a, granola-performance-tuning) and includes external resource links. However, the document is quite long (~200+ lines of content) and the source-specific export details, comparison table, and error handling table could be split into separate reference files. The inline content is heavy for a SKILL.md overview. | 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.