Install
$ agentstack add skill-the-alien-club-claude-workflows-review-playbook ✓ 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 No
- ✓ 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.
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
Review Against Playbook
This skill spawns the playbook-reviewer agent with a target and a playbook path. The agent does all the reading — rules and diff — on its own. Your job here is only to resolve the target and locate the correct playbook.
Step 1 — Resolve the Target
Argument forms:
- No argument → current branch vs
dev(fall back tomain) !1234or1234(numeric) → GitLab MR number- 7–40 hex chars → commit SHA
- A branch name → that branch vs
dev
Step 2 — Find the Playbook
find . -type d -name playbook | grep -v node_modules | grep -v .git
If only one playbook exists, use it.
If multiple, determine which repo the target touches:
- Commit:
git show [sha] --name-only - Branch/MR:
git diff dev...[branch] --name-only
Match changed paths to the correct repo subdirectory and pick its playbook.
If no playbook found: stop and report: > No playbook found. Run /add_playbook_rule to create rules first.
Step 3 — Spawn the Reviewer
Call Agent with subagent_type: "playbook-reviewer" and a prompt that contains only:
- The target identifier (commit SHA, branch range, or MR number)
- The absolute path to the playbook directory
- The working directory (so git commands resolve correctly)
Example prompt:
Review target: git diff dev...feature/my-branch
Playbook: /home/xqua/Documents/Work/Alien/DataStreaming/datastreaming-demos/lds-chatbot/playbook
Working directory: /home/xqua/Documents/Work/Alien/DataStreaming/datastreaming-demos/lds-chatbot
Step 4 — Relay Output
Print the agent's output verbatim. Do not editorialize, soften, or add context.
Append this footer:
---
Playbook : [path]
Target : [resolved target]
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: the-alien-club
- Source: the-alien-club/claude-workflows
- 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.