Evaluation report

• Repository is reachable

  https://github.com/huifer/WellAlly-health @ 27c2603 — ★ 895 · Shell · MIT · last push 6 months ago

• Manifest detected

  kind=skill slug=emergency-card · path=.claude/skills/emergency-card · source=SKILL.md

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for skill/emergency-card

• Version is semver

  0.1.0

• Description quality

  93 words · 120 chars — "生成紧急情况下快速访问的医疗信息摘要卡片。当用户需要旅行、就诊准备、紧急情况或询问"紧急信息"、"医疗卡片"、"急救信息"时使用此技能。提取关键信息（过敏、用药…"

• README is present and substantial

  9,400 chars · 11 sections · 2 code blocks

• Tags / topics declared

  4 total — claude, claude-code, health, health-data

• README has usage / example sections

  found: Quick Start

• Homepage / docs URL declared

  https://www.wellally.tech/

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

• Skill: body content present

  2,525 words · 10,684 chars · 41 sections · 14 code blocks

• Skill: allowed-tools scope

  no allowed-tools restriction (Claude may use anything)

• Recent activitywarn

  last push 6 months ago — looks slowing down

  Consumers prefer artifacts that are actively maintained (threshold: 90 days, configurable via EVAL_RECENCY_PASS_DAYS).

• 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.

• 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.

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