agentleFS
jqaisystemsjqaisystems/jqai-ai-skills/skills/proposal-writer/SKILL.md

proposal-writer

Skill3 starsChanged 6 months agoMITView on GitHub

Write a client proposal or quote from your own service tiers, saved once in a pricing config. Produces a structured proposal with a current-situation read, scoped line items, an investment table, process phases, and terms. Drafts only, a human reviews before anything reaches a client. Use when the user says "write a proposal", "quote for this client", "proposal for this project", or "turn this brief into a proposal".

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

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Look for a proposal-pricing.config.md file in the project root.

    line 12
  2. Distinctive:

    Never invent prices, discounts, or proof points.

    line 23
  3. Very specific:

    Default output is a markdown file named Proposal_<Client>.md in the folder the user indicates (or the current project).

    line 31
  4. Distinctive:

    Every scope item maps to a deliverable the client can point at.

    line 63
  5. Distinctive:

    Keep the whole proposal under one page of reading.

    line 65
  6. Distinctive:

    Never invent prices, deadlines, availability, or credentials.

    line 74
  7. Distinctive:

    No em dashes in any output.

    line 75
  8. Distinctive:

    If the user asks for a price you consider off-config, flag it once and then follow their instruction.

    line 76

“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

You write proposals that read like a busy specialist wrote them: specific about the client's situation, clear about scope, and unapologetic about price. This skill produces drafts for human review. It never sends anything.

Step 0: Load the pricing config (never guess prices)

Look for a proposal-pricing.config.md file in the project root. If it does not exist, ask the user for the values below, then offer to save them for next time.

SENDER          Name and positioning title for the header
SERVICES        The services offered, each with a one-line description
TIERS           Price ranges per service or package, with currency
TERMS           Payment split, revision rounds, validity window
PROCESS         The phases a project moves through, with rough durations
PROOF_POINTS    Optional real numbers for credibility, e.g. "300+ projects"

Never invent prices, discounts, or proof points. If a requested scope has no tier, say so and propose a custom line item for the user to price.

Step 1: Read the client's situation

Gather whatever exists: a brief, meeting notes, their website, or a description from the user. The proposal opens with a short read of where the client is now, and that section only works if it is specific. If you know nothing about the client, ask for two sentences about them rather than writing filler.

Step 2: Write the proposal

Default output is a markdown file named Proposal_<Client>.md in the folder the user indicates (or the current project). Structure:

# Proposal: <Client>

**Prepared by:** <SENDER>
**Date:** <today>
**Valid until:** <today + validity window from TERMS>

## Where you are now
Two or three sentences on their current situation. Specific observations, not flattery.

## What I propose
Each scope item with one line on the outcome it buys the client.

## Investment
| Item | Deliverables | Price |
|---|---|---|

## Process
The phases from PROCESS with rough timeline.

## Terms
Payment split, revisions, validity from TERMS.

## Next step
One low-friction closing line.

Rules for the body:

  • Price from TIERS. Round numbers. State the currency once.
  • Every scope item maps to a deliverable the client can point at.
  • The "Where you are now" section must contain at least one observation the client would recognize as true about their business. If it could open any proposal, rewrite it.
  • Keep the whole proposal under one page of reading. Longer proposals hide weak scoping.

Step 3: Report

Show the Investment table and the "Where you are now" section in chat, with the file path. The user reviews and adjusts before the client ever sees it.

Rules

  • Drafts only. Never email or deliver the proposal anywhere.
  • Never invent prices, deadlines, availability, or credentials. Everything comes from the config or the user.
  • No em dashes in any output. Use commas, colons, full stops, or brackets.
  • If the user asks for a price you consider off-config, flag it once and then follow their instruction. It is their business.

Output

One proposal markdown (or HTML on request) file plus a chat summary of investment and positioning for quick review.

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.