Evaluation report

• Repository is reachable

  https://github.com/dzcmemory-web/bazi-ziwei-skill @ 8fd7dfa — ★ 450 · TypeScript · MIT · last push 7 days ago

• Manifest detected

  kind=skill slug=bazi-ziwei · source=SKILL.md

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for skill/bazi-ziwei

• Version is semver

  0.1.0

• Description quality

  109 words · 146 chars — "八字 + 紫微斗数 AI 排盘与综合分析。当用户提供生辰（阳历/农历日期、时辰、性别）询问八字、紫微、命理、命盘、流年大运相关问题时使用。基于 Yiqi 算法库…"

• README is present and substantial

  4,783 chars · 10 sections · 6 code blocks

• Tags / topics declared

  10 total — ai-agent, bazi, bazi-suanming, chinese-astrology, claude-skill, fortune-telling (+4)

• README has usage / example sections

  no labeled section but 6 code blocks document usage

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

• Skill: body content present

  2,494 words · 5,398 chars · 15 sections · 5 code blocks

• Skill: allowed-tools scope

  no allowed-tools restriction (Claude may use anything)

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

• Recent activity

  last push 7 days ago

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