Evaluation report
Warningsblender-to-unity · mcp484937c· 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/CoplayDev/unity-mcp @ 484937c — ★ 12,201 · C# · MIT · last push yesterday
Manifest detected
kind=skill slug=blender-to-unity · path=.claude/skills/blender-to-unity · source=SKILL.md
Slug is URL-safe
"blender-to-unity" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/blender-to-unity
Version is semver
0.1.0
Documentation
5 passedDescription quality
66 words · 384 chars — "Hand off a model from Blender (via BlenderMCP) into Unity (via MCP for Unity) — …"
README is present and substantial
5,215 chars · 9 sections · 1 code block
Tags / topics declared
16 total — ai, ai-integration, anthropic, claude, copilot, cursor (+10)
README has usage / example sections
found: Quickstart
Homepage / docs URL declared
https://coplaydev.github.io/unity-mcp/
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/blender-to-unity/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
550 words · 4,110 chars · 3 sections
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Maintenance
3 passedRecent activity
last push yesterday
Tests detected
2 test directories · 89 test files
CI configuration detected
GitHub Actions (11 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.