CtrlK
BlogDocsLog inGet started
Tessl Logo

data-handling-template

Data handling plan generator — evidence retention, encryption, chain-of-custody, compliance frameworks (GDPR / HIPAA / PCI-DSS / SOC2).

73

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A tight, well-structured instruction skill: concrete values, clear sequencing, an explicit validation checklist, and no wasted tokens or concept explanations. It is appropriately self-contained with no bundle files needed.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what GDPR/HIPAA or a chain-of-custody is, and every section (defaults, classes, storage, frameworks, purge cap) earns its place without padding.

3 / 3

Actionability

Although instruction-only, it gives concrete, copy-ready specifics — e.g. `health-records` with 'classification: secret, retention: 7 days, framework: HIPAA', the default path `/workspace/<engagement>/evidence/`, and named framework entries — so the guidance is fully actionable.

3 / 3

Workflow Clarity

The five steps are clearly sequenced and the Validation Checklist provides explicit pre-write checkpoints for a plan that governs destructive purge/retention behavior, satisfying the feedback-loop requirement rather than capping at 2.

3 / 3

Progressive Disclosure

It is a self-contained, well-organized skill with clearly labeled sections (When to Use, Workflow, Validation Checklist, Anti-patterns, Output) and no nested or broken references, so the simple-skill allowance applies.

3 / 3

Total

12

/

12

Passed

Description

82%

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

A specific, well-scoped description with strong trigger terms and low conflict risk, but it omits any explicit 'Use when' trigger guidance, which caps completeness. Adding a brief usage-trigger clause would round it out.

Suggestions

Append an explicit trigger clause such as 'Use when creating a data handling plan, defining retention/evidence policy, or handling PII under GDPR/HIPAA/PCI-DSS' to lift completeness to 3.

The frontmatter already has richer when_to_use terms; consider surfacing one or two of the most natural phrasings (e.g. 'retention policy', 'PII handling') directly in the description.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — "evidence retention, encryption, chain-of-custody, compliance frameworks (GDPR / HIPAA / PCI-DSS / SOC2)" — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly answers 'what does this do' but includes no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

It surfaces natural domain terms a user would actually say — "data handling", "retention", "encryption", "compliance", "GDPR", "HIPAA", "PCI-DSS" — giving good coverage rather than opaque jargon.

3 / 3

Distinctiveness Conflict Risk

The niche (data handling plans for regulated engagements) is distinct and the framework-specific triggers (GDPR/HIPAA/PCI-DSS/SOC2) make it unlikely to fire for an unrelated skill.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.