Evaluation report
Failingtextum · skillbdf8746· 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/snakeying/Textum @ bdf8746 — ★ 40 · Python · MIT · last push 5 months ago
Manifest detected
kind=skill slug=textum · path=.claude/skills/textum · source=SKILL.md
Slug is URL-safe
"textum" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/textum
Version is semver
0.1.0
Documentation
3 passed2 warningsDescription qualitywarn
11 words · 84 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README has usage / example sectionswarn
README has no Usage / Example / Quick start / Installation heading at any level
Add a `# Usage`, `## Quick start`, or similar section so end users can copy/paste a working invocation. Code blocks alone work too if there are several.
README is present and substantial
6,524 chars · 8 sections · 2 code blocks
Tags / topics declared
6 total — claude-code, claude-skill, codex, codex-skill, skills, vibe-coding
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/textum/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
510 words · 2,509 chars
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
2 test directories · 10 test files