CtrlK
BlogDocsLog inGet started
Tessl Logo

article-illustrations

Generate hand-drawn 16:9 article illustrations featuring the Grav character IP. Turns article concepts into memorable whiteboard-sketch explanations with a recurring floating character, sparse annotations, and absurd metaphors.

61

Quality

72%

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 ./skills/article-illustrations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with a clear validated workflow, but suffers from repeated style constraints across four sections and does not split its longer reference material into bundle files. Tightening redundancy and extracting reference material would lift conciseness and progressive disclosure.

Suggestions

De-duplicate the style rules: state them once in the Visual Style table and have the Prompt Template and QA Checklist reference it rather than re-listing them.

Move the Character spec, Visual Style detail, and Prompt Template into files under references/ (e.g. references/grav-character.md, references/prompt-template.md) and link to them one level deep from SKILL.md.

DimensionReasoningScore

Conciseness

Mostly efficient with domain-specific content (Grav IP, color discipline, structure types) Claude would not know, but the same style constraints are restated across Visual Style, Step 3, the Prompt Template, and the QA Checklist, so it could be tightened; not the lean 'every token earns its place' anchor.

2 / 3

Actionability

Provides a copy-paste-ready Prompt Template with {variables}, a concrete shot-list structure, four worked examples, and a granular QA checklist with explicit must-pass and regenerate-if items, matching the 'fully executable / copy-paste ready' anchor for an instruction-only skill.

3 / 3

Workflow Clarity

Steps 1-4 are clearly sequenced (Digest → Plan shot list → Generate → QA Check) with an explicit validation checkpoint and feedback loop ('Regenerate or edit on any failure'), matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are empty) and the ~200-line body is self-contained with well-organized sections, but content such as the Visual Style table, Character spec, and Prompt Template is inline rather than split into one-level-deep reference files, fitting 'some structure but content that should be separate is inline'.

2 / 3

Total

10

/

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 but lacks an explicit 'Use when...' trigger clause, capping completeness at 2. Trigger-term coverage is good but misses common variations present in the body.

Suggestions

Append an explicit trigger clause, e.g. 'Use when adding inline illustrations to articles, blog posts, or documentation, or when turning abstract concepts into visual metaphors.'

Add common user phrasings ('blog post', 'documentation', 'article diagrams') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Generate hand-drawn 16:9 article illustrations' and 'Turns article concepts into memorable whiteboard-sketch explanations' — naming the deliverable format and the transformation, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural phrases a user might say ('article illustrations', 'whiteboard-sketch explanations', 'absurd metaphors') but omits common variations like 'blog post', 'documentation', or 'article diagrams' that the body covers, fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The recurring 'Grav character IP', 'hand-drawn', and 'whiteboard-sketch' framing carves a clear niche unlikely to trigger for other skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
rmyndharis/antigravity-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.