agentleFS
HaroonArshad-53HaroonArshad-53/skills-for-everyone/skills/proposal-writer/SKILL.md

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

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.
  • Dokkabei97Skill

    sop-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 AzureSkill

    weekly-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

  • akhilkannurSkill

    content-repurposer

    Also in 4 projects that use this

  • claude-office-skillsSkill

    meeting-notes

    >

    Also in 3 projects that use this

  • LangChainSkill

    linkedin-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

  • seikaikyoSkill

    interview-me

    需求不明時的意圖萃取訪談:一次一題、每題附上自己的猜測、聽出「真正想要 vs 覺得應該要」,直到能預測使用者反應(約 95% 信心)才動工。適用:需求缺少對象 / 動機 / 成功標準 / 約束,或使用者點名「訪談我」「先確認一下」「我們確定嗎」。明確自足的指示、純資訊查詢、機械性操作不適用。

    Also in 3 projects that use this

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
  1. Distinctive:

    Read the job post first. Pull out the client number-one problem, the deliverables, and any specific words, tools, or details only a careful …

    line 14
  2. Distinctive:

    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, …

    line 15
  3. Distinctive:

    Never invent experience, clients, numbers, ratings, or portfolio links.

    line 23
  4. Distinctive:

    Never promise a specific result you cannot control (guarantee number-1 ranking, sales in 7 days).

    line 24
  5. Distinctive:

    No buzzword stuffing: avoid synergy, guru, ninja, passionate team player.

    line 25
  6. Distinctive:

    Write in the user own simple voice if they are not a native English speaker - clean and professional, not fake-corporate.

    line 26
  7. Distinctive:

    User: Write me an Upwork proposal for this logo design job post.

    line 34

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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.
  2. 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.
  3. 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.
  4. Paragraph 2: your plan in 3-4 concrete steps, in the order you would actually do the work.
  5. Paragraph 3: proof - the most relevant past result, stated exactly as the user provided it.
  6. Close with one low-friction next step: a short call, a small first milestone, or one clear question.
  7. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.