Evaluation report
Warningsinvestigate-issue · skill65f33df· 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/maximhq/bifrost @ 65f33df — ★ 6,426 · Go · Apache-2.0 · last push today
Manifest detected
kind=skill slug=investigate-issue · path=.claude/skills/investigate-issue · source=SKILL.md
Slug is URL-safe
"investigate-issue" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/investigate-issue
Version is semver
0.1.0
Documentation
5 passedDescription quality
44 words · 331 chars — "Investigate a GitHub issue by fetching details, analyzing the codebase, research…"
README is present and substantial
13,097 chars · 11 sections · 7 code blocks
Tags / topics declared
16 total — ai-gateway, gateway, gateway-services, generative-ai, guardrails, llm (+10)
README has usage / example sections
found: Quick Start · Getting Started · Quick Start
Homepage / docs URL declared
https://www.getmaxim.ai/bifrost
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
3 passed1 warningSkill: 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/investigate-issue/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
3,150 words · 22,614 chars · 56 sections · 30 code blocks
Skill: allowed-tools scope
13 declared: Read, Grep, Glob, Bash, WebSearch (+8)
Maintenance
3 passedRecent activity
last push today
Tests detected
4 test directories · 484 test files
CI configuration detected
GitHub Actions (14 workflows)
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.