api-development
PassAudited by ClawScan on May 10, 2026.
Overview
This instruction-only API workflow skill appears coherent, with noteworthy but purpose-aligned guidance around tool orchestration, deployment, and optional remote/global installation.
This looks reasonable for an API-development orchestration skill. Before using it on a real project, keep release and deployment steps user-approved, review generated code before applying it, and be cautious with the README’s external or global installation commands.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If used with powerful development or CI/CD tools, the agent could make code, release, or deployment changes as part of the workflow.
The skill intentionally orchestrates other skills/tools and includes release/deployment steps. That is aligned with the API lifecycle purpose, but deployment and release tagging can affect real systems if the agent has those tools.
`Follow these steps in order. Each step routes to the appropriate skill or tool` ... `tag the release, update changelogs, and deploy through the pipeline.`
Require explicit user confirmation before release tags, production deployments, migrations, or other irreversible actions; review diffs and target environments before applying changes.
Following the README install path could install a version from a remote source, and global installation makes it available to future agent sessions or projects.
The README provides user-directed installation commands from an external GitHub path and optional global skill-directory copies. This is expected installation documentation, but users should trust and review the source before using it.
`npx add https://github.com/wpank/ai/tree/main/skills/api/api-development` ... `cp -r ~/.ai-skills/skills/api/api-development ~/.cursor/skills/api-development`
Prefer the reviewed registry artifact when possible, or pin and review the external source before installing; use per-project installation unless global availability is needed.