algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

1.80x

Quality

67%

Does it follow best practices?

Impact

54%

1.80x

Average score across 10 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./examples/algorithmic-art/SKILL.md

Quality

Discovery

100%

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

This is a strong skill description that clearly defines a specific niche (algorithmic/generative art with p5.js), includes an explicit 'Use when' clause with natural trigger terms, and adds a useful behavioral constraint about originality. The description is concise yet comprehensive, covering capabilities, triggers, and guardrails effectively.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and techniques: 'algorithmic art using p5.js', 'seeded randomness', 'interactive parameter exploration', 'flow fields', 'particle systems'. These are concrete, specific capabilities.	3 / 3
Completeness	Clearly answers both 'what' (creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration) and 'when' (explicit 'Use this when...' clause listing trigger scenarios). Also includes a behavioral constraint about avoiding copyright violations.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would actually say: 'art using code', 'generative art', 'algorithmic art', 'flow fields', 'particle systems', and 'p5.js'. These cover the main ways users would phrase such requests.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche combining p5.js, generative/algorithmic art, seeded randomness, and specific techniques like flow fields and particle systems. Unlikely to conflict with general coding skills or other art-related skills due to the specific domain focus.	3 / 3
	Total	12 / 12 Passed

Implementation

35%

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

This skill is highly verbose and repetitive, spending significant tokens on motivational language, repeated emphasis on craftsmanship, and philosophical framing that Claude doesn't need. While it provides a clear two-step workflow and some concrete code snippets, the actionable technical content is buried under layers of creative direction. The skill would benefit enormously from being cut to roughly one-third its current length, moving examples and detailed specifications into separate referenced files.

Suggestions

Cut content by 60-70%: Remove all repeated instructions (e.g., 'use the template' appears 6+ times, craftsmanship emphasis appears 4+ times), motivational language, and explanations of concepts Claude already knows (what generative art is, how creativity works).

Move the philosophy examples and HTML structure details into separate referenced files (e.g., examples/philosophies.md and templates/README.md) to reduce the main skill to a concise workflow overview.

Add explicit validation checkpoints: after generating the HTML artifact, include steps to verify all required features work (seed navigation, parameter controls, download button) before delivering to the user.

Replace the abstract algorithm guidance ('if the philosophy is about organic emergence, consider using...') with a single concrete end-to-end example showing philosophy → actual working code, demonstrating the expected quality level.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~400+ lines. Repeats the same concepts multiple times (e.g., 'meticulously crafted' emphasis repeated 4+ times, 'use the template' repeated 6+ times, philosophy length guidance repeated 3 times). Explains creative processes Claude already understands, and includes extensive motivational language ('beauty lives in the process') that wastes tokens without adding actionable value.	1 / 3
Actionability	Provides some concrete code snippets (seeded randomness, canvas setup, HTML structure) and references a template file, but much of the guidance is abstract and philosophical rather than executable. The code examples are incomplete fragments rather than copy-paste ready implementations. The actual algorithm creation is left entirely to interpretation of vague philosophical guidance.	2 / 3
Workflow Clarity	The two-step process (philosophy creation → p5.js implementation) is clearly stated, and Step 0 (read template) is called out. However, there are no validation checkpoints - no step to verify the HTML works, no error recovery for broken artifacts, no checklist for ensuring all required features are present. The workflow also conflates creative guidance with technical steps, making the sequence harder to follow.	2 / 3
Progressive Disclosure	References templates/viewer.html and templates/generator_template.js appropriately, but the SKILL.md itself is monolithic - it contains massive inline sections (philosophy examples, HTML structure, sidebar details) that could be split into separate reference files. The main file tries to be both a creative brief and a technical specification, resulting in a wall of text that's hard to navigate.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: douglasvought/wiggle-skills
Commit: b27906e

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.