Evaluation report
Warningsjava-checkstyle · mcp2918561· 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/open-metadata/OpenMetadata @ 2918561 — ★ 14,240 · TypeScript · Apache-2.0 · last push today
Manifest detected
kind=skill slug=java-checkstyle · path=.agents/skills/java-checkstyle · source=SKILL.md
Slug is URL-safe
"java-checkstyle" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/java-checkstyle
Version is semver
0.1.0
Documentation
5 passedDescription quality
38 words · 229 chars — "Run `mvn spotless:apply` to fix Java checkstyle / formatting failures and verify…"
README is present and substantial
19,444 chars · 15 sections · 2 code blocks
Tags / topics declared
20 total — context, context-layer, data-catalog, data-collaboration, data-contracts, data-discovery (+14)
README has usage / example sections
found: Quickstart
Homepage / docs URL declared
https://open-metadata.org
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/java-checkstyle/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
310 words · 1,977 chars · 3 sections
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Maintenance
3 passedRecent activity
last push today
Tests detected
12 test directories · 2057 test files
CI configuration detected
GitHub Actions (57 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.