CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-security-basics

Apply Groq security best practices for API key management and data protection. Use when securing API keys, implementing least privilege access, or auditing Groq security configuration. Trigger with phrases like "groq security", "groq secrets", "secure groq", "groq API key security".

70

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-5

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

A well-structured, actionable skill body with a clear six-step workflow, explicit validation checkpoints, error-recovery feedback loops, and clean progressive disclosure into two real reference files. Minor redundancy between the Instructions, Output, and Examples sections is the only conciseness drag.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explanations of what an API or key is), but the Output and Examples sections partially restate links already present in Instructions, giving minor trimmable redundancy.

4 / 5

Actionability

Provides concrete executable commands inline (echo for .env.local/.gitignore, the gsk_ grep regex) while delegating full code to real reference files; mostly executable with the bulk of copy-ready code one level deep.

4 / 5

Workflow Clarity

Six steps are clearly sequenced in order with explicit validation (verify a 200 from /v1/models before deleting the old key) and an Error Handling section providing feedback loops for recovery, plus a Security Checklist; destructive/batch operations have validation so the cap does not apply.

5 / 5

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references to references/implementation.md and references/examples.md (both verified present), each described by content; content is appropriately split and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 strong, well-targeted description that clearly states capabilities and explicit trigger guidance in third-person imperative voice. Minor specificity and synonym-coverage gaps keep specificity and trigger_term_quality just below the top anchor.

DimensionReasoningScore

Specificity

Names the Groq security domain and several concrete actions ("API key management", "data protection", "securing API keys", "least privilege access", "auditing Groq security configuration"), though "best practices" is slightly generic, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ("Apply Groq security best practices for API key management and data protection") and when ("Use when securing API keys... or auditing..." plus concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Provides natural trigger phrases users would say ("groq security", "groq secrets", "secure groq", "groq API key security") with good coverage, but a few synonyms (e.g. "groq key rotation", "groq hardening") are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Groq security specifically) with distinct, Groq-scoped triggers, giving minimal conflict risk with other skills.

5 / 5

Total

18

/

20

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.