Evaluation report
Warningsgithub · skill85dcfcc· 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/sipeed/picoclaw @ 85dcfcc — ★ 29,710 · Go · MIT · last push yesterday
Manifest detected
kind=skill slug=github · path=workspace/skills/github · source=SKILL.md
Slug is URL-safe
"github" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/github
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
25 words · 136 chars — "Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and …"
README is present and substantial
31,627 chars · 14 sections · 14 code blocks
README has usage / example sections
no labeled section but 14 code blocks document usage
Homepage / docs URL declared
https://picoclaw.io
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 workspace/skills/github/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
149 words · 938 chars · 3 sections · 6 code blocks
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Maintenance
3 passedRecent activity
last push yesterday
Tests detected
327 test files
CI configuration detected
GitHub Actions (9 workflows)
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.