Evaluation report
Warningsswift-concurrency · skill0d472de· 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/AvdLee/Swift-Concurrency-Agent-Skill @ 0d472de — ★ 1,556 · MIT · last push 3 weeks ago
Manifest detected
kind=skill slug=swift-concurrency · path=swift-concurrency · source=SKILL.md
Slug is URL-safe
"swift-concurrency" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for skill/swift-concurrency
Version is semver
0.1.0
Documentation
5 passedDescription quality
31 words · 242 chars — "Diagnose Swift Concurrency issues, refactor callback-based code to async/await, …"
README is present and substantial
9,114 chars · 10 sections · 4 code blocks
Tags / topics declared
5 total — agent-skills, async-await, swift, swift-actor, swift-concurrency
README has usage / example sections
found: How to Use
Homepage / docs URL declared
https://www.swiftconcurrencycourse.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
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 swift-concurrency/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
1,698 words · 12,181 chars · 12 sections · 3 code blocks
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Maintenance
2 passed1 warningTests 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 3 weeks ago
CI configuration detected
GitHub Actions (2 workflows)
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.