Evaluation report

• Repository is reachable

  https://github.com/stevembarclay/pencilplaybook @ b732429 — ★ 28 · Python · MIT · last push 3 months ago

• Manifest detected

  kind=skill slug=pencilplaybook · source=SKILL.md

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for skill/pencilplaybook

• Version is semver

  1.1.0

• Description quality

  32 words · 211 chars — "PencilPlaybook is the UI Skills / Taste-Skill for Pencil.dev + Claude Code — a d…"

• README is present and substantial

  11,463 chars · 11 sections · 9 code blocks

• Tags / topics declared

  10 total — ai-design, anti-ai-slop, claude-code, claude-skill, design-skill, design-system (+4)

• README has usage / example sections

  found: Quick Start · 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 SKILL.md · frontmatter source: SKILL.md

• Skill: body content present

  2,903 words · 25,586 chars · 32 sections · 21 code blocks

• Skill: allowed-tools scope

  no allowed-tools restriction (Claude may use anything)

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

• Recent activity

  last push 3 months ago

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