create-proposal
Skill16 starsChanged 9 months agoMITView on GitHub
Generate PandaDoc proposals from client information or sales call transcripts. Use when user asks to create a proposal, generate a quote, draft a contract, or prepare a client document.
- Reads credentials
4 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- nexus-a1/claude-skillstheir own version, first seen Oct 17, 2026
- MohamedEssam0-0/claude-skillsedited, first seen Oct 11, 2026
- phuongdo/claude-skillsedited, first seen Feb 17, 2026
- nickjwells/skills-workspaceedited, first seen Feb 1, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 3
- nickjwells/skills-workspace★ 2897% same
- MohamedEssam0-0/claude-skills★ 096% same
- phuongdo/claude-skills★ 097% same
Wrote their own version · 1
- nexus-a1/claude-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- add-webhookSkill
- aws-production-deploySkill
- build-in-public-youtubeSkill
- casualize-namesSkill
- classify-leadsSkill
- cross-niche-outliersSkill
- design-websiteSkill
- euron-qaSkill
- excalidraw-diagramSkill
- excalidraw-visualsSkill
- generate-reportSkill
- ghost-browserSkill
- gmail-inboxSkill
- gmail-labelSkill
- gmaps-leadsSkill
- image-to-videoSkill
- instantly-autoreplySkill
- instantly-campaignsSkill
- linkedin-carousel-handwrittenSkill
- literature-researchSkill
- local-serverSkill
- mac-controlSkill
- modal-deploySkill
- Nano Banana 2 Image Generation MasterSkill
- onboarding-kickoffSkill
- pan-3d-transitionSkill
- recreate-thumbnailsSkill
- scrape-leadsSkill
- send-telegramSkill
- skill-builderSkill
- skool-monitorSkill
- skool-ragSkill
- thumbnail-generatorSkill
- title-variantsSkill
- upwork-applySkill
- video-editSkill
- welcome-emailSkill
- whisper-voiceSkill
- youtube-outliersSkill
The file
We split this skill into the rules it gives an agent
7 rules. 7 are common, 0 are distinctive, and 0 are very specific to this project.
7
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 9
Create PandaDoc proposals for clients, either from structured information or by extracting details from sales call transcripts.
- Common: line 31
If user provides structured data, use directly
- Common: line 32
If user provides transcript, extract:
- Common: line 38
Ask for any missing critical information
- Common: line 44
Use direct "you" language (not third-person)
- Common: line 97
Use Gmail to send HTML follow-up email:
- Common: line 111
Follow-up email sent to client
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Proposal Generation
Goal
Create PandaDoc proposals for clients, either from structured information or by extracting details from sales call transcripts.
Inputs (One of the following)
Option A: Structured Data
- Client First Name, Last Name, Email, Company
- Project Title
- 4 Key Problems (brief)
- 4 Key Benefits (brief)
- Project Duration
- Investment Breakdown (Month 1, Month 2, Month 3+)
Option B: Call Transcript
- Sales call transcript to extract all details from
Scripts
./scripts/create_proposal.py- Creates PandaDoc proposal via API./scripts/read_sheet.py- Read client data from sheets if needed
Process
1. Gather Information
- If user provides structured data, use directly
- If user provides transcript, extract:
- Client info (name, company, email)
- Project context and title
- 4 main problems/pain points
- 4 proposed solutions/benefits
- Financial terms (duration, value, costs)
- Ask for any missing critical information
2. Generate Content
Expand the 4 problems and 4 benefits into strategic paragraphs:
Problem Expansion Guidelines:
- Use direct "you" language (not third-person)
- Focus on revenue impact and dollar amounts
- Be specific and actionable
- Example: "Right now, your top-of-funnel is converting very poorly to booked meetings..."
Benefit Expansion Guidelines:
- Address the client directly
- Emphasize ROI and payback period
- Focus on concrete deliverables
Also generate:
- Slide Footer: "Confidential | [Company] Strategic Initiative | [Date]"
- Contract Footer: "[Company]-[ProjectTitle]-[YYYY-MM]"
- Created Date: Current date (YYYY-MM-DD)
3. Execute Proposal Creation
python3 ./scripts/create_proposal.py <<'EOF'
{
"client": {
"firstName": "...",
"lastName": "...",
"email": "...",
"company": "..."
},
"project": {
"title": "...",
"problems": {
"problem01": "[Expanded Problem 1]",
"problem02": "[Expanded Problem 2]",
"problem03": "[Expanded Problem 3]",
"problem04": "[Expanded Problem 4]"
},
"benefits": {
"benefit01": "[Expanded Benefit 1]",
"benefit02": "[Expanded Benefit 2]",
"benefit03": "[Expanded Benefit 3]",
"benefit04": "[Expanded Benefit 4]"
},
"monthOneInvestment": "...",
"monthTwoInvestment": "...",
"monthThreeInvestment": "..."
},
"generated": {
"slideFooter": "...",
"contractFooterSlug": "...",
"createdDate": "..."
}
}
EOF4. Send Follow-Up Email
Use Gmail to send HTML follow-up email:
- Subject: "Re: [Brief Project Context] Discussion"
- Opening: Thank them for discussing challenges
- Body: 2-4 numbered sections with bold headers
- Each section: Description + "Steps:" bullet points
- Closing: "I'll send you a full proposal shortly..."
- Signature: "Thanks, Nick"
5. Notify User
- Provide the PandaDoc "internalLink" for review
- Confirm follow-up email was sent
Output
- PandaDoc proposal URL (for editing/review)
- Follow-up email sent to client
Environment
Requires in .env:
PANDADOC_API_KEY=your_keySchema
Inputs
| Name | Type | Required | Description |
client_first_name | string | Yes | Client first name |
client_last_name | string | Yes | Client last name |
client_email | string | Yes | Client email address |
client_company | string | Yes | Client company name |
project_title | string | Yes | Project title |
problems | array | Yes | 4 key problems (brief) |
benefits | array | Yes | 4 key benefits (brief) |
investment_breakdown | object | Yes | Month 1, Month 2, Month 3+ pricing |
call_transcript | string | No | Alternative: sales call transcript to extract details from |
Outputs
| Name | Type | Description |
pandadoc_url | string | PandaDoc internal link for review |
email_sent | boolean | Whether follow-up email was sent |
Credentials
| Name | Source |
PANDADOC_API_KEY | .env |
Composable With
Skills that chain well with this one: onboarding-kickoff, welcome-email
Cost
PandaDoc API call (free tier available)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

