granola-debug-bundle
Create diagnostic bundles for Granola support requests. Use when preparing support tickets, collecting system/audio/network info, or diagnosing complex issues that require Granola support team assistance. Trigger: "granola debug", "granola diagnostics", "granola support bundle", "granola logs", "granola system info".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 communicates its purpose, scope, and activation conditions. It uses third person voice, lists concrete actions, provides explicit 'Use when' guidance, and includes natural trigger terms. The Granola-specific context makes it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: creating diagnostic bundles, preparing support tickets, collecting system/audio/network info, and diagnosing complex issues. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (create diagnostic bundles, collect system/audio/network info) and 'when' (preparing support tickets, diagnosing complex issues requiring Granola support team assistance), with explicit trigger terms listed. | 3 / 3 |
Trigger Term Quality | Excellent trigger term coverage with natural phrases users would say: 'granola debug', 'granola diagnostics', 'granola support bundle', 'granola logs', 'granola system info'. These are realistic user queries with good variation. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the 'Granola' product name as a strong differentiator. The combination of diagnostic bundles, support requests, and Granola-specific triggers makes it 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 strong, highly actionable skill with executable commands specific to Granola's actual infrastructure and file paths. The workflow is well-sequenced with clear steps and good error handling. The main weakness is that the content is somewhat long for a single file — the Windows variant and self-diagnosis checklist could be split out — and a few sections include mildly unnecessary explanations.
Suggestions
Consider moving the Windows PowerShell commands to a separate referenced file (e.g., WINDOWS.md) to reduce the main skill's length and improve progressive disclosure.
Remove the Prerequisites section — Claude knows it needs terminal access and an internet connection for network diagnostics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elements. The 'Current State' section with live commands at the top is a nice touch, but the Prerequisites section explains obvious things (e.g., 'Terminal access', 'Internet access for network diagnostics'). Some inline comments are redundant (e.g., '# Audio configuration (critical for transcription issues)'). The Privacy section and Self-Diagnosis Checklist add value but could be slightly tighter. | 2 / 3 |
Actionability | Every step contains fully executable, copy-paste ready bash/PowerShell commands with proper error handling (set -euo pipefail). The commands are specific to Granola's actual paths, endpoints (api.granola.ai, api.workos.com), and cache file locations. The error handling table provides concrete fixes for specific failure modes. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced from directory creation through packaging and submission. Each step builds on the previous one. The self-diagnosis checklist serves as a pre-flight validation checkpoint, and the error handling table provides recovery paths. The privacy constraints act as guardrails throughout the process. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical flow, but it's quite long for a single SKILL.md file. The Windows PowerShell variant, the self-diagnosis checklist, and the error handling table could potentially be split into referenced files. However, the Resources section does link out to external docs appropriately, and the Next Steps section provides navigation. | 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.