Evaluation report
Warningskirby-project-tour · skill3474420· 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/bnomei/kirby-mcp @ 3474420 — ★ 56 · PHP · MIT · last push 11 days ago
Manifest detected
kind=skill slug=kirby-project-tour · path=skills/kirby-project-tour · source=SKILL.md
Slug is URL-safe
"kirby-project-tour" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/kirby-project-tour
Version is semver
0.1.0
Documentation
5 passedDescription quality
38 words · 269 chars — "Maps a Kirby project using Kirby MCP tools/resources, including roots, templates…"
README is present and substantial
49,083 chars · 16 sections · 39 code blocks
Tags / topics declared
17 total — agent-tools, agentic-workflow, claude-code, cli, codex-cli, commands (+11)
README has usage / example sections
found: Quickstart
Homepage / docs URL declared
https://forum.getkirby.com/t/kirby-mcp-inspect-blueprints-templates-plugins-interact-with-a-real-kirby-runtime-and-use-a-bundled-knowledge-base/35106
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 skills/kirby-project-tour/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
288 words · 2,498 chars · 8 sections
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Maintenance
3 passedRecent activity
last push 11 days ago
Tests detected
1 test directory
CI configuration detected
GitHub Actions (4 workflows)
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.