skill-daddia-claude-for-strategy-exec-memo · by Install
$ agentstack add skill-daddia-claude-for-strategy-exec-memo ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-daddia-claude-for-strategy-exec-memo) 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
Exec Memo
When to use
BLUF executive memo from narrative, notes, or narrative-builder output. Conclusion first per ../../references/bluf-conventions.md.
What this skill does not do
- Does not bury the bottom line — BLUF is structural, not stylistic.
- Does not exceed profile length by shrinking the bottom line — cut detail section.
- Does not ship board-final without gate — confirm + reviewer note.
Preconditions
| Input | If missing | |---|---| | Practice profile (length, audience) | Default one page; flag practice-setup | | Source material or narrative | Ask for notes or run narrative-builder |
Provisional mode
Raw notes only: compress inline; label structured first pass if MECE weak.
Trust spine
Per trust-conventions.md — sourcing, assumptions, numbers, confidence, gate before exec-final.
- Analytical Rigor: Every WHY point traces to support; cut non-load-bearing detail.
- Escalation: Ask missing → make impossible to miss; unverified claims → tag not smooth over.
Workflow
- Read practice profile.
- Use
narrative-builderoutput if available; else compress notes inline. - Bottom line first (1–2 sentences, the answer).
- WHY: 2–4 MECE points.
- ASK: decision/resource/sign-off if any.
- DETAIL: optional background last.
- Check length vs profile.
Output format
[BOTTOM LINE]
WHY:
1. [point]
2. [point]
ASK: [or omit]
DETAIL: [...]Worked example
Input: Notes on pricing failure. Bottom line: revert mid-tier increase.
Excerpt: BLUF states revert; WHY three MECE points (volume, elasticity, competitor); ASK: CFO sign-off by Friday.
Quality checks before delivering
- [ ] Bottom line before context
- [ ] MECE WHY section
- [ ] ASK visible if needed
- [ ] Length vs profile
- [ ] Trust spine on figures
Propose profile update
When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/consulting/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /consulting:practice-setup auto-applies a full profile write.
Outputs
Follows plugin CLAUDE.md § Outputs. Quiet mode for client-facing per profile.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: daddia
- Source: daddia/claude-for-strategy
- 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.