algorithmic-art

Create generative art using p5.js with seeded randomness so every render is reproducible. Useful for procedural posters, motion-style stills, and artistic frame studies.

Quality

49%

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 ./skills/algorithmic-art/SKILL.md

Quality

Content

40%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 concise but offers little executable guidance: it defers almost all real instruction to an external upstream repository and provides no local bundle files, leaving the agent without concrete steps or referenceable detail.

Suggestions

Inline at least a minimal executable quick-start (e.g. a p5.js sketch template with seeded random) rather than pointing entirely off-site.

Provide concrete installation steps (exact paths/commands) instead of 'inspect the upstream README for exact paths'.

If the upstream bundle is the source of truth, vendor key reference files locally (references/ or scripts/) so progressive disclosure has actual one-level-deep targets.

Dimension	Reasoning	Score
Conciseness	The body is short and largely free of padded explanation, though it restates the description and includes a few sentences about catalogue advertisement that could be trimmed.	4 / 5
Actionability	Guidance is mostly high-level: it tells the agent to install the upstream bundle and 'inspect the upstream README for exact paths' via an `open` command, but gives no concrete executable steps, code, or commands to actually run the skill.	2 / 5
Workflow Clarity	A rough sequence is present (inspect upstream README, install bundle, invoke by name/trigger) but steps are poorly defined with no specifics on how to install or verify, and no validation checkpoints.	2 / 5
Progressive Disclosure	The body has minimal structure with section headers, but the actual detailed instructions live entirely off-site (the upstream repo); there are no local reference files (references/, scripts/, assets/ are absent), so navigation to real detail is absent.	2 / 5
	Total	10 / 20 Passed

Description

58%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 reasonably specific and distinct, with solid trigger phrase coverage, but it lacks an explicit 'Use when...' clause telling Claude when to invoke the skill, which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when creating reproducible generative art, procedural posters, or motion-style stills with p5.js.'

Expand the action list to be more comprehensive (e.g. mention sketch setup, seed-based variation, frame export) rather than a single action.

Add common synonyms or file-format triggers a user might naturally say (e.g. 'p5.js sketches', 'creative coding').

Dimension	Reasoning	Score
Specificity	The description names the domain (generative art via p5.js) and one concrete action (create generative art with seeded reproducibility) but does not enumerate multiple specific actions like the score-5 anchor.	3 / 5
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance; per the judging guidelines a missing use-when clause caps completeness at 3.	3 / 5
Trigger Term Quality	Triggers cover natural phrases ('generative art', 'procedural art', 'algorithmic art', 'p5js', '生成艺术') with good coverage, though it lacks some common synonyms a user might say.	4 / 5
Distinctiveness Conflict Risk	The p5.js generative-art niche with seeded randomness is fairly distinct with minimal overlap risk against unrelated skills, though it could overlap slightly with other image-generation skills.	4 / 5
	Total	14 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/algorithmic-art/SKILL.md
Commit: 1a7a23d

Reviewed: about 7 hours 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.