Evaluation report

• Repository is reachable

  https://github.com/stephengpope/thepopebot @ 33f032d — ★ 1,845 · JavaScript · MIT · last push 8 weeks ago

• Manifest detected

  kind=skill slug=agent-job-background · path=templates/skills-library/agent-job-background · source=SKILL.md

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for skill/agent-job-background

• 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

  55 words · 312 chars — "Use to spawn or check on long-running background agent jobs (each launches a new…"

• README is present and substantial

  13,517 chars · 9 sections · 8 code blocks

• README has usage / example sections

  no labeled section but 8 code blocks document usage

• Homepage / docs URL declared

  https://skool.com/ai-architects

• 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 templates/skills-library/agent-job-background/SKILL.md · frontmatter source: SKILL.md

• Skill: body content present

  185 words · 1,363 chars · 4 sections · 1 code block

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

• Recent activity

  last push 8 weeks ago

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