proposal-writer

Draft client proposals and statements of work that scope, price, and win the project.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./apps/desktop/electron/default-skills/proposal-writer/SKILL.md

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, well-structured instruction-only skill with concrete guidance and a clear workflow; its main gap is the absence of a worked example and an explicit validation feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and purposeful with no padding and no over-explanation of concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Provides a concrete section checklist, named principles, a four-step workflow, and an output-format template, but lacks a worked example proposal to anchor the guidance.	4 / 5
Workflow Clarity	The 'How to work' steps give a clear four-step sequence with a 'flag assumptions / confirm before sending' checkpoint, but there is no explicit error-recovery feedback loop.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references, organized into well-labeled sections (When to use, What a strong proposal contains, Principles, How to work, Output format), matching the simple-skill exception for a top score.	5 / 5
	Total	18 / 20 Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a clear niche with several concrete actions, but it lacks an explicit 'when to use' trigger clause, which caps completeness and limits trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when drafting a client proposal, SOW, or bid from a brief or discovery notes').

Include common synonyms users say (SOW, bid, RFP, pitch) to broaden trigger-term coverage.

Add one or two more concrete deliverable actions (e.g., 'define scope, timeline, and pricing') to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (client proposals and statements of work) with a few concrete actions (draft, scope, price), but coverage is not comprehensive and 'win the project' is an outcome rather than an action.	3 / 5
Completeness	Gives a clear 'what' (draft proposals/SOWs that scope, price, and win) but no explicit 'Use when...' trigger clause, so completeness is capped at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('client proposals', 'statements of work', 'scope', 'price') but omits common synonyms such as SOW, bid, or RFP.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (client proposals and SOWs) with minimal conflict risk, though it could overlap with closely related writing skills such as PRD or copywriting.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: holaboss-ai/holaOS
Path: apps/desktop/electron/default-skills/proposal-writer/SKILL.md
Commit: 4684714

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.