Evaluation report
Warningsgithub-workflow · plugincbc95ae· 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/fvadicamo/dev-agent-skills @ cbc95ae — ★ 71 · Shell · MIT · last push 3 weeks ago
Manifest detected
kind=plugin slug=github-workflow · path=plugins/github-workflow/.claude-plugin · source=plugin.json
Slug is URL-safe
"github-workflow" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for plugin/github-workflow
Version is semver
1.4.2
Documentation
5 passedDescription quality
11 words · 80 chars — OK but more detail helps
README is present and substantial
9,460 chars · 8 sections · 3 code blocks
Tags / topics declared
10 total — ai-coding-agent, anthropic, claude-code, claude-code-plugin, claude-code-skills, conventional-commits (+4)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
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 warningPlugin: bundled artifacts presentwarn
Couldn't find a skills/ subdir or an MCP server config inside the plugin
A plugin is most useful when it bundles ≥ 1 skill or an MCP server.
Plugin: manifest fields complete
Plugin: bundle shape
empty bundle
Plugin: manifest location
manifest at plugin.json
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 weeks ago
Tests detected
1 test directory
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.