CtrlK
BlogDocsLog inGet started
Tessl Logo

audit-content

Verifies truthfulness, accuracy, and link integrity of content before publishing. Catches fabricated statistics, dead URLs, misattributed sources, and company claims that contradict the brand DNA.

64

Quality

76%

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 ./audit-content/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is a well-structured, highly actionable audit workflow with clear sequencing and a concrete output template. Its only real weakness is mild redundancy between the opening paragraph, the workflow steps, and the Rules section.

Suggestions

Remove the verbatim restate of the frontmatter description in the opening paragraph, or trim it to a single orienting sentence.

Consolidate the Rules section so it only adds net-new guidance (e.g. arXiv-ID checks, time-bounding) rather than restating steps already covered in the Workflow.

Consider moving the full report markdown template into a reference file and summarizing the structure inline, to keep the main body focused on the audit procedure.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but the opening paragraph restates the frontmatter description verbatim and the Rules section reiterates workflow steps (e.g. Rule 1 restates Step 3's "check every URL"), so it could be tightened.

2 / 3

Actionability

Provides concrete, executable guidance throughout: explicit PASS/BROKEN/MISMATCH/UNVERIFIABLE categories, named fabrication patterns, a brand-DNA cross-reference checklist, and a copy-paste markdown report template.

3 / 3

Workflow Clarity

The six-step workflow is clearly sequenced with verification built into each step (URL fetch, source web-search, brand-DNA cross-check); the verification categorization acts as explicit checkpoints, and fixing is deliberately out of scope so a fix-retry loop is not applicable.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single SKILL.md is well-organized into clear sections (When To Use, Workflow, Output Format, Rules, What This Skill Does NOT Do) with no nested or multi-level references.

3 / 3

Total

11

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, clearly conveying a content-verification niche. Its main weakness is the absence of an explicit "Use when..." trigger clause, which leaves the activation condition implied rather than stated.

Suggestions

Add an explicit trigger clause, e.g. "Use before publishing articles, or when the user asks to fact-check, audit, or verify content claims."

Include more natural user phrasings such as "fact-check", "audit my article", or "verify citations" alongside the current technical terms.

Tighten the overlap between "truthfulness, accuracy, and link integrity" and the later "fabricated statistics, dead URLs..." list to avoid near-duplication.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Verifies truthfulness, accuracy, and link integrity" and "Catches fabricated statistics, dead URLs, misattributed sources, and company claims that contradict the brand DNA" — rather than vague language.

3 / 3

Completeness

Clearly states what the skill does, but "when" is only implied via "before publishing"; there is no explicit "Use when..." clause, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Contains relevant natural terms ("dead URLs", "fabricated statistics", "misattributed sources") but lacks common user phrasings like "fact-check my article" or "audit my content" and has no explicit trigger clause.

2 / 3

Distinctiveness Conflict Risk

The content-auditing niche with the distinctive "brand DNA" reference and specific verification categories makes it unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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
onvoyage-ai/gtm-engineer-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.