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.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/article-illustrations/SKILL.md

Quality

Content

77%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 highly actionable with a clear validated workflow, but it is a monolithic single file with no progressive disclosure to bundle files and notable redundancy of style rules across sections.

Suggestions

Move the Prompt Template and QA Checklist into separate reference files (e.g. references/prompt-template.md, references/qa-checklist.md) and link to them one level deep to reduce inline length and redundancy.

Consolidate the repeated style/color/whitespace rules into a single canonical section (Visual Style table) and reference it from Step 3 and the Prompt Template instead of restating them.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-organized, but the style rules (colors, whitespace, Grav traits) are restated across the Instructions, Visual Style table, Prompt Template, and QA Checklist, which could be tightened.	3 / 5
Actionability	Provides a copy-paste-ready Prompt Template with {variables}, a concrete shot-list schema, four usage examples, and a specific QA checklist — fully executable guidance covering common cases.	5 / 5
Workflow Clarity	Four clearly sequenced steps (Digest → Plan shot list → Generate → QA Check) with an explicit validation checkpoint and a regenerate-or-edit feedback loop for this batch operation.	5 / 5
Progressive Disclosure	Good internal section structure, but the skill is a single ~207-line file with no bundle files in references/scripts/assets, and content that could be split out (Prompt Template, QA Checklist) is fully inlined.	3 / 5
	Total	16 / 20 Passed

Description

62%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 concretely states what the skill does and occupies a distinct niche, but it omits an explicit 'when to use' trigger clause, which caps completeness and leaves trigger-term coverage only partial.

Suggestions

Append an explicit 'Use when...' clause naming concrete triggers (e.g. 'Use when adding inline illustrations to articles, blog posts, or documentation, or when the user asks for hand-drawn whiteboard sketches of concepts').

Add natural synonyms and variations users might say (e.g. 'article diagrams', 'concept sketches', 'blog illustrations') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Generate hand-drawn 16:9 article illustrations', 'Turns article concepts into memorable whiteboard-sketch explanations', with specific features (recurring floating character, sparse annotations, absurd metaphors); not quite comprehensive enough for a 5.	4 / 5
Completeness	The 'what' is clear and concrete, but the description lacks any 'when should Claude use it' clause — trigger guidance appears only in the body, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Contains some natural keywords ('article illustrations', 'hand-drawn', 'whiteboard-sketch') but misses common synonyms/variations and any explicit 'use when' phrasing users would naturally say.	3 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — 'hand-drawn 16:9 article illustrations featuring the Grav character IP' — with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/article-illustrations/SKILL.md
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.