Evaluation report

• Repository is reachable

  https://github.com/vibe-with-me-tools/agent-reachout @ a4fdd86 — ★ 48 · TypeScript · MIT · last push 3 months ago

• Manifest detected

  kind=plugin slug=agent-reachout · source=.claude-plugin/plugin.json

• Slug is URL-safe

  "agent-reachout" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for plugin/agent-reachout

• Version is semver

  1.0.3

• Description qualitywarn

  Only 6 words · 50 chars — more detail helps discovery

  Tell consumers what this artifact does in a full sentence.

• README is present and substantial

  5,766 chars · 11 sections · 5 code blocks

• Tags / topics declared

  10 total — agentic-ai, claude-code, claude-code-plugin, llm, mcp, messaging (+4)

• README has usage / example sections

  found: Installation

• Homepage / docs URL declared

  no homepage declared (registry will use the repo URL) — info-only, not blocking

• 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

  1 skill

• Plugin: bundle shape

  1 skill

• Plugin: manifest location

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

• Recent activitywarn

  last push 3 months ago — looks slowing down

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

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

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.