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".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly specifies concrete capabilities (sanitization, PII redaction, filtering, tracking) within a well-defined domain (Groq API integrations). It includes explicit trigger phrases that are natural and distinctive, and clearly communicates both what the skill does and when it should be activated.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: prompt sanitization, PII redaction, response filtering, and usage tracking, all scoped to Groq API integrations. | 3 / 3 |
Completeness | Clearly answers both 'what' (prompt sanitization, PII redaction, response filtering, usage tracking for Groq API) and 'when' (explicit trigger phrases provided). The 'Trigger with phrases like...' clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Provides a good set of natural trigger terms users would say: 'groq data', 'groq PII', 'groq GDPR', 'groq data retention', 'groq privacy', 'groq compliance'. These are realistic phrases a user concerned about data handling with Groq would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of Groq API + data privacy/compliance concerns. The trigger terms are all prefixed with 'groq' making conflicts with generic privacy or other API skills unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable TypeScript code for Groq data handling with good coverage of PII redaction, usage tracking, auditing, and content moderation. However, it's quite lengthy for a SKILL.md file—the six full code implementations would be better served by progressive disclosure into separate reference files. The workflow lacks explicit validation checkpoints for what is fundamentally a data safety pipeline.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Verify redaction by logging sanitized output before API call' and 'Test PII rules against sample data before deploying'.
Move the full code implementations to a referenced file (e.g., IMPLEMENTATION.md) and keep SKILL.md as a concise overview showing key patterns and the overall pipeline flow.
Add a quick-start section at the top showing the minimal usage pattern (just auditedCompletion call) before diving into the building blocks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly efficient with executable code blocks, but is quite long (~200+ lines). Some sections like the cost report and daily tracking could be trimmed or referenced externally. The Groq data policy section is useful context but the overall volume is high for what could be more tightly organized. | 2 / 3 |
Actionability | Fully executable TypeScript code throughout with concrete regex patterns, specific model names, actual pricing data, and copy-paste ready functions. Each step provides complete, runnable implementations including types and interfaces. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (sanitize → wrap → track → audit → moderate → report), but there are no explicit validation checkpoints or feedback loops. For a skill involving PII handling and data safety, there should be verification steps (e.g., validate redaction worked before sending, test the pipeline end-to-end). | 2 / 3 |
Progressive Disclosure | The content is mostly monolithic with all code inline in a single file. The error handling table and resources section are well-structured, but the extensive code blocks (6 steps of full implementations) would benefit from being split into referenced files, with SKILL.md serving as an overview with key patterns. | 2 / 3 |
Total | 9 / 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
c8a915c
- 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.