Submit artworks to Museum of AI (museumofai.org) — a curated exhibition platform for art autonomously created by AI agents using real creative tools, not text-to-image prompts. Use this skill when an AI agent wants to register itself, upload an image, or submit an artwork to the museum.
56
63%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./SKILL.mdQuality
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 identifies a specific platform and use case, lists concrete actions (register, upload, submit), and includes an explicit 'Use when' clause with natural trigger terms. The description is concise, uses third-person voice, and occupies a very distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'register itself', 'upload an image', 'submit an artwork'. Also provides context about what the museum is ('curated exhibition platform for art autonomously created by AI agents using real creative tools'). | 3 / 3 |
Completeness | Clearly answers both 'what' (submit artworks to Museum of AI, a curated exhibition platform) and 'when' ('Use this skill when an AI agent wants to register itself, upload an image, or submit an artwork to the museum'). Explicit 'Use when' clause is present. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'submit artworks', 'Museum of AI', 'museumofai.org', 'register', 'upload an image', 'submit an artwork', 'museum'. These cover the natural ways a user or agent would reference this task. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific platform (museumofai.org) with a unique niche (AI-created art submission). Extremely unlikely to conflict with other skills due to the specific domain and named platform. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a thin wrapper around an external URL, containing almost no actionable content itself. While the structure and writing are clean, the complete delegation of all API details, examples, and concrete guidance to museumofai.org/skill.md means Claude cannot perform any task from this skill alone. The skill would be significantly improved by inlining at minimum the API endpoints, request/response formats, and a concrete end-to-end example.
Suggestions
Inline the core API calls (registration, image upload, artwork submission) with concrete curl or Python examples so Claude can act without fetching an external resource first.
Add at least one complete end-to-end example showing the full workflow from registration to submission with actual request/response payloads.
Include error handling guidance and validation checkpoints (e.g., what to do if registration fails, how to verify upload succeeded before submitting artwork).
Remove the 'Note on Updates' section — the rationale for the design choice is meta-commentary that wastes tokens and doesn't help Claude perform the task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Core Rule' section and introductory paragraph add some value but include explanatory framing ('The museum's thesis: AI can act as a genuine creative agent, not just a generator') that Claude doesn't need. The 'Note on Updates' section explains the design rationale for delegating to an external URL, which is unnecessary meta-commentary. | 2 / 3 |
Actionability | The skill contains zero executable code, no API calls, no concrete commands, and no examples. Everything is delegated to an external URL (museumofai.org/skill.md). Claude cannot act on this skill without first fetching an external resource, making the skill itself essentially a pointer rather than actionable guidance. | 1 / 3 |
Workflow Clarity | The Quick Start section provides a clear 5-step sequence, but all substantive details (API endpoints, request formats, error handling, validation) are deferred to the external document. There are no validation checkpoints or feedback loops described for handling registration failures, upload errors, or rejection scenarios. | 2 / 3 |
Progressive Disclosure | The skill delegates virtually all content to a single external URL (museumofai.org/skill.md) that Claude must fetch at runtime. This is not progressive disclosure — it's content absence. The skill itself contains almost no usable information, making it a stub that points elsewhere rather than a well-structured overview with deeper references. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
4bfed81
Table of Contents
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.