algorithmic-art

Algorithmic philosophies are computational aesthetic movements that are then expressed through code. Output .md files (philosophy), .html files (interactive viewer), and .js files (generative algorithms).

Quality

22%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills/skills/algorithmic-art/SKILL.md

Quality

Content

27%Scale 1-3

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

This skill is excessively verbose, repeating key concepts (template usage, craftsmanship emphasis, algorithmic philosophy definition) multiple times throughout. While the creative workflow is interesting and the two-phase structure is clear, the document would benefit enormously from being cut to roughly 1/3 its current length. The missing bundle files (templates/viewer.html, templates/generator_template.js) undermine the progressive disclosure strategy, and the lack of validation steps for the generated HTML artifacts is a notable gap.

Suggestions

Reduce content by at least 60% - eliminate repeated instructions about template usage (stated 4+ times), remove redundant craftsmanship emphasis phrases, and consolidate the philosophy examples to 1-2 instead of 5.

Provide the referenced bundle files (templates/viewer.html, templates/generator_template.js) so the progressive disclosure strategy actually works, and move detailed HTML structure and philosophy examples into those supporting files.

Add explicit validation steps: after generating the HTML artifact, include a checkpoint to verify it loads correctly, the seed controls function, and parameters update in real-time.

Replace the pseudocode HTML skeleton with one complete, minimal working example that demonstrates the full pipeline from philosophy to functioning artifact.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. Repeats the same concepts multiple times (e.g., 'meticulously crafted' emphasis repeated across sections, the template instructions are stated 3-4 times, 'algorithmic philosophy' concept is re-explained constantly). Explains concepts Claude already knows (what p5.js is, how parameters work, what seeded randomness means). The philosophy examples alone consume significant tokens while being largely redundant with each other.	1 / 3
Actionability	Provides some concrete code snippets (seeded randomness, canvas setup, control group HTML) but most are incomplete fragments or pseudocode-level templates rather than executable examples. The actual algorithm creation is left entirely abstract ('express the philosophy through code') with no complete working example. The HTML structure shown is a skeleton, not a working artifact.	2 / 3
Workflow Clarity	The two-step process (philosophy creation → p5.js implementation) is clearly sequenced, and there's a sub-step (Step 0: read template) that's well-called-out. However, there are no validation checkpoints - no step to verify the HTML works, no feedback loop for testing the generated art, no verification that the template was correctly followed. For a workflow producing complex HTML artifacts, this is a significant gap.	2 / 3
Progressive Disclosure	Despite referencing external files (templates/viewer.html, templates/generator_template.js), no bundle files are provided, making those references unresolvable. The SKILL.md itself is a monolithic wall of text with everything inline - the philosophy examples, implementation details, UI specifications, and creative process guidance are all crammed into one massive document with no meaningful separation. Content that should be in referenced files (like the detailed HTML structure, the philosophy examples) bloats the main file.	1 / 3
	Total	6 / 12 Passed

Description

17%Scale 1-3

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 introduces a novel but poorly defined concept ('algorithmic philosophies as computational aesthetic movements') without explaining concrete actions or providing trigger guidance. The jargon-heavy language would make it very difficult for Claude to know when to select this skill, and the lack of a 'Use when...' clause is a significant gap. The output file types listed are too generic to serve as meaningful differentiators.

Suggestions

Add an explicit 'Use when...' clause with natural trigger terms users might say, such as 'generative art', 'creative coding', 'procedural aesthetics', or 'algorithmic art'.

Replace abstract language like 'computational aesthetic movements expressed through code' with concrete actions such as 'Generates philosophy documents, interactive HTML viewers, and JavaScript-based generative art algorithms'.

Include example use cases or scenarios to clarify the skill's niche, e.g., 'Use when the user wants to create generative art projects, explore procedural design philosophies, or build interactive algorithmic visualizations'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('algorithmic philosophies', 'computational aesthetic movements') and lists output file types (.md, .html, .js), but the actual actions are vague—'expressed through code' doesn't specify concrete operations like 'generate', 'render', or 'animate'.	2 / 3
Completeness	The description partially addresses 'what' (output file types and vague domain) but completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent, which per the rubric caps completeness at 2, and the 'what' is also weak enough to warrant a 1.	1 / 3
Trigger Term Quality	The terms 'algorithmic philosophies' and 'computational aesthetic movements' are highly specialized jargon that users would almost never naturally say. There are no common trigger terms like 'generative art', 'creative coding', 'procedural generation', or similar natural phrases.	1 / 3
Distinctiveness Conflict Risk	The niche concept of 'algorithmic philosophies' is unusual enough to avoid many conflicts, but the output types (.md, .html, .js) are extremely generic and could overlap with numerous other skills. The domain is distinctive but poorly bounded.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: popey/claude-code-skills
Path: plugins/antigravity-awesome-skills/skills/algorithmic-art/SKILL.md
Commit: a5a6601

Reviewed: 5 days 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.