Evaluation report
Failingmodel-hierarchy · skill9095f83· 3 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/zscole/model-hierarchy-skill @ 9095f83 — ★ 344 · Python · MIT · last push 5 months ago
Manifest detected
kind=skill slug=model-hierarchy · source=SKILL.md
Slug is URL-safe
"model-hierarchy" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/model-hierarchy
Version is semver
0.1.0
Documentation
3 passed2 warningsDescription qualitywarn
10 words · 72 chars — skills use the description as their trigger; aim higher — manifest description is empty; graded the GitHub repo description instead
Aim for 15+ words and include trigger phrases like “use this skill when …”.
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
README is present and substantial
2,189 chars · 8 sections · 4 code blocks
README has usage / example sections
found: Quick Start
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
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 SKILL.md · frontmatter source: SKILL.md
Skill: body content present
1,302 words · 8,700 chars · 22 sections · 5 code blocks
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Maintenance
1 passed2 warningsRecent activitywarn
last push 5 months ago — looks slowing down
Consumers prefer artifacts that are actively maintained (threshold: 90 days, configurable via EVAL_RECENCY_PASS_DAYS).
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.
Tests detected
1 test directory · 2 test files