CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-data-handling

Implement prompt sanitization, PII redaction, response filtering, and usage tracking for Groq API integrations. Trigger with phrases like "groq data", "groq PII", "groq GDPR", "groq data retention", "groq privacy", "groq compliance".

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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 and token-efficient, but it lacks validation checkpoints in its multi-step workflow and keeps all material inline without progressive file-based disclosure.

Suggestions

Add explicit validation/verification steps (e.g., assert redaction succeeded, verify audit log written, run a sample moderation check) before proceeding in Steps 1–6 to lift workflow clarity.

Move the model pricing table and per-model reference details into a separate reference file linked from the body to improve progressive disclosure and keep the overview lean.

Resolve the `groq-enterprise-rbac` reference — either provide the bundled file or remove the dead Next Steps pointer.

DimensionReasoningScore

Conciseness

The body is lean prose plus executable code with no padding explaining what PII, GDPR, or libraries are; every section earns its tokens and assumes Claude's competence.

3 / 3

Actionability

It provides complete, executable TypeScript functions with real model identifiers and pricing, copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

Steps 1–6 are sequenced, but there are no explicit validation checkpoints or verify-then-proceed feedback loops for risky operations like PII redaction, which caps clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

All content is inline in a single ~270-line file with no bundle files; the only cross-reference is to a non-existent `groq-enterprise-rbac` skill, so structure is present but references are not well-signaled or split out.

2 / 3

Total

10

/

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, complete, and distinctive, pairing a clear capability list with explicit, natural trigger phrases. It satisfies each dimension at the top anchor.

DimensionReasoningScore

Specificity

The description lists four concrete actions — "prompt sanitization, PII redaction, response filtering, and usage tracking" — matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

It explicitly answers both what it does (the four data-handling actions) and when to use it via an explicit "Trigger with phrases like..." clause.

3 / 3

Trigger Term Quality

It enumerates natural trigger phrases ("groq data", "groq PII", "groq GDPR", "groq data retention", "groq privacy", "groq compliance") a user would plausibly say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The Groq-specific data-handling niche with "groq data/PII/GDPR" triggers is clearly distinct and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.