granola-data-handling

Manage Granola data export, retention policies, GDPR/CCPA compliance, and archival workflows. Handle Subject Access Requests and Right to Erasure. Trigger: "granola export", "granola data", "granola GDPR", "granola retention", "granola delete data", "granola compliance".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 executable code and specific compliance tables, but it is over-inline for a skill that ships a reference file it never points to, and its destructive/batch workflows lack validation checkpoints.

Suggestions

Add explicit verify-then-proceed checkpoints to destructive and batch workflows — e.g., confirm the export count matches expected notes before purging, and validate archive integrity before deleting from Granola.

Link references/implementation.md from the body (e.g., under a 'Detailed implementation' section) and move duplicated templates/procedures (retention YAML, SAR/deletion steps) into it instead of restating them inline.

Trim inferable commentary such as the 'significant privacy advantage' sentence and the rationale column where the retention period already speaks for itself.

Dimension	Reasoning	Score
Conciseness	Largely actionable tables and code, but includes commentary Claude could infer (e.g., 'This is a significant privacy advantage — there is no audio file to leak, export, or subpoena') and could be tightened throughout.	2 / 3
Actionability	Provides fully executable, copy-paste-ready artifacts: a Python cache-export script, a curl/Enterprise-API call, a YAML Zapier workflow, and concrete retention tables and GDPR/CCPA mappings.	3 / 3
Workflow Clarity	Steps are sequenced across six phases, but destructive/batch operations (Right to Erasure, bulk export, monthly archival) lack explicit validation checkpoints or verify-then-proceed feedback loops, capping clarity at 2.	2 / 3
Progressive Disclosure	Sections are well-organized, but a bundled references/implementation.md exists and is never linked from the body, while content that could live in that file (retention templates, SAR/deletion procedures) is duplicated inline.	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.

The description is specific, third-person, and answers both 'what' and 'when' with explicit, natural trigger phrases. It is concise yet comprehensive, with low conflict risk thanks to its Granola-scoped triggers.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'export, retention policies, GDPR/CCPA compliance, and archival workflows' plus 'Handle Subject Access Requests and Right to Erasure' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what it does and when to use it via the literal 'Trigger:' clause with concrete invocation terms.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say ('granola export', 'granola data', 'granola GDPR', 'granola retention', 'granola delete data', 'granola compliance') with good variation coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Granola data handling) with 'granola'-prefixed triggers, making it unlikely to fire for unrelated 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: 5 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.