Evaluation report

• Repository is reachable

  https://github.com/jasonkneen/kiro @ 22577b6 — ★ 684 · TypeScript · MIT · last push 5 months ago

• Manifest detected

  kind=plugin slug=kiro-spec-driven · source=.claude-plugin/plugin.json

• Slug is URL-safe

  "kiro-spec-driven" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for plugin/kiro-spec-driven

• Version is semver

  1.0.0

• Tags / topics declaredwarn

  No manifest tags and no GitHub repo topics

  Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.

• Description quality

  24 words · 215 chars — "Spec-driven development methodology for Claude Code. Provides skills for require…"

• README is present and substantial

  11,177 chars · 8 sections · 5 code blocks

• README has usage / example sections

  found: Quick Start · Quick Start · Installation

• Homepage / docs URL declared

  https://github.com/jasonkneen/kiro

• LICENSE file at repo root

  LICENSE

• No sensitive files in the repo

  scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found

• Plugin: manifest fields complete

• Plugin: bundled artifacts present

  8 skills

• Plugin: bundle shape

  8 skills · 2 commands

• Plugin: manifest location

  manifest at .claude-plugin/plugin.json (modern convention)

• Recent activitywarn

  last push 5 months ago — looks slowing down

  Consumers prefer artifacts that are actively maintained (threshold: 90 days, configurable via EVAL_RECENCY_PASS_DAYS).

• 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.

• Tests detected

  1 test directory · 1 test file

Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.