Evaluation report

• Repository is reachable

  https://github.com/iamzifei/gtd-coach-plugin @ 7b515e2 — ★ 34 · MIT · last push 5 months ago

• Manifest detected

  kind=skill slug=gtd-coach · path=skills/gtd-coach · source=SKILL.md

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for skill/gtd-coach

• Version is semver

  0.1.0

• Description quality

  47 words · 352 chars — "Personal GTD (Getting Things Done) coach that helps users achieve their annual g…"

• README is present and substantial

  3,986 chars · 11 sections · 10 code blocks

• Tags / topics declared

  4 total — ai, claude, claude-code, claude-skill

• README has usage / example sections

  found: Installation · Usage · Example

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

• Skill: body content present

  1,594 words · 10,247 chars · 50 sections · 14 code blocks

• Skill: allowed-tools scope

  no allowed-tools restriction (Claude may use anything)

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

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