Jarvis Api Contract Guard 01
v1.0.0Design and verify API contracts for backward compatibility. Use when handling development work that needs repeatable steps, quality gates, and practical outp...
⭐ 0· 615·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (API contract design and verification) match the SKILL.md content: a playbook, quality gates, and output format. The skill requests no binaries, env vars, or config paths, which is proportionate for a planning/checklist skill.
Instruction Scope
The instructions are high-level and focused on planning, checkpoints, evidence collection, and producing implementation-ready outputs. They do not direct the agent to read system files, access credentials, or transmit data externally. One ambiguity: steps like 'Execute in checkpoints' and 'Exact checklist or commands where useful' could be interpreted by an agent as permission to run tests/commands if the agent has other capabilities; the SKILL.md itself does not provide or require such capabilities.
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is written to disk and no external packages are requested.
Credentials
The skill declares no environment variables, credentials, or config paths. There is no unexplained request for secrets or access to unrelated services.
Persistence & Privilege
The skill does not request persistent presence (always:false) and uses default invocation settings. It does not modify other skills or system-wide settings.
Assessment
This skill is a reusable checklist/playbook for API contract work and appears internally consistent. It will not install software or ask for credentials. Keep in mind: (1) it is purely advisory — it won't run tests or change systems by itself; if you ask the agent to actually execute commands or integrate with CI/CD, ensure those actions are gated and do not expose secrets; (2) the instructions are intentionally high-level, so confirm any concrete test commands or scripts before running them in your environment; (3) if you need the skill to perform automated verifies, prefer pairing it with well-scoped, trusted tools and explicit environment variables rather than handing over broad access.Like a lobster shell, security has layers — review code before you run it.
latestvk9790tcypfvhhvhc251rt5556s81b42j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.