Evaluation report
Warningsbuilding-blog · plugin1f5e1db· 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/BuildShipGrowRepeat/nextjs-sanity-blog-skill @ 1f5e1db — ★ 5 · MIT · last push 7 weeks ago
Manifest detected
kind=plugin slug=building-blog · source=.claude-plugin/plugin.json
Slug is URL-safe
"building-blog" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for plugin/building-blog
Version is semver
0.1.0
Documentation
5 passedDescription quality
54 words · 356 chars — "Opinionated, batteries-included spec for adding an SEO-first, i18n-ready blog to…"
README is present and substantial
6,367 chars · 11 sections · 2 code blocks
Tags / topics declared
18 total — ai-blog, blog, blogposting, claude-code, claude-plugin, claude-skills (+12)
README has usage / example sections
found: How to use
Homepage / docs URL declared
https://github.com/BuildShipGrowRepeat/nextjs-sanity-blog-skill
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
4 passedPlugin: manifest fields complete
Plugin: bundled artifacts present
1 skill
Plugin: bundle shape
1 skill
Plugin: manifest location
manifest at .claude-plugin/plugin.json (modern convention)
Maintenance
1 passed2 warningsTests detectedwarn
no test/tests/__tests__/spec/t/ dirs, no JVM src/test/, and no JS/TS/Python/Go/Ruby/Elixir test files
Add tests (even a smoke test). Consumers gauge maintenance quality by their presence.
CI 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 7 weeks ago
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.