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".
74
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/gamma-pack/skills/gamma-data-handling/SKILL.mdQuality
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 skill description that clearly defines its scope (data privacy and compliance for Gamma integrations) and provides explicit trigger guidance. Its main weakness is that the capability descriptions are somewhat high-level—listing more concrete actions would strengthen it. The Gamma-specific trigger terms effectively minimize conflict risk with other skills.
Suggestions
Add more specific concrete actions such as 'configure data retention schedules, generate GDPR compliance reports, manage consent records, handle data deletion requests' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (data privacy/compliance for Gamma integrations) and mentions some actions like 'implementing GDPR compliance' and 'managing user data,' but the actions are fairly high-level and not concrete enough to qualify as multiple specific actions (e.g., no mention of specific operations like encrypting data, generating compliance reports, configuring retention schedules). | 2 / 3 |
Completeness | The description clearly answers both 'what' (handle data privacy, retention, and compliance for Gamma integrations) and 'when' (explicit 'Use when' clause with specific scenarios plus a 'Trigger with phrases' section). Both components are explicitly stated. | 3 / 3 |
Trigger Term Quality | The description includes explicit trigger phrases like 'gamma data', 'gamma privacy', 'gamma GDPR', 'gamma data retention', 'gamma compliance' which are natural terms a user would say. It also includes broader terms like 'GDPR compliance', 'data retention policies', and 'user data' which provide good keyword coverage. | 3 / 3 |
Distinctiveness Conflict Risk | The description is scoped specifically to Gamma integrations combined with data privacy/compliance, which creates a clear niche. The trigger terms are all prefixed with 'gamma' making it unlikely to conflict with generic data privacy skills or other integration 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 framework for Gamma data handling and compliance, with useful data flow diagrams, classification tables, and a compliance checklist. However, several code implementations are incomplete stubs, validation/verification steps are missing for destructive operations like GDPR erasure, and the content is somewhat verbose with explanations Claude doesn't need. The skill would benefit from completing the implementation gaps and adding explicit validation checkpoints.
Suggestions
Complete the stub functions (deleteOldExports, anonymizeLogs, deletePrompts, etc.) with executable implementations or explicitly mark them as user-provided dependencies
Add validation/verification steps after destructive operations — e.g., verify deletion completed for GDPR erasure, confirm export download integrity before deleting temporary URLs
Trim explanatory text that Claude already knows (e.g., what Gamma does, what GDPR is) and remove redundant code comments like '// Never log raw content or API keys' above code that already demonstrates this
Split the lengthy inline code examples into referenced bundle files (e.g., sanitize.ts, retention.ts) and keep SKILL.md as a concise overview with pointers
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary explanation (e.g., 'Gamma processes user-submitted content through AI to generate presentations' is context Claude doesn't need). The data flow diagram and classification table are useful but the overall content is somewhat verbose for what could be more tightly expressed. Some code comments are redundant. | 2 / 3 |
Actionability | The code examples are mostly concrete and executable, but several key functions are left unimplemented (deleteOldExports, anonymizeLogs, deletePrompts, listS3Objects, deleteS3Prefix, db references) making the workflow incomplete. The sanitization and logging examples are copy-paste ready, but the retention and GDPR sections are more like pseudocode scaffolding. | 2 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, and the compliance checklist provides a good summary. However, there are no explicit validation checkpoints or feedback loops — for data handling operations involving PII deletion and GDPR compliance (destructive/batch operations), the absence of verify-after-delete steps and error recovery patterns caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a logical flow from data mapping to implementation to compliance checklist. However, with no bundle files, the inline content is quite long (~200 lines of code) that could benefit from being split into referenced files. The references to external resources and next steps are good but the main body is monolithic. | 2 / 3 |
Total | 8 / 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
3a2d27d
- 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.