proposal-writer
Skill1 starsChanged 32 days agoMITView on GitHub
Write a specific, non-spammy freelance proposal for Upwork, Fiverr, Contra, or direct clients, based on the client actual job post and the freelancer real skills and past work. Use when a user asks to write a proposal, cover letter for a gig, bid, or pitch for a freelance job, or says help me apply for this job post. Never produce generic copy-paste proposals.
29 other projects use a version of this.
Adopted by
Most recently taken up by
- runbooklabhq/freelancer-ops-skills-litetheir own version, first seen Nov 8, 2026
- Jakeschincariol/closer-skilltheir own version, first seen Nov 8, 2026
- AgnesAI-Labs/agnet-skills-cntheir own version, first seen Nov 1, 2026
- jqaisystems/jqai-ai-skillstheir own version, first seen Nov 1, 2026
- Nomanriaz786/claude-consulting-teamtheir own version, first seen Nov 1, 2026
- genspark-ai/genofficetheir own version, first seen Oct 25, 2026
Used with
Projects with it also use sop-writer, weekly-report and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Dokkabei97Skillsop-writer
Creates Standard Operating Procedures for repetitive tasks. Generates step-by-step documentation with checklists, decision trees, and responsibility assignments to eliminate single points of failure.
Also in 3 projects that use this
Microsoft AzureSkillweekly-report
**WORKFLOW SKILL** — Generate weekly executive reports for the azd team. Pulls PR/issue/release data from GitHub, reads changelogs, combines with team notes, and produces a polished markdown report.
Also in 5 projects that use this
akhilkannurSkillcontent-repurposer
Also in 4 projects that use this
claude-office-skillsSkillmeeting-notes
>
Also in 3 projects that use this
LangChainSkilllinkedin-post
Write a LinkedIn post based on research findings or a given topic. Use this skill when asked to create LinkedIn content, professional posts, or thought leadership pieces.
Also in 3 projects that use this
seikaikyoSkillinterview-me
需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。
Also in 3 projects that use this
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 29
- genspark-ai/genoffice★ 12ksame name
- claude-office-skills/skills★ 433same name
- hamzafarooq/claude-code-starter★ 145same name
- duncan-buildroom/freeskills★ 65same name
- ncklrs/startup-os-skills★ 51same name
- Jakeschincariol/closer-skill★ 33same name
- Xipher-Labs/walter-os★ 8same name
- ARCASSystems/FounderOS★ 7same name
- chakmarebel/federal-proposal-copilot★ 4same name
- dotlabshq/crux★ 4same name
19 more not listed
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 repository11 other files it gives its agents.
- assignment-researcherSkill
- client-brief-analyzerSkill
- fyp-project-managerSkill
- interview-grillerSkill
- learn-in-30-daysSkill
- portfolio-case-studySkill
- pricing-calculatorSkill
- professional-emailSkill
- project-scope-plannerSkill
- resume-builderSkill
- study-any-topicSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
7
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
- Distinctive: line 14
Read the job post first. Pull out the client number-one problem, the deliverables, and any specific words, tools, or details only a careful …
- Distinctive: line 15
Ask for (or use what the user gave): the user 2-3 most relevant past results, tools they actually know, and one proof item (link, number, …
- Distinctive: line 23
Never invent experience, clients, numbers, ratings, or portfolio links.
- Distinctive: line 24
Never promise a specific result you cannot control (guarantee number-1 ranking, sales in 7 days).
- Distinctive: line 25
No buzzword stuffing: avoid synergy, guru, ninja, passionate team player.
- Distinctive: line 26
Write in the user own simple voice if they are not a native English speaker - clean and professional, not fake-corporate.
- Distinctive: line 34
User: Write me an Upwork proposal for this logo design job post.
“Common” is measured: kept by at least 6 in 10 of the 21 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 Writer
When to use this skill
- Applying to a freelance job post on any platform
- Pitching a client directly by email or DM
- Rewriting a proposal that got no replies
Workflow
- Read the job post first. Pull out the client number-one problem, the deliverables, and any specific words, tools, or details only a careful reader would catch.
- Ask for (or use what the user gave): the user 2-3 most relevant past results, tools they actually know, and one proof item (link, number, or outcome). If proof is missing, write the proposal without inventing any.
- Open with the client problem and a specific detail from their post - never with Dear Sir/Madam, I am an expert with 5 years experience.
- Paragraph 2: your plan in 3-4 concrete steps, in the order you would actually do the work.
- Paragraph 3: proof - the most relevant past result, stated exactly as the user provided it.
- Close with one low-friction next step: a short call, a small first milestone, or one clear question.
- Match length to platform: Upwork and direct proposals 150-250 words unless the post asks specific questions - then answer every question first.
Rules - never break these
- Never invent experience, clients, numbers, ratings, or portfolio links. If the user has no proof yet, use a credible first-job angle: a small paid trial milestone and a relevant sample they do have.
- Never promise a specific result you cannot control (guarantee number-1 ranking, sales in 7 days). Promise process and deliverables instead.
- No buzzword stuffing: avoid synergy, guru, ninja, passionate team player. Specific beats impressive.
- Write in the user own simple voice if they are not a native English speaker - clean and professional, not fake-corporate.
Output format
- The proposal - ready to paste, in the structure above
- Why this angle - 1 line: which client pain the opening targets
- One thing to personalise before sending - the single detail to double-check
Example
User: Write me an Upwork proposal for this logo design job post. I have done 3 logos for local shops, I use Illustrator, no online reviews yet.
Good output (excerpt): Opening line written for that post: Your post mentions the current logo looks fine on the shop sign but unreadable on Instagram - that is a scalability problem, not a design-taste problem, and it is fixable in the first concept round. No experience was invented; the 3 local-shop logos are used as proof.
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.

