Api

v1.0.0

Backups, RPO/RTO, restores, and drills. Use when designing DR or testing restores.

0· 110·0 current·0 all-time
byClawKK@codekungfu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The SKILL.md describes a Backup Recovery/DR planning workflow and the declared requirements (no env vars, no binaries, instruction-only) match that purpose. However, the registry metadata shows the top-level Name as 'Api' while the skill slug and SKILL.md use 'backup-recovery' — a metadata/name mismatch worth confirming with the publisher.
Instruction Scope
Runtime instructions are purely advisory: ask about RPO/RTO, propose staged workflows, request user-provided context, and produce checklists and runbooks. The instructions do not ask the agent to read files, access credentials, call external endpoints, or perform actions outside the user's control.
Install Mechanism
No install spec and no code files — instruction-only. This is low-risk because nothing is written to disk or fetched during installation.
Credentials
The skill declares no required environment variables, credentials, or config paths. The SKILL.md asks the user for contextual information (environment, scale, deadlines) which is appropriate and not the same as requesting secrets or system access.
Persistence & Privilege
always is false and the skill does not request persistent presence or modify agent/system configuration. It can be invoked by the model (default), which is normal for skills and acceptable here given the limited scope and lack of credentials.
Assessment
This skill is instruction-only and matches its stated purpose, so technical risk is low. Before installing: (1) verify the publisher/owner and resolve the metadata mismatch (top-level Name 'Api' vs SKILL.md 'backup-recovery'); (2) prefer skills with a homepage or source repo when possible; (3) because it can be invoked by the agent, confirm you trust the owner or test in a restricted environment first; (4) no secrets are requested by the skill, but never paste credentials into chat — the skill will ask only for contextual info like RPO/RTO, scale, or deadlines. If the name mismatch or unknown owner concerns you, ask the publisher for clarification or choose a skill with clearer provenance.

Like a lobster shell, security has layers — review code before you run it.

latestvk972x31hypqwmfbzpvc8b0ym0583hw30

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments