agents-repo--agents-repo-package-creation--package-submission-reviewer

Reviews drafted registry packages for description quality and produces a structured readiness verdict.

3|1|Updated May 2, 2026
One-click install
npx skills add https://github.com/agents-repo/registry --skill agents-repo-agents-repo-package-creation-package-submission-reviewer-agents-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agents-repo--agents-repo-package-creation--package-submission-reviewer
Source: https://github.com/agents-repo/registry/tree/main/.cursor/skills/agents-repo/agents-repo-package-creation/agents-repo--agents-repo-package-creation--package-submission-reviewer
Command: npx skills add https://github.com/agents-repo/registry --skill agents-repo-agents-repo-package-creation-package-submission-reviewer-agents-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafted agent and flow packages often contain unclear descriptions, overlapping agent roles, weak interaction contracts, or outdated URL paths that would confuse catalog readers and maintainers. This Skill performs a human-facing quality review of a drafted package and returns structured feedback with a clear submission readiness verdict. ## Core Features & Use Cases - Description and Naming Review: Evaluates package, agent, and flow descriptions for clarity, specificity, and distinguishable naming. - Contract and Flow Quality Checks: Assesses interaction contract inputs and outputs, flow step ordering, error handling coverage, and cost band consistency against registry ranges. - Readiness Verdict: Produces per-asset findings, prioritized revision requests for the package creator, and a verdict of ready, needs-revision, or needs-clarification. - Use Case: Before submitting a new multi-agent package to the registry, run this review to catch redundant agent responsibilities, legacy flat package paths in homepage URLs, and hand-edited versioned files that should be flagged. ## Quick Start Review the drafted package source files in this directory and produce a structured review report with a readiness verdict.

Frequently Asked Questions about agents-repo--agents-repo-package-creation--package-submission-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an agent package before submitting it to a registry?▼

Provide the full drafted package source tree, including metadata.json, the package README, agent definitions, and flow definitions. The review returns per-file findings, cross-cutting concerns, prioritized revision requests, and a readiness verdict.

What does the package submission reviewer check in agent definitions?▼

It checks description clarity and completeness, overlapping or redundant agent responsibilities, interaction contract input and output quality, flow step ordering, error handling coverage, and whether names are meaningful and distinguishable.

Does this review run structural validation or artifact integrity checks?▼

No. Deterministic registry rule checks and artifact gates are owned by script orchestration agents such as package-script-runner and package-release-gate. This review covers only human-facing quality and usability.

What readiness verdicts can the package review produce?▼

The review outputs one of three verdicts: ready if the package can be submitted, needs-revision if changes are required, or needs-clarification if the reviewer lacks enough information to evaluate.

What cost band values are valid in package metadata?▼

Bands must match estimatedCost ranges: minimal 1-2, low 3-4, moderate 5-6, high 7-8, critical 9-10. Package-level band mixed may pair with any optional aggregate estimatedCost.