api-development
v1.0.0Meta-skill that orchestrates the full API development lifecycle — from design through documentation — by coordinating specialized skills, agents, and commands into a seamless build workflow.
⭐ 1· 939·1 current·1 all-time
by@wpank
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (API development orchestration) matches the SKILL.md: it coordinates design → spec → scaffold → implement → test → document → deploy and routes to specialized skills (e.g., api-design, api-versioning). It does not request unrelated binaries, env vars, or config paths.
Instruction Scope
The instructions are focused on API lifecycle tasks and explicitly route work to other skills and files (e.g., api-design/assets/openapi-template.yaml). Steps like 'deploy through the pipeline' are high-level and will rely on other skills or the agent's environment — this is expected for a meta-skill but leaves room for the agent to access deployment credentials or CI/CD tooling when invoked.
Install Mechanism
No install spec and no code files are included (instruction-only). That minimizes on-disk execution risk; README suggests using npx or manual copy, but those are optional instructions and not enforced by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. However, because it orchestrates other skills (which may require secrets like cloud or CI tokens), users should verify the downstream skills' requirements before granting access.
Persistence & Privilege
always is false and there is no indication the skill writes to global agent configs or requests permanent presence. It does not request elevated privileges on its own.
Assessment
This skill itself is an instruction-only meta-skill and appears coherent with its purpose. Before installing or enabling it for autonomous use: 1) Verify the skill’s provenance (source/homepage is unknown here) and confirm the publisher is trusted. 2) Inspect the referenced skills (api-design, api-versioning, deploy-related skills) because those will perform actions that may require credentials or network access. 3) When you run orchestration steps that deploy or access CI/CD, supply the minimal credentials (least privilege) and prefer ephemeral or scoped tokens. 4) If you need stronger assurance, ask for a version with explicit provenance (official repo/maintainer link) or review the concrete implementation of the downstream skills that this meta-skill will invoke.Like a lobster shell, security has layers — review code before you run it.
latestvk976yb50pjb3tsyees4zv5sejd80wm84
License
MIT-0
Free to use, modify, and redistribute. No attribution required.