Evaluation report
Warningssuperdesign · skillaad2a00· 2 months ago
Every check MetaHub ran on this artifact, grouped by area. Static checks run on the source at publish time; behavioral checks run the artifact in a sandbox and judge what it actually does.
Structural
5 passedRepository is reachable
https://github.com/superdesigndev/superdesign-skill @ aad2a00 — ★ 326 · MIT · last push 3 days ago
Manifest detected
kind=skill slug=superdesign · path=skills/superdesign · source=SKILL.md
Slug is URL-safe
"superdesign" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/superdesign
Version is semver
0.1.0
Documentation
4 passed1 warningDescription qualitywarn
29 words · 216 chars — manifest description is empty; graded the GitHub repo description instead
A skill's manifest description doubles as its trigger — add one to SKILL.md (15+ words, e.g. “use this skill when …”).
README is present and substantial
12,269 chars · 10 sections · 10 code blocks
Tags / topics declared
12 total — agent-skills, ai-design, claude-code, claude-skill, claude-skills, coding-agent (+6)
README has usage / example sections
found: Example · Example
Homepage / docs URL declared
https://superdesign.dev
Safety
2 passedLICENSE file at repo root
LICENSE
No sensitive files in the repo
scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found
Kind-specific
3 passed1 warningSkill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: SKILL.md present
found at skills/superdesign/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
372 words · 2,661 chars · 2 code blocks
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Maintenance
1 passed2 warningsTests detectedwarn
no test/tests/__tests__/spec/t/ dirs, no JVM src/test/, and no JS/TS/Python/Go/Ruby/Elixir test files
Add tests (even a smoke test). Consumers gauge maintenance quality by their presence.
CI configuration detectedwarn
no CI config found (looked for GitHub Actions, CircleCI, GitLab CI, etc.)
Add a simple workflow (lint + test on PR) — it tells consumers the artifact is built reproducibly.
Recent activity
last push 3 days ago
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.