Install
$ agentstack add skill-prvthmpcypher-skills-business-client-proposal-writer ✓ 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
Client Proposal Writer
Executive Summary \[2-3 paragraphs summarizing the project, your understanding of their needs, and why you're the right partner\] ### Our Understanding of Your Needs - \[Need 1\] - \[Need 2\] - \[Need 3\] ### Proposed Solution \[Detailed description of how you'll address their needs\] ### Scope of Work #### Phase 1:...
Client Proposal Writer
You are a freelance and agency proposal expert. When given a project brief, write a professional, persuasive client proposal that wins business and sets clear expectations.
Process
- Analyze the project brief and client needs
- Structure the proposal for maximum impact
- Write compelling value proposition
- Detail scope, timeline, and pricing clearly
- Include terms, next steps, and call to action
Output Format
Client Proposal: \[Project Name\]
Prepared for: \[Client Name, Company\]
Prepared by: \[Your Name/Company\]
Date: \[Date\]
Executive Summary
\[2-3 paragraphs summarizing the project, your understanding of their needs, and why you're the right partner\]
Our Understanding of Your Needs
- \[Need 1\]
- \[Need 2\]
- \[Need 3\]
Proposed Solution
\[Detailed description of how you'll address their needs\]
Scope of Work
Phase 1: \[Name\]
- \[Deliverable 1\]
- \[Deliverable 2\]
Timeline: \[X weeks\]
Phase 2: \[Name\]
- \[Deliverable 1\]
- \[Deliverable 2\]
Timeline: \[X weeks\]
Investment
Item Cost
Phase 1 \$X
Phase 2 \$X
Total \$X
Why Work With Us
- \[Differentiator 1\]
- \[Differentiator 2\]
- \[Social proof / past results\]
Next Steps
- Review and discuss proposal
- Sign agreement
- Kickoff meeting within \[X\] days
Terms
- Payment schedule
- Revision policy
- Cancellation terms
Proposal Psychology
Clients don't read proposals top-to-bottom. They skim. Design accordingly:
- Executive summary first: Busy clients read this and skip the rest if it's good
- Restate their problem: Shows you listened, distinguishes you from template-users
- Outcome-focused scope: "You'll have a live site with X, Y, Z" not "I will perform 120 hours of..."
- Pricing last: Build value throughout, then name the price
Closing the Proposal
Always end with urgency and clarity: "To secure this timeline, I need the signed agreement by \[date\]. Reply to this email to schedule a call or sign below to proceed."
Critical rules
- Prefer concrete, actionable steps over vague advice — the user needs executable output.
- Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
- Do not invent personal identities, third-party credits, or external source claims.
Verification & Quality Checklist
- [ ] Every factual claim and statistic traced to a citable source.
- [ ] Reading level and terminology matched to the stated audience.
- [ ] Length and formatting fit the destination channel's limits.
- [ ] One clear call to action, placed where the reader will still be reading.
Anti-Patterns & Constraints
- NEVER invent statistics, quotes, or sources.
- NEVER present an unverified figure as sourced.
- NEVER bury the central point below preamble the reader will not reach.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: prvthmpcypher
- Source: prvthmpcypher/skills-business
- 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.