Evaluation report
Failingplaywright-pom · skilld3be9ca· 3 months ago
Every check MetaHub ran on this artifact, grouped by area. Static checks run on the source at publish time; behavioral checks run the artifact in a sandbox and judge what it actually does.
Structural
5 passedRepository is reachable
https://github.com/testdino-hq/playwright-skill @ d3be9ca — ★ 311 · MIT · last push 8 days ago
Manifest detected
kind=skill slug=playwright-pom · path=pom · source=SKILL.md
Slug is URL-safe
"playwright-pom" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/playwright-pom
Version is semver
0.1.0
Documentation
5 passedDescription quality
25 words · 138 chars — "Page Object Model patterns for Playwright — when to use POM, how to structure pa…"
README is present and substantial
12,105 chars · 9 sections · 3 code blocks
Tags / topics declared
13 total — ai, ai-skills, antigravity-skills, claude-skills, codex-skills, cursor-skills (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://www.testdino.com
Safety
2 passedLICENSE file at repo root
LICENSE
No sensitive files in the repo
scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found
Kind-specific
2 passed2 warningsSkill: body content presentwarn
Body is short (66 words · 482 chars) — Claude has little to go on
Add concrete usage steps, example invocations, and any reference links. (≥3 code blocks lifts a short body to pass.)
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 pom/SKILL.md · frontmatter source: SKILL.md
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Maintenance
1 passed2 warningsTests 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.
Recent activity
last push 8 days ago