CtrlK
BlogDocsLog inGet started
Tessl Logo

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

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/granola-pack/skills/granola-debug-bundle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

The content is highly actionable with complete, copy-paste-ready diagnostic scripts for both macOS and Windows. It is held back by missing validation checkpoints in the workflow and by failing to link to the existing collection-scripts.md reference, which leaves the inline body doing work a reference could carry.

Suggestions

Insert explicit validation between steps (e.g. verify each .txt was created before zipping) and reposition the Self-Diagnosis Checklist as a 'validate before packaging' gate to reach workflow_clarity level 3.

Link to references/collection-scripts.md from the body (e.g. 'See collection-scripts.md for platform-specific collection variants') and move the duplicated script material there to enable progressive disclosure.

Trim the 'Current State' dynamic shell blocks and the redundant Output/Privacy restatements; the scripts and the privacy section already convey what is and isn't collected.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable scripts and minimal conceptual filler, but a few sections (Current State dynamic shell blocks, the Self-Diagnosis Checklist, and the Privacy/Output sections) restate or pad content that Claude could infer or that the scripts already demonstrate, keeping it just short of lean.

2 / 3

Actionability

Every step ships copy-paste-ready, executable bash/PowerShell with concrete commands, real file paths, and specific endpoints (api.granola.ai, api.workos.com), fully matching the level 3 'executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Steps are clearly numbered 1-6, but the workflow lacks explicit validation checkpoints between steps; the Self-Diagnosis Checklist comes after packaging rather than as a validate-then-proceed gate, and nothing verifies collected files exist before zipping, so it sits at the level 2 'sequence present but checkpoints missing' anchor rather than 3.

2 / 3

Progressive Disclosure

A references/collection-scripts.md file exists, but the body never signals or links to it — all detail is inline — and the inline scripts duplicate much of that reference file; the bundle structure is real but not navigated, matching the level 2 'content that should be separate is inline / references present but not clearly signaled' anchor.

2 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

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

The description is well-structured with explicit 'what' and 'when' guidance plus natural, distinctive Granola-specific triggers. Its only weakness is specificity — it states the purpose but does not enumerate the concrete collection actions (system, audio, network, packaging) that the body delivers.

Suggestions

Add one or two concrete actions to the description, e.g. 'Collects system info, audio config, and network connectivity into a redacted zip bundle' to reach the multiple-specific-actions level.

Tighten the multi-line description into a single concise paragraph; the current line-wrapped form adds tokens without aiding clarity.

DimensionReasoningScore

Specificity

It names the domain ('diagnostic bundles for Granola support requests') and a concrete outcome, but lists no concrete actions (collects system/audio/network info is implied via the body, not stated); closer to 'Names domain and some actions' than the multiple-concrete-actions level 3 anchor.

2 / 3

Completeness

It explicitly answers 'what' (create diagnostic bundles for support requests) and 'when' ('Use when preparing support tickets, collecting system/audio/network info') with an explicit Trigger clause, satisfying both halves of the level 3 anchor.

3 / 3

Trigger Term Quality

Natural trigger phrases like 'granola debug', 'granola diagnostics', 'granola support bundle', 'granola logs', and 'granola system info' are exactly what a user would say, giving good coverage of natural variations.

3 / 3

Distinctiveness Conflict Risk

The Granola-specific trigger terms carve out a clear niche unlikely to fire for unrelated skills, matching the level 3 'clear niche with distinct triggers' anchor.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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