Evaluation report

• Repository is reachable

  https://github.com/echoVic/spec-flow @ 3ae2516 — ★ 32 · Shell · MIT · last push 4 months ago

• Manifest detected

  kind=skill slug=spec-flow · source=SKILL.md

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for skill/spec-flow

• Version is semver

  0.1.0

• Description quality

  79 words · 421 chars — "Spec-driven development workflow. Interactive phase-by-phase confirmation from p…"

• README is present and substantial

  4,132 chars · 9 sections · 5 code blocks

• Tags / topics declared

  11 total — ai-skill, claude, claude-code, claude-code-skills, claude-skill, development-workflow (+5)

• README has usage / example sections

  found: Installation · Quick Start

• 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

• Skill: 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 SKILL.md · frontmatter source: SKILL.md

• Skill: body content present

  973 words · 4,142 chars · 10 sections · 1 code block

• Skill: allowed-tools scope

  no allowed-tools restriction (Claude may use anything)

• Recent activitywarn

  last push 4 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.

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