skill-ao92265-claude-code-playbook-deploy · by Install
$ agentstack add skill-ao92265-claude-code-playbook-deploy ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ao92265-claude-code-playbook-deploy) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Deploy Workflow
Safe deployment checklist. Runs pre-deploy verification before any deployment action.
Steps
- Verify git credentials:
gh auth status— if failing, STOP and report - Run build with OOM prevention:
NODE_OPTIONS='--max-old-space-size=4096' npm run build— if OOM occurs, retry with 8192 - Run tests with
npm test— if any fail, stop and report - Check for port conflicts on the target port
- Verify required environment variables are set (check .env exists, don't expose values)
- Check git status — warn if there are uncommitted changes
- Show a summary of what will be deployed (current branch, latest commit, build status)
- STOP and ask for explicit confirmation before proceeding with any deployment action
Important
- Do NOT push, deploy, or run any deployment commands without explicit user confirmation
- Do NOT proceed past a failed build or test step
- If deploying to Azure, verify the tier supports the required features first
- Always show what branch and commit will be deployed before asking for confirmation
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ao92265
- Source: ao92265/claude-code-playbook
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.