Install
$ agentstack add skill-ao92265-claude-code-playbook-draft-reply ✓ 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
Draft Reply
Prevents the recurring "first draft too technical, needs tone rework" friction.
Pre-Write Checklist (ASK IF UNSPECIFIED)
Before writing a single word, confirm:
- Recipient: name + role
- Technical level: engineer / manager / non-technical
- Tone: formal / conversational / terse / warm
- Desired action: what should the reader do after reading?
- Format: Slack thread / email / Teams / inline comment
- Length cap: sentence / paragraph / multi-paragraph
If ANY are unspecified and not obvious from context → ASK before drafting. Single batched question.
Drafting Rules
- Non-technical audience → no bullets unless explicitly requested. Conversational prose.
- Manager audience → lead with outcome/ask, technical detail only if requested.
- Engineer audience → bullets + code refs fine.
- Match the recipient's prior message style (formality, length) when reply thread exists.
Output
Single draft. No "let me know if you want changes" coda — user will iterate naturally.
Attribution
When naming people (PR authors, ticket owners) → verify via gh CLI / source-of-truth before draft. Don't guess from memory.
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.