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".
67
82%
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 strong skill description that clearly identifies the specific product (Granola), enumerates concrete problem categories (audio capture, transcription, calendar sync, integrations), specifies platform scope (macOS/Windows), and provides explicit trigger terms. It follows third-person voice and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: troubleshooting audio capture failures, transcription issues, calendar sync problems, and integration errors, with platform-specific fixes for macOS and Windows. | 3 / 3 |
Completeness | Clearly answers both 'what' (troubleshoot common Granola errors including audio capture, transcription, calendar sync, integration) and 'when' (explicit trigger terms listed). The 'Trigger:' clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Includes highly natural trigger terms that users would actually say: 'granola error', 'granola not working', 'granola not recording', 'fix granola', 'granola troubleshoot'. These cover common variations of how users express troubleshooting needs. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific product (Granola) with specific error categories. The named product and specific problem domains make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%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 troubleshooting skill with excellent actionability — specific commands, exact UI paths, and concrete fixes for each symptom. Its main weaknesses are the lack of explicit verification steps after applying fixes (e.g., 'test by joining a test meeting and confirming transcript appears') and the monolithic structure that could benefit from splitting into sub-files. Some content like generic audio quality tips adds marginal value for Claude.
Suggestions
Add explicit verification steps after each fix (e.g., 'Verify: Join a test meeting for 1 minute and confirm transcript appears in the note') — this is critical for troubleshooting workflows.
Trim generic advice Claude already knows (e.g., 'use noise-cancelling headset', 'smaller room, soft furnishings') and focus on Granola-specific diagnostics.
Consider splitting integration-specific troubleshooting (Slack, Notion, HubSpot, Zapier) into a separate reference file to reduce the main skill's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and structured sections, but includes some unnecessary framing (e.g., the Overview paragraph explaining how Granola captures audio, the 'Output' section restating obvious outcomes). Some sections like 'Poor Transcription Quality' include generic audio advice Claude already knows. | 2 / 3 |
Actionability | Highly actionable with specific executable bash commands, exact UI navigation paths (System Settings > Privacy & Security > Screen & System Audio Recording), concrete Slack commands (/invite @Granola), and precise file paths for cache clearing. Nearly every fix is copy-paste ready or step-by-step navigable. | 3 / 3 |
Workflow Clarity | The initial diagnostic steps (Step 1-2) provide a reasonable triage workflow, and individual fixes have clear sequences. However, there are no explicit validation/verification steps after applying fixes — the skill never says 'verify the fix worked by doing X' after each remediation, which is important for troubleshooting workflows. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a useful quick reference table, but it's a long monolithic file (~150+ lines of detailed content) that could benefit from splitting integration errors or platform-specific fixes into separate files. The reference to 'granola-debug-bundle' at the end is good but there are no other bundle files to support progressive disclosure. | 2 / 3 |
Total | 9 / 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
a04d1a2
- 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.