Evaluation report

• Repository is reachable

  https://github.com/smerchek/claude-epub-skill @ 7c07230 — ★ 137 · Python · MIT · last push 9 months ago

• Manifest detected

  kind=skill slug=markdown-to-epub-converter · path=markdown-to-epub · source=SKILL.md

• Slug is URL-safe

  "markdown-to-epub-converter" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for skill/markdown-to-epub-converter

• Version is semver

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

  22 words · 131 chars — "Convert markdown documents and chat summaries into formatted EPUB ebook files th…"

• README is present and substantial

  6,938 chars · 18 sections · 6 code blocks

• README has usage / example sections

  found: Installation · Usage

• 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 markdown-to-epub/SKILL.md · frontmatter source: SKILL.md

• Skill: body content present

  997 words · 6,405 chars · 26 sections · 2 code blocks

• Skill: allowed-tools scope

  no allowed-tools restriction (Claude may use anything)

• Recent activitywarn

  last push 9 months ago — looks slowing down

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

• Tests detected

  1 test file

• CI configuration detected

  GitHub Actions (1 workflows)

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