Install
$ agentstack add skill-marcozorn-agencykit-proposal-writing ✓ 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.
About
proposal-writing
When to use this skill
EN triggers: "proposal", "write a proposal", "client proposal", "new pitch", "scope document" IT triggers: "proposta", "scrivi una proposta", "pitch", "documento di scopo"
Inputs required
Before generating, ask:
- Client name and industry
- Service scope (what will be delivered)
- Budget range (or "unknown")
- Deadline for the proposal
- Do you have past proposals or scope/outcome examples to reference? (optional but recommended)
Output format
Produces two blocks:
CLIENT-FACING PROPOSAL
- Executive summary (2-3 sentences, outcome-focused)
- Scope of work (phased, specific)
- Deliverables list
- Timeline
- Investment (pricing table)
- Payment terms (default: 50% upfront, 50% on delivery)
- Revision policy (2 included, extras billed separately)
- Next steps / CTA
INTERNAL NOTE (do not send)
- Margin estimate if budget provided
- Assumptions made
- Risks flagged
Human gate
This output is a draft. Review all pricing, scope, and commitment language before sending to the client. Do not send automatically.
Brand voice
If a BRAND.md file exists in .claude/skills/proposal-writing/ or .claude/brand/, read it before generating and apply its tone, terminology, and examples throughout the proposal.
Past proposal reference
If the user provides past proposals or scope/outcome example pairs, extract:
- Tone and structure patterns
- Pricing conventions
- How scope was framed
Apply these patterns to the new proposal without copying verbatim.
Edge cases
- If budget is unknown: produce the proposal with a [TBD] placeholder and a note to fill before sending
- If scope is vague: ask one clarifying question before proceeding
- If past examples conflict: use the most recent one as primary reference
🇮🇹 Versione italiana
Quando usare questa skill
Frasi trigger: "proposta", "scrivi una proposta", "pitch cliente", "documento di scopo"
Input necessari
Prima di generare, chiedi:
- Nome e settore del cliente
- Scope del servizio
- Budget indicativo (o "non definito")
- Deadline per la proposta
- Hai proposte precedenti o esempi scope/outcome da usare come riferimento? (opzionale ma consigliato)
Output
PROPOSTA PER IL CLIENTE — sommario esecutivo, scope, deliverable, timeline, investimento, termini di pagamento, politica revisioni, prossimi passi. NOTA INTERNA — stima margine, assunzioni, rischi.
Nota importante
L'output è una bozza. Verifica sempre prezzi, scope e linguaggio contrattuale prima di inviare.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: MarcoZorn
- Source: MarcoZorn/agencykit
- License: MIT
- Homepage: https://marcozorn.github.io/agencykit
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.