Evaluation report

• Repository is reachable

  https://github.com/Nunchi-trade/agent-cli @ 58619a2 — ★ 521 · Python · MIT · last push 3 days ago

• Manifest detected

  kind=skill slug=pulse · path=skills/pulse · source=SKILL.md

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for skill/pulse

• Version is semver

  1.0.0

• Description qualitywarn

  10 words · 77 chars — skills use the description as their trigger; aim higher

  Aim for 15+ words and include trigger phrases like “use this skill when …”.

• Tags / topics declaredwarn

  No manifest tags and no GitHub repo topics

  Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.

• README is present and substantial

  30,878 chars · 14 sections · 30 code blocks

• README has usage / example sections

  found: Quick Start

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

• Skill: body content present

  664 words · 4,020 chars · 10 sections · 2 code blocks

• Skill: allowed-tools scope

  no allowed-tools restriction (Claude may use anything)

• 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 3 days ago

• Tests detected

  1 test directory · 112 test files

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