Evaluation report

• Repository is reachable

  https://github.com/SkillBoss-AI/skillboss-skills @ 5e3dc20 — ★ 54 · TypeScript · Apache-2.0 · last push 12 days ago

• Manifest detected

  kind=mcp slug=skillboss-mcp-server · path=mcp-server · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/skillboss-mcp-server

• Version is semver

  1.0.1

• Description quality

  14 words · 84 chars — OK but more detail helps

• README is present and substantial

  4,405 chars · 6 sections · 4 code blocks

• Tags / topics declared

  19 total — mcp, model-context-protocol, ai, claude, gpt, gemini (+13)

• README has usage / example sections

  no labeled section but 4 code blocks document usage

• Homepage / docs URL declared

  https://skillboss.co/docs/integrations/mcp-server

• Dependencies: known vulnerabilitieswarn

  2 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) · @modelcontextprotocol/[email protected] (HIGH: GHSA-w48q-cv73-mx4w)

  Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)

• 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

  bin: skillboss-mcp

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.0.4"

• MCP: SDK version pinned

  pinned at "^1.0.4"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• 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 12 days ago

• CI configuration detected

  GitHub Actions (3 workflows)

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.