Evaluation report

• Repository is reachable

  https://github.com/gradusnikov/eclipse-chatgpt-plugin @ 170d9bc — ★ 158 · Java · MIT · last push 12 days ago

• Manifest detected

  kind=skill slug=eclipse-edit · path=.claude/skills/eclipse-edit · source=SKILL.md

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for skill/eclipse-edit

• Version is semver

  0.1.0

• Description quality

  33 words · 213 chars — "Edit files in Eclipse projects using MCP tools. Use this when modifying code in …"

• README is present and substantial

  22,317 chars · 7 sections · 2 code blocks

• Tags / topics declared

  6 total — eclipse, eclipse-plugin, mcp, mcp-client, mcp-server, plugin

• README has usage / example sections

  found: Getting Started · 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

• 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/eclipse-edit/SKILL.md · frontmatter source: SKILL.md

• Skill: body content present

  393 words · 2,854 chars · 4 sections

• Skill: allowed-tools scope

  24 declared: mcp__eclipse-coder__applyPatch, mcp__eclipse-coder__replaceString, mcp__eclipse-coder__insertIntoFile, mcp__eclipse-coder__createFile, mcp__eclipse-coder__deleteFile (+19)

• 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 (1 workflows)

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