Evaluation report

• Repository is reachable

  https://github.com/zeroclaw-labs/zeroclaw @ bacda86 — ★ 32,229 · Rust · Apache-2.0 · last push today

• Manifest detected

  kind=skill slug=pr-architecture-check · path=.claude/skills/pr-architecture-check · source=SKILL.md

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for skill/pr-architecture-check

• Version is semver

  0.1.0

• Description quality

  37 words · 286 chars — "Advisory architecture review of a PR diff. Validates dependency direction, trait…"

• README is present and substantial

  12,140 chars · 10 sections · 6 code blocks

• Tags / topics declared

  8 total — agent, agentic, ai, infra, ml, openclaw (+2)

• README has usage / example sections

  found: Quick start

• Homepage / docs URL declared

  https://www.zeroclawlabs.ai/

• LICENSE file at repo rootwarn

  No LICENSE / LICENCE / COPYING / UNLICENSE file (.md/.txt/.rst variants) and no SPDX-License-Identifier header found in common source files

  Pick an SPDX license and add a LICENSE file at the repo root, or put an `SPDX-License-Identifier:` comment at the top of your main source file.

• 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 .claude/skills/pr-architecture-check/SKILL.md · frontmatter source: SKILL.md

• Skill: body content present

  811 words · 5,602 chars · 18 sections · 5 code blocks

• Skill: allowed-tools scope

  no allowed-tools restriction (Claude may use anything)

• Recent activity

  last push today

• Tests detected

  8 test directories · 1 test file

• CI configuration detected

  GitHub Actions (25 workflows)

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