Evaluation report
Warningsskyll · skill6b20d0e· 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/assafelovic/skyll @ 6b20d0e — ★ 235 · Python · Apache-2.0 · last push 3 months ago
Manifest detected
kind=skill slug=skyll · path=.agents/skills/skyll · source=SKILL.md
Slug is URL-safe
"skyll" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/skyll
Version is semver
0.1.0
Documentation
5 passedDescription quality
42 words · 280 chars — "Search and retrieve agent skills at runtime. This skill should be used when the …"
README is present and substantial
9,235 chars · 10 sections · 13 code blocks
Tags / topics declared
3 total — claude-skill, mcp, skills
README has usage / example sections
found: Quick Start
Homepage / docs URL declared
https://skyll.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 .agents/skills/skyll/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
454 words · 3,373 chars · 11 sections · 5 code blocks
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Maintenance
2 passed1 warningCI 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.
Recent activity
last push 3 months ago
Tests detected
1 test directory · 4 test files
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.