CtrlK
BlogDocsLog inGet started
Tessl Logo

consistency-audit

Adversarial consistency audit of a multi-document package across symbol lineage, bidirectional cross-references, brand discipline and naming drift, via scripts/audit_full.sh and the four dimensional audit_*.sh scripts. Use when the user asks to audit a documentation, proposal or discovery package for orphan references, asymmetric links or naming drift before release. [EXPLICIT]

63

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/claude-native-toolkit/skills/consistency-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Well-structured with clean progressive disclosure, but the body carries noise (evidence-tags, redundant TL;DR, boilerplate Packet) and defers the core executable script invocation to references, weakening actionability and conciseness.

Suggestions

Drop the [EXPLICIT]/[INFERENCE]/[SUPUESTO]/[DOC] tags and the redundant '## TL;DR' line to recover tokens without losing information.

Add the concrete audit command (e.g. `bash scripts/audit_full.sh <package-dir>`) to the Procedure so the core action is executable from the body.

Trim or localize the auto-generated Spanish Packet block, and remove references to packet layers (knowledge/, prompts/, examples/, agents/) that do not exist in this bundle.

DimensionReasoningScore

Conciseness

Sections are short, but pervasive evidence-tags ([EXPLICIT], [INFERENCE], [SUPUESTO], [DOC]), a redundant '## TL;DR' that only restates the title, and the Spanish boilerplate Packet block add tokens that do not earn their place.

3 / 5

Actionability

The Procedure defers the core action to references ('open the matching references/ playbook', 'Apply its decision tables') and never shows how to run scripts/audit_full.sh in the body, leaving a key executable detail missing.

3 / 5

Workflow Clarity

Three sequenced steps with a validate-and-tag checkpoint plus a Quality Criteria checklist and Contract acceptance gate give a clear sequence, though steps remain somewhat abstract and lack an explicit fix-retry loop.

4 / 5

Progressive Disclosure

SKILL.md is a lean overview with a clearly signaled one-level-deep references table whose five files all exist, plus a scripts/ directory; deep playbooks are appropriately split out and easy to navigate.

5 / 5

Total

15

/

20

Passed

Description

92%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, specific description that names concrete audit dimensions and tooling, with an explicit third-person 'Use when' trigger clause. Trigger-term coverage is good but could add a few more natural synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete audit dimensions — 'symbol lineage, bidirectional cross-references, brand discipline and naming drift' plus 'orphan references, asymmetric links' — and names the executing mechanism ('scripts/audit_full.sh and the four dimensional audit_*.sh scripts'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Clearly states what it does ('Adversarial consistency audit... across symbol lineage, bidirectional cross-references...') and gives an explicit 'Use when the user asks to audit... before release' trigger clause with concrete phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ('audit', 'consistency', 'documentation, proposal or discovery package', 'orphan references', 'naming drift', 'before release'), but a few common synonyms/variations users might say are missing, so it sits just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (multi-document package consistency auditing) with named tooling and distinct triggers, minimizing overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

68%

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

Validation — 11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

11

/

16

Passed

Repository
JaviMontano/claude-plugins
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.