devrel-tooling

Build developer CLIs and API collections. Use when adding commands, completions, or generating a Postman collection from routes. It does not design the SDK API (that's `sdk-craft`).

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with clear workflows, concrete examples, and disciplined progressive disclosure to real reference files. The main slack is light duplication between Constraints, Phase gates, and the Quality checklist, and a few high-level early workflow steps.

Suggestions

Collapse the Quality checklist into the Constraints/Phase-gates sections (or vice versa) to remove the duplicated must-do/must-not items and save tokens.

Tighten the early CLI workflow steps ("Analyze UX", "Design commands") with a concrete artifact or inline check, or move detail to cli-patterns.md, so they are actionable rather than advisory.

Trim the conversational "Did this help?" section to a one-line issue-filing pointer; the question prompt adds little actionable guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding about what a CLI or Postman is — but the Quality checklist partially reiterates the Constraints and Phase gates, and the conversational "Did this help?" prose could be trimmed.	4 / 5
Actionability	Provides executable content — a complete commander example, a concrete command-hierarchy tree, a Postman v2.1 JSON template, and validation commands — but Python/Go framework examples are deferred to references and the workflow's early steps ("Analyze UX", "Design commands") stay high-level.	4 / 5
Workflow Clarity	Numbered core workflows (CLI 1–5, API 1–6) plus a Phase gates section with concrete validation checkpoints ("mytool --help", "npx ajv validate", completion sourcing) give a clear sequence; validation lives in a separate section rather than inline within each workflow step, a minor gap.	4 / 5
Progressive Disclosure	The body is an overview that points to two clearly signaled, one-level-deep reference files — `references/cli-patterns.md` and `references/api-collection-generators.md` (both present in the bundle) — via blockquote callouts, matching the top anchor for clean navigation.	5 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description that covers what and when with concrete triggers and an explicit boundary against a sibling skill. Minor room to add synonyms (OpenAPI) and tighten the generic "API collections" phrasing.

Dimension	Reasoning	Score
Specificity	"Build developer CLIs and API collections" names the domains and pairs them with concrete actions like "adding commands, completions, or generating a Postman collection from routes" — multiple specific actions, though "API collections" stays slightly generic versus the more specific Postman route generation.	4 / 5
Completeness	It explicitly answers what ("Build developer CLIs and API collections") and when ("Use when adding commands, completions, or generating a Postman collection from routes") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural terms users would say appear — "commands", "completions", "Postman collection", "routes", "CLI" — giving good coverage, but synonyms like OpenAPI and file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (developer CLIs and API collections) and adds an explicit boundary clause — "It does not design the SDK API (that's `sdk-craft`)" — minimizing conflict with adjacent skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: saif-shines/devex-kit
Path: plugins/tooling/skills/devrel-tooling/SKILL.md
Commit: df60de1

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.