granola-common-errors

Troubleshoot common Granola errors — audio capture failures, transcription issues, calendar sync problems, and integration errors. Platform-specific fixes for macOS and Windows. Trigger: "granola error", "granola not working", "granola not recording", "fix granola", "granola troubleshoot".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

72%

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

The body is highly actionable with concrete platform-specific commands and a clear symptom-matched structure, but it inlines material that overlaps the bundled reference without linking to it and omits verification steps for several destructive fixes. Tightening inline redundancy and adding validate-after-fix checkpoints would lift the weaker dimensions.

Suggestions

Add explicit verification steps after destructive commands (e.g. 'Re-run pgrep -l Granola and confirm audio capture resumes' after sudo killall coreaudiod) so workflows include feedback loops.

Link references/detailed-errors.md from SKILL.md (e.g. in the Resources or a 'Detailed error reference' section) and pull the duplicated integration/processing tables out of the main body to reduce redundancy.

Trim the inline Error Quick Reference table or move it into the bundled reference, keeping SKILL.md as a lean overview that points to detailed-errors.md for exhaustive cases.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of conceptual padding, but content that belongs in the bundled reference (e.g. the full Error Quick Reference table and several platform-specific fix lists) is inlined in SKILL.md and could be tightened given a references/ bundle exists.	2 / 3
Actionability	Provides concrete, executable bash commands (pgrep, defaults read, sudo killall coreaudiod, pkill -9 Granola, brew reinstall --cask granola) and specific UI navigation steps, copy-paste ready across macOS and Windows.	3 / 3
Workflow Clarity	Symptom-to-fix sections are well organized, but this is a troubleshooting skill with several destructive/batch operations (sudo killall coreaudiod, rm -rf ~/Library/Caches/Granola, defaults delete) that lack explicit validation/verification checkpoints confirming the fix worked before moving on.	2 / 3
Progressive Disclosure	A references/detailed-errors.md bundle exists and is well structured, but it is never linked or signaled from SKILL.md; the body largely duplicates the same error categories inline, so navigation to the deeper material is unclear.	2 / 3
	Total	9 / 12 Passed

Description

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.

A strong, concise description that names concrete capabilities, supplies explicit natural-language triggers, and occupies a distinct product-specific niche. It satisfies the 'what' and 'when' requirements clearly.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('audio capture failures, transcription issues, calendar sync problems, and integration errors') plus platform-specific fixes for macOS and Windows, matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers both what it does (troubleshoot specific Granola error classes) and when to use it via an explicit 'Trigger:' clause with natural trigger terms.	3 / 3
Trigger Term Quality	Explicit Trigger clause covers natural phrases a user would say ('granola error', 'granola not working', 'granola not recording', 'fix granola', 'granola troubleshoot'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to a single named product (Granola) with product-specific triggers, making it unlikely to fire for unrelated troubleshooting skills.	3 / 3
	Total	12 / 12 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
Commit: 1628598

Reviewed: 2 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.