Evaluation report
Warningsinterview · skill3a6ecb2· 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/ryanb/dotfiles @ 3a6ecb2 — ★ 2,392 · Vim Script · MIT · last push 12 days ago
Manifest detected
kind=skill slug=interview · path=claude/skills/interview · source=SKILL.md
Slug is URL-safe
"interview" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/interview
Version is semver
0.1.0
Documentation
4 passed1 warningTags / 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.
Description quality
52 words · 342 chars — "Interview the user relentlessly about a plan or design until reaching shared und…"
README is present and substantial
4,149 chars · 4 sections · 9 code blocks
README has usage / example sections
found: Installation
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 claude/skills/interview/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
236 words · 1,427 chars · 1 section · 1 code block
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 12 days ago
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.