CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

genai-disclaimer

Standard disclaimer and attribution templates for AI-generated or AI-assisted data analysis outputs

Quality

76%

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 ./.claude/skills/skills/genai-disclaimer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a strong, highly actionable instruction-only skill: ready-to-use templates at three levels plus clear decision tables for when each applies. Its only weaknesses are minor — a trimmable regulatory section and content long enough that a reference split would improve organization.

DimensionReasoningScore

Conciseness

The body is efficient: copy-paste templates, two decision tables, and terse bullet lists with almost no padding. The 'Regulatory Considerations' section (e.g. 'Transparency obligations for AI-generated content', 'Executive orders and agency policies on AI use') is background Claude largely already knows and could be trimmed to one line, matching the anchor 'Efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean score-5 anchor.

4 / 5

Actionability

Three complete, copy-paste-ready disclaimer templates (Short, Medium, Full), a level-selection table by output type, a per-command mapping ('/data-describe → Full'), and a fallback rule ('When in doubt, use the Full disclaimer') cover the common cases completely. This matches the anchor 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

For a simple single-purpose skill, the action is unambiguous: check 'When to Apply' criteria, pick a level via the 'Choosing the Right Level' table, and use the 'Integration with Commands' mapping for the command that produced the output. The rubric's simple-skill exception applies, and no destructive or batch operations are involved, so no validation cap applies.

5 / 5

Progressive Disclosure

No bundle files exist, and the body is well organized into clearly headed sections (templates, level selection, attribution, command integration, regulatory). At ~107 lines it exceeds the under-50-line simple-skill exception, and the regulatory section is arguably reference material that could live in a separate file, matching 'Good structure; most content is appropriately placed; minor organization gaps' rather than the well-split score-5 anchor.

4 / 5

Total

18

/

20

Passed

Description

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

The description is concise, domain-specific, and answers 'what' clearly, but it omits any 'when to use' trigger guidance and lacks synonym coverage ('disclosure', 'AI content'). It sits just above the midpoint of the rubric: distinct and specific, yet incomplete as a trigger surface.

Suggestions

Add an explicit trigger clause, e.g. 'Use when producing AI-generated or AI-assisted analysis outputs, or when the user asks for a disclaimer, disclosure, or attribution notice.'

Include natural synonym keywords such as 'disclosure', 'AI content notice', and 'attribution statement' so users phrasing the need differently still match.

Name the deliverable variants briefly (inline footnote, report footer, formal disclosure) to make the concrete actions more comprehensive.

DimensionReasoningScore

Specificity

The description names its domain ('disclaimer and attribution templates') and one concrete deliverable (templates), quoting: 'Standard disclaimer and attribution templates for AI-generated or AI-assisted data analysis outputs'. It does not list multiple specific actions, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than the score-4 anchor 'Lists several specific actions'.

3 / 5

Completeness

The 'what' is clear (standard disclaimer and attribution templates for AI outputs) but there is no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3: 'Has a clear what but when is missing or only weakly implied'.

3 / 5

Trigger Term Quality

It contains relevant keywords users would say ('disclaimer', 'attribution', 'AI-generated', 'AI-assisted', 'data analysis') but misses common natural variations such as 'disclosure', 'AI content', or 'add a disclaimer'. This matches the anchor 'Some relevant keywords but missing common variations or synonyms', below the good-coverage level of score 4.

3 / 5

Distinctiveness Conflict Risk

The niche is clear and specific (disclaimer/attribution templates for AI data-analysis outputs), which makes conflict with other skills unlikely. It falls short of score 5 only because the phrasing does not include explicit trigger phrases that would fully separate it from generic citation or attribution skills.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

dathere/qsv

Path

.claude/skills/skills/genai-disclaimer/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.