Evaluation report

• Repository is reachable

  https://github.com/mhattingpete/claude-skills-marketplace @ 3fa16a9 — ★ 646 · HTML · Apache-2.0 · last push 4 months ago

• Manifest detected

  kind=mcp slug=claude-marketplace-execution-runtime · path=execution-runtime · source=pyproject.toml

• Slug is URL-safe

  "claude-marketplace-execution-runtime" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for mcp/claude-marketplace-execution-runtime

• Version is semver

  2.0.0

• Description quality

  16 words · 112 chars — "Code execution environment for Claude Code - implements Anthropic code execution…"

• README is present and substantial

  19,481 chars · 17 sections · 7 code blocks

• Tags / topics declared

  9 total — ai-agents, ai-tools, anthropic, automation, claude-code, claude-skills (+3)

• README has usage / example sections

  found: Installation

• 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

• MCP: launch path

  launch declared in pyproject.toml

• MCP: @modelcontextprotocol/sdk in dependencies

  non-Node server (pyproject.toml) — uses its language's MCP SDK

• MCP: ESM package

  non-Node server (pyproject.toml) — n/a

• MCP: server surface

  0 tools

• Recent activitywarn

  last push 4 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.

This artifact hasn't produced behavioral results yet: the evaluation sandbox couldn't run it (it may need credentials we don't provide, or a build our environment doesn't support). That's a limitation of our environment, not a verdict on the artifact.