Evaluation report
Failingandroid-development · skilledfca5e· 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/dpconde/claude-android-skill @ edfca5e — ★ 259 · Python · MIT · last push 7 months ago
Manifest detected
kind=skill slug=android-development · source=SKILL.md
Slug is URL-safe
"android-development" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/android-development
Version is semver
0.1.0
Documentation
5 passedDescription quality
51 words · 429 chars — "Create production-quality Android applications following Google's official archi…"
README is present and substantial
7,052 chars · 13 sections · 7 code blocks
Tags / topics declared
5 total — android, claude-code, claude-skill, mcp, now-in-android
README has usage / example sections
found: Installation · Usage
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
683 words · 6,324 chars · 13 sections · 7 code blocks
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Maintenance
3 warningsRecent activitywarn
last push 7 months ago — looks slowing down
Consumers prefer artifacts that are actively maintained (threshold: 90 days, configurable via EVAL_RECENCY_PASS_DAYS).
Tests 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.