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.66x

Quality

75%

Does it follow best practices?

Impact

95%

1.66x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills_all/algorithmic-art/SKILL.md

Quality

Content

56%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 content is actionable with a clear creative workflow and concrete p5.js/HTML examples, but it is held back by heavy repetition of the craftsmanship framing and template-reading reminders, plus references to bundle files that are not present in the skill directory.

Suggestions

Collapse the repeated craftsmanship emphasis (it appears in CRITICAL GUIDELINES, ESSENTIAL PRINCIPLES, CRAFTSMANSHIP REQUIREMENTS, and the philosophy examples) into a single concise statement to reduce padding.

State the instruction to read templates/viewer.html once in STEP 0 and refer back to it instead of restating it across INTERACTIVE ARTIFACT CREATION and RESOURCES.

Provide the referenced templates/viewer.html and templates/generator_template.js files, or remove the references and inline only what is essential, so progressive disclosure points to real resources.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the craftsmanship framing is repeatedly hammered ('meticulously crafted algorithm', 'master-level implementation', 'painstaking optimization' restated across multiple sections) and the instruction to read templates/viewer.html is repeated 4+ times, matching level 2's 'several unnecessary explanations or padded sections' rather than level 3's mostly-efficient bar.	2 / 5
Actionability	Provides concrete executable code (randomSeed/noiseSeed, params object, setup/draw, full HTML artifact skeleton, sidebar control-group HTML) with only minor gaps (the params object leaves fields as comments for the model to fill), matching level 4's 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	Clear multi-step sequence (Philosophy Creation → Deduce conceptual seed → p5.js implementation with STEP 0 → Interactive artifact) with most checkpoints present; no explicit validate-the-output-runs step is a minor gap, and the destructive/batch cap does not apply to this creative skill, so level 4 fits rather than 3 or 5.	4 / 5
Progressive Disclosure	References to templates/viewer.html and templates/generator_template.js are clearly signaled, but those files do not exist in the bundle, and large blocks that belong in separate files (philosophy examples, full HTML template spec) are inlined into SKILL.md, matching level 3's 'references present but... content that should be separate is inline' rather than level 4.	3 / 5
	Total	13 / 20 Passed

Description

95%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 strong: third-person voice, explicit what-and-when structure, and comprehensive natural trigger terms covering the generative-art domain. Specificity is the only slightly softer dimension, as the action verbs could be more granular.

Dimension	Reasoning	Score
Specificity	Quotes 'Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration' — names the domain plus several specific capabilities (seeded randomness, interactive parameter exploration, p5.js), with only minor gaps in coverage, matching the 'several specific actions' anchor rather than the fully comprehensive level 5.	4 / 5
Completeness	Explicitly answers both what ('Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration') and when ('Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems') with concrete trigger phrases, matching the level 5 anchor.	5 / 5
Trigger Term Quality	Quotes 'creating art using code, generative art, algorithmic art, flow fields, or particle systems' — comprehensive coverage of natural synonyms a user would say; file extensions are not applicable to this domain, so it matches the level 5 anchor rather than level 4's 'a few natural terms missing'.	5 / 5
Distinctiveness Conflict Risk	The p5.js generative-art niche with distinct triggers (flow fields, particle systems, generative/algorithmic art) is a clear niche with minimal conflict risk, matching level 5; 'creating art' alone could be broad but the surrounding specificity keeps it distinct.	5 / 5
	Total	19 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Microck/ordinary-claude-skills
Path: skills_all/algorithmic-art/SKILL.md
Commit: 1056d29

Reviewed: 6 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.