Evaluation report

• Repository is reachable

  https://github.com/rorkai/app-store-connect-cli-skills @ 0886ecb — ★ 899 · MIT · last push yesterday

• Manifest detected

  kind=skill slug=asc-aso-audit · path=skills/asc-aso-audit · source=SKILL.md

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for skill/asc-aso-audit

• Version is semver

  0.1.0

• Description quality

  27 words · 170 chars — "Run an offline ASO audit on canonical App Store metadata under `./metadata` and …"

• README is present and substantial

  11,131 chars · 5 sections · 24 code blocks

• Tags / topics declared

  13 total — agent-skills, ai-skills, app-store-connect, apple, asc, automation (+7)

• README has usage / example sections

  found: Installation · Usage

• Homepage / docs URL declared

  https://asccli.sh

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

• Skill: body content present

  1,530 words · 10,186 chars · 22 sections · 8 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 yesterday

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