CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/algorithmic-art/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%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 body is a catalogue stub: lean and cleanly organized, but it provides no executable guidance for the skill's actual purpose — it defers entirely to an upstream GitHub URL with a vague 'install the upstream bundle' instruction. Actionability and workflow clarity are the clear weak points, as the agent is left without concrete install steps or any minimal working example.

Suggestions

Replace the vague 'install the upstream bundle into your active agent's skills directory' with a concrete command sequence (e.g., git clone the skills repo and cp/symlink the algorithmic-art directory into the skills path, with an example path).

Include a minimal executable example of the skill's core capability in the body — e.g., a short p5.js snippet showing seeded randomness via a seeded PRNG — so the entry is useful even before installing the full bundle.

Drop the 'What it does' section (a verbatim repeat of the frontmatter description) and instead use that space for the concrete install/invocation steps.

DimensionReasoningScore

Conciseness

The body is short with no padding or explanations of known concepts, but the 'What it does' section duplicates the frontmatter description verbatim — a minor trim opportunity that keeps it below the lean top anchor.

4 / 5

Actionability

Only one concrete command is given ('open https://github.com/...'), while the real instruction — 'install the upstream bundle into your active agent's skills directory' — is a high-level hint with no clone/copy command, target path, or example invocation of the actual workflow.

2 / 5

Workflow Clarity

A rough sequence exists (inspect upstream → install bundle → invoke by name or trigger), but the critical install step is undefined, there are no concrete sub-steps, and no verification that the skill is installed or working.

2 / 5

Progressive Disclosure

The body is well-organized into short sections with a single clearly signaled upstream pointer, and no local bundle files exist to misstructure. It falls short of the top anchor because all substantive content lives in an external repository rather than one-level-deep local references, so the skill itself contains no detail to navigate to.

4 / 5

Total

12

/

20

Passed

Description

75%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.

A concise, specific description that names the tool, the key technical property (seeded, reproducible renders), and concrete use cases. Both 'what' and an explicit 'when'-equivalent are present. The main gap is the absence of a direct 'Use when...' trigger clause and a few natural synonyms.

DimensionReasoningScore

Specificity

Names the tool ('p5.js'), a concrete technical property ('seeded randomness so every render is reproducible'), and concrete outputs ('procedural posters, motion-style stills'), but enumerates only one main action rather than the multiple distinct actions of the top anchor.

4 / 5

Completeness

Clearly answers 'what' (create reproducible generative art with p5.js) and provides an explicit when-equivalent ('Useful for procedural posters, motion-style stills, and artistic frame studies'), though a direct 'Use when...' clause would be more directive.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ('generative art', 'procedural posters', 'seeded randomness', 'p5.js'), but misses common variations like 'creative coding' or 'make art'.

4 / 5

Distinctiveness Conflict Risk

'generative art with p5.js and seeded randomness' is a clear niche, but as an image-generation skill it has minor overlap risk with sibling image-generation skills on generic requests like 'make art'.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
Reviewed

Table of Contents

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.