gamma-data-handling

Handle data privacy, retention, and compliance for Gamma integrations. Use when implementing GDPR compliance, data retention policies, or managing user data within Gamma workflows. Trigger with phrases like "gamma data", "gamma privacy", "gamma GDPR", "gamma data retention", "gamma compliance".

Quality

70%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/gamma-pack/skills/gamma-data-handling/SKILL.md

Quality

Discovery

89%

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 solid description that clearly defines its niche (Gamma-specific data privacy and compliance), includes explicit 'Use when' and trigger phrase guidance, and is well-differentiated from other skills. The main weakness is that the capability descriptions are somewhat high-level—'handle' and 'managing' are vague verbs that don't convey specific concrete actions like 'encrypt PII fields' or 'generate data retention audit reports'.

Suggestions

Replace vague verbs like 'handle' and 'managing' with more specific concrete actions (e.g., 'configure data retention schedules', 'generate GDPR compliance reports', 'anonymize user PII in Gamma workflows').

Dimension	Reasoning	Score
Specificity	Names the domain (data privacy/compliance for Gamma integrations) and some actions (implementing GDPR compliance, data retention policies, managing user data), but the actions are somewhat high-level and not deeply concrete—e.g., it doesn't specify what 'handle' or 'manage' entails in practice.	2 / 3
Completeness	Clearly answers both 'what' (handle data privacy, retention, and compliance for Gamma integrations) and 'when' (explicit 'Use when' clause with specific triggers and a 'Trigger with phrases' section).	3 / 3
Trigger Term Quality	Includes explicit trigger phrases like 'gamma data', 'gamma privacy', 'gamma GDPR', 'gamma data retention', 'gamma compliance', plus natural keywords like 'GDPR compliance', 'data retention policies', and 'user data'. Good coverage of terms a user would naturally use.	3 / 3
Distinctiveness Conflict Risk	The combination of 'Gamma' platform specificity with data privacy/GDPR/compliance creates a clear niche. The explicit 'gamma' prefix on trigger terms makes it unlikely to conflict with generic data privacy skills or other platform-specific skills.	3 / 3
	Total	11 / 12 Passed

Implementation

50%

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

This skill provides a solid structural framework for Gamma data handling with useful tables, a compliance checklist, and mostly concrete TypeScript examples. However, it falls short on actionability due to several undefined helper functions that break the copy-paste readiness of the retention and GDPR sections. The workflow lacks explicit validation checkpoints between steps, which is important for data privacy operations involving PII and destructive erasure.

Suggestions

Implement or stub the undefined helper functions (deleteOldExports, anonymizeLogs, deletePrompts, listS3Objects, deleteS3Prefix) with at least minimal executable implementations so the retention and GDPR code is truly actionable.

Add explicit validation steps: verify sanitization output before API call, confirm export download integrity (e.g., check file size/hash), and verify erasure completion before returning success.

Consider extracting the longer code blocks into referenced files (e.g., 'See [sanitize.ts](examples/sanitize.ts)') to improve progressive disclosure and keep the SKILL.md as a concise overview.

Remove the Prerequisites section — Claude already understands GDPR/CCPA concepts and doesn't need to be told to have 'data classification policies defined'.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-structured but includes some unnecessary elements like the Prerequisites section (Claude knows what GDPR is), verbose comments in code, and the data flow ASCII diagram could be more compact. The data classification table is useful but some rows are obvious.	2 / 3
Actionability	Code examples are mostly concrete and executable, but several key functions are referenced without implementation (deleteOldExports, anonymizeLogs, deletePrompts, listS3Objects, deleteS3Prefix, db references). The sanitization and export archiving code is copy-paste ready, but the retention and GDPR code relies on undefined helpers, making it incomplete pseudocode in practice.	2 / 3
Workflow Clarity	Steps are clearly sequenced (sanitize → log → export → retain → GDPR), and the compliance checklist serves as a validation checkpoint. However, there are no explicit validation/verification steps between stages — e.g., no check that sanitization actually removed PII before sending, no verification that exports downloaded successfully before proceeding. For data handling involving PII and destructive operations (erasure), feedback loops are missing.	2 / 3
Progressive Disclosure	The skill has good section organization and references external resources at the end, plus a 'Next Steps' pointer. However, the inline code is quite lengthy (~150+ lines) and could benefit from being split into referenced files. The data flow map, classification table, and compliance checklist are well-placed, but the overall document is monolithic for its complexity.	2 / 3
	Total	8 / 12 Passed

Validation

81%

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3e83543

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.