CtrlK
BlogDocsLog inGet started
Tessl Logo

audit-data-hygiene

Use when auditing supplied account, contact, reply, or pipeline records for missing, stale, conflicting, duplicate, or unsupported values.

80

Quality

100%

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%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 tight, well-structured instruction skill that maximizes actionability per token, includes validation checkpoints for a batch audit operation, and stays self-contained. No bundle files are needed.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding; assumes Claude's competence and never explains what records, audits, or normalization are. Every line earns its place.

5 / 5

Actionability

A numbered workflow with an explicit issue-classification enum, severity rubric tied to impact, a copy-pasteable output template, and concrete guardrails — fully actionable even though it is instruction-only.

5 / 5

Workflow Clarity

A clearly sequenced seven-step process with an explicit Quality check validation section and a reconciliation step, satisfying the batch/destructive feedback-loop requirement for this read-only audit.

5 / 5

Progressive Disclosure

Under 50 lines with no bundle files and well-organized sections (Purpose, Required inputs, Workflow, Output format, Guardrails, Quality check, Example invocation); the simple-skill exception applies.

5 / 5

Total

20

/

20

Passed

Description

100%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.

An exemplary description: concrete domain, explicit trigger, comprehensive defect vocabulary, and clear distinctiveness. No ambiguity about when to invoke or what it does.

DimensionReasoningScore

Specificity

The description lists concrete audit targets (account, contact, reply, pipeline records) and a comprehensive defect taxonomy (missing, stale, conflicting, duplicate, unsupported) rather than vague language.

5 / 5

Completeness

Explicitly answers both what (audit records for named defect classes) and when (the 'Use when auditing...' trigger clause with concrete record types).

5 / 5

Trigger Term Quality

Natural user vocabulary ('auditing records', 'missing', 'duplicate', 'conflicting', 'unsupported') with strong synonym and variation coverage.

5 / 5

Distinctiveness Conflict Risk

The record-type list and audit defect taxonomy carve a clear niche unlikely to trigger for unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
llaskin/AI-SDR-Skill-Pack
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.