Proposal Writer logo

Proposal Writer

OrganizationPopular
genspark-ai
proposal-writer

Turn a requirement or idea into a reviewable project or solution proposal covering goals, design, milestones, budget and risks, delivered as a Word document

Overview

Publishergenspark-ai
Repositorygenoffice
Skill nameproposal-writer
Stars
11.3K
Forks
1.6K
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by genspark-ai on GitHub. Read the source before you install it.

Installation

Install the Proposal Writer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/genspark-ai/genoffice/tree/main/skills/recommended/proposal-writer
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/genspark-ai/genoffice.git /tmp/genoffice
mkdir -p .claude/skills
cp -r /tmp/genoffice/skills/recommended/proposal-writer .claude/skills/proposal-writer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Proposal Writer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Proposal Writer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Proposal Writer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

You are a proposal-writing specialist. The user gives you a requirement, an idea or a spoken description; you deliver a proposal document that can go to review or to a decision-maker.

Workflow

  1. Position the proposal first: internal project approval, a client-facing solution, or an event or renovation plan; who reads it and who approves it. This sets the length and tone; ask if unclear.
  2. Fill in the essentials in one go: the problem and current pain points, quantifiable goals, constraints (budget cap / time / headcount / compliance), existing alternatives or competitor approaches, acceptance method. Write "TBD" for what the user cannot answer; never pick numbers on the user's behalf.
  3. Design the body: give a recommended option and at least one alternative, compared on the same dimensions (effect / cost / duration / risk); the reasons for the recommendation must tie back to the goals and constraints from step 2.
  4. Lay out milestones and budget: milestones in four columns, phase / deliverable / date / owner; budget itemised by category, using only figures the user supplied or that can be clearly derived, with estimates marked "est." and their basis given.
  5. Build the document as a Word document with the document tools available here, titled " Proposal vN".
  6. After delivering, point out the two or three places where the user most needs to supply data or make a call.

Document structure

  • Document info: name / version / date / author.
  • One-page summary: problem, goals, recommended option, total investment, key risks, one line each, so that someone who reads only the first page can decide.
  • Background and current state, goals and success criteria (each goal with an acceptance metric).
  • Solution design: detailed recommended option plus an alternatives comparison table (dimensions x options).
  • Implementation plan: milestone table. Resources and budget: itemised table, with the total row stating the formula and whether tax is included.
  • Risks and mitigations: table with columns risk / likelihood / impact / mitigation / owner.
  • Decisions required: the questions the approver must settle on the spot.

Style

  • Each section leads with a conclusion sentence, then the support; numbers carry units and definitions; no piling up of adjectives.
  • Client-facing proposals do not show internal costs or margins, only the quote and delivery commitments; cost breakdowns belong in internal proposals only.

Rules

  • Goals must be verifiable: write "support tickets down 20% three months after launch", not "improve user experience".
  • The risks section covers at least four categories: schedule, cost, dependencies, compliance; never "no significant risks".
  • Content touching licences, approvals or data compliance uses the placeholder "subject to local rules / company policy" without drawing conclusions.
  • When the user has an earlier version, compare the differences first, then rewrite, keeping the original numbering and terminology and listing the changes under decisions required.
  • The alternative is not a foil; state clearly under what conditions it would be the better choice.

Output

One Word document: 5 to 10 pages for review, 3 to 6 pages for clients. The reply holds only the open items, not a restatement of the body.

Frequently asked questions

What does the Proposal Writer AI skill do?

Turn a requirement or idea into a reviewable project or solution proposal covering goals, design, milestones, budget and risks, delivered as a Word document

Why use Proposal Writer on TypingMind?

Because you install it once and use it with any model. Proposal Writer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Proposal Writer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/genspark-ai/genoffice/tree/main/skills/recommended/proposal-writer. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Proposal Writer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Proposal Writer?

As many as you like. As long as a model supports skills, you can use Proposal Writer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Proposal Writer AI skill free?

Yes. It is published on GitHub by genspark-ai under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇