CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

auditing-skills

Use when checking skills for security or quality issues, reviewing audit results from skills.sh or Tessl, or remediating findings across published skills.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/auditing-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, well-sequenced auditing guide with concrete URLs, commands, and copy-paste templates. It is weakened by redundancy between the per-finding remediation bullets and the reusable template sections, and by keeping all reference material inlined in one monolithic file — the very anti-pattern it teaches readers to fix.

Suggestions

Extract the finding catalogs and remediation templates (Common Finding Categories, Remediation Patterns, Common Tessl Finding Categories) into references/ files, replacing them with one-line links — the skill's own "Monolithic Files" remediation guidance applied to itself.

Deduplicate the per-finding remediation bullets (W007, W011, Trust Hub entries) against the reusable templates in "Remediation Patterns" — state the trigger per finding and link once to the shared template instead of repeating its bullets.

Add an explicit feedback loop to both audit workflows: if "uv run scripts/validate_repo.py" fails, fix the reported issues and re-run until validation passes before considering remediation complete.

DimensionReasoningScore

Conciseness

The per-finding remediation bullets (e.g., W007's "use environment variable references... never log, display, or echo token values") duplicate the later "Credential Security" and "Handling External Content" reusable templates, and the "Key phrases to include" list restates the same template content a third time — several sections could be consolidated, matching the mostly-efficient-but-could-be-tightened anchor. Not 4: the redundancy is repeated across sections rather than a minor instance.

3 / 5

Actionability

Provides concrete URL patterns ("https://skills.sh/{org}/{repo}/{skill-name}/security/{auditor}"), an executable validation command ("uv run scripts/validate_repo.py"), copy-paste markdown remediation templates, and a before/after YAML example — fully actionable guidance covering the common cases, matching the top anchor.

5 / 5

Workflow Clarity

Both audit workflows are numbered and sequenced with gating checkpoints ("For any non-Pass result, fetch the detailed finding", "any skill below 85%") and a terminal validation step, matching the clear-sequence-with-most-checkpoints anchor. Not 5: no explicit validate→fix→re-validate feedback loop for the batch remediation workflow, which the rubric flags as important for batch operations.

4 / 5

Progressive Disclosure

The single file inlines ~150 lines of finding catalogs, scoring-dimension tables, and remediation templates — exactly the "Monolithic Files" pattern the skill itself instructs users to remediate by extracting to references/ — while section headers provide reasonable structure, matching the some-structure-but-inline-content anchor. Not 4: no references/ split exists at all despite the volume of reference material.

3 / 5

Total

15

/

20

Passed

Description

78%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 well-targeted description with explicit trigger guidance, platform-named actions, and low conflict risk. Its main weakness is structural: the capability statement lives inside the "Use when" clause rather than preceding it, which slightly blurs what vs. when.

DimensionReasoningScore

Specificity

Lists three specific actions — "checking skills for security or quality issues", "reviewing audit results from skills.sh or Tessl", "remediating findings across published skills" — with named platforms, matching the anchor for several specific actions with minor gaps. Not 5: the verbs stay domain-generic and never state a concrete output artifact.

4 / 5

Completeness

The explicit "Use when..." clause answers when, and the gerunds (checking, reviewing, remediating) convey what, so both are present as in the anchor for both-with-room-to-improve. Not 5: the what is embedded inside the when-clause rather than a standalone capability statement, blurring the what/when separation; not 3 because both are answered concretely.

4 / 5

Trigger Term Quality

Good natural-term coverage including "security", "quality issues", "audit results", "skills.sh", "Tessl", and "remediating findings", which users would plausibly say. Not 5: common synonyms like "fix findings", "review skills", or "lint" are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — auditing published skills against named external scanners (skills.sh, Tessl) — with triggers unlikely to collide with generic security-review or code-review skills. Matches the anchor for a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

12

/

16

Passed

Repository

dbt-labs/dbt-agent-skills

Path

.claude/skills/auditing-skills/SKILL.md

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.