Evaluation report

• Repository is reachable

  https://github.com/lee-fuhr/claude-session-index @ ad2f2b2 — ★ 25 · Python · MIT · last push 3 months ago

• Manifest detected

  kind=skill slug=session-index · path=skills/session-index · source=SKILL.md

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for skill/session-index

• Version is semver

  0.3.1

• Description quality

  23 words · 136 chars — "Search, analyze, and synthesize across all your Claude Code sessions. Ask "what …"

• README is present and substantial

  10,147 chars · 9 sections · 10 code blocks

• Tags / topics declared

  16 total — agent-skills, ai, analytics, claude, claude-code, claude-code-skill (+10)

• README has usage / example sections

  found: 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 skills/session-index/SKILL.md · frontmatter source: SKILL.md

• Skill: body content present

  437 words · 3,034 chars · 7 sections · 5 code blocks

• Skill: allowed-tools scope

  no allowed-tools restriction (Claude may use anything)

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

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