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

50%

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

42%

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

The body is well-organized and lean as a catalogue pointer, but it provides no executable p5.js guidance or real install commands, delegating everything to an upstream URL. Its value as a standalone skill is limited by the absence of concrete, actionable content.

Suggestions

Include a minimal executable p5.js seeded-sketch starter (e.g., a `createCanvas` + `randomSeed` snippet) so the skill is actionable without leaving the file.

Replace the `open https://...` placeholder with the actual command(s) to fetch or install the upstream bundle into the agent's skills directory.

Add a concrete invocation example showing how to call the skill by name or trigger phrase once installed, with an expected outcome.

Dimension	Reasoning	Score
Conciseness	The body is short and does not explain concepts Claude already knows, but it repeats the frontmatter description verbatim in "What it does" and carries meta-commentary ("Curated from Anthropic's official skills repository") that could be tightened, fitting the score-2 "mostly efficient but includes some unnecessary explanation".	2 / 3
Actionability	The only command is `open https://...` which merely launches a URL, and "install the upstream bundle into your active agent's skills directory" gives no actual install command or p5.js code; it describes and points rather than instructing, matching the score-1 "vague or abstract; no concrete code/commands".	1 / 3
Workflow Clarity	A loose sequence is present (inspect the upstream README, install the bundle, ask the agent to invoke) but the install step has no concrete command and there are no checkpoints, fitting the score-2 "steps listed but validation gaps; sequence present but checkpoints missing" rather than the fully-specified score-3.	2 / 3
Progressive Disclosure	The body is a brief, well-sectioned overview that points one level deep to a single external reference (the upstream repository), with no nested or multi-level indirection; for a short catalogue entry this matches the score-3 "clear overview with well-signaled one-level-deep references".	3 / 3
	Total	8 / 12 Passed

Description

57%

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 specific and distinctive, pinning a clear p5.js generative-art niche, but it lacks an explicit "Use when..." trigger clause and only implies when to activate. Stronger trigger guidance and a broader set of concrete actions would raise it above the middle of the scale.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating generative or procedural art, reproducible p5.js sketches, or artistic frame studies."

List more concrete actions beyond "create" (e.g., "generate, animate, export frames") to move specificity from a single capability toward multiple distinct actions.

Include more natural user-facing trigger terms such as "creative coding" or "art with code" alongside the existing keywords.

Dimension	Reasoning	Score
Specificity	"Create generative art using p5.js with seeded randomness so every render is reproducible" names the domain and the core mechanism (seeded reproducibility), but describes essentially one capability rather than a list of multiple concrete actions, matching the score-2 anchor rather than the score-3 "Lists multiple specific concrete actions".	2 / 3
Completeness	It clearly answers "what" (create reproducible generative art with p5.js) but the "when" is only implied via "Useful for procedural posters, motion-style stills, and artistic frame studies" with no explicit "Use when..." trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	The description surfaces relevant natural terms ("generative art", "p5.js", "seeded randomness", "procedural posters") but mixes in less-natural jargon ("motion-style stills", "artistic frame studies") and omits common variations like "creative coding" or "art with code", fitting the score-2 "some relevant keywords but missing common variations".	2 / 3
Distinctiveness Conflict Risk	"Create generative art using p5.js with seeded randomness" carves a clear niche (reproducible p5.js art) that is unlikely to trigger for unrelated skills, matching the score-3 "clear niche with distinct triggers; unlikely to conflict".	3 / 3
	Total	9 / 12 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: f2760fd

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