Evaluation report
Warningsbackport-commit · mcp5775e94· 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/penpot/penpot @ 5775e94 — ★ 52,061 · Clojure · MPL-2.0 · last push 2 days ago
Manifest detected
kind=skill slug=backport-commit · path=.opencode/skills/backport-commit · source=SKILL.md
Slug is URL-safe
"backport-commit" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/backport-commit
Version is semver
0.1.0
Documentation
5 passedDescription quality
24 words · 156 chars — "Port changes from a specific Git commit to the current branch by manually applyi…"
README is present and substantial
11,066 chars · 6 sections · 1 code block
Tags / topics declared
7 total — clojure, clojurescript, design, prototyping, ui, ux-design (+1)
README has usage / example sections
found: Getting started
Homepage / docs URL declared
https://penpot.app
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 .opencode/skills/backport-commit/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
479 words · 2,978 chars · 9 sections · 1 code block
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Maintenance
3 passedRecent activity
last push 2 days ago
Tests detected
2 test directories · 91 test files
CI configuration detected
GitHub Actions (20 workflows)
Behavioral
This artifact hasn't produced behavioral results yet: the evaluation sandbox couldn't run it (it may need credentials we don't provide, or a build our environment doesn't support). That's a limitation of our environment, not a verdict on the artifact.