jezweb/claude-skills is a collection of skills, commands, plugins, settings, instructions, and hooks that guide the Claude Code CLI through development tasks and produce outputs such as project scaffolds, assets, documents, or deployed services. It is for developers using Claude Code with technologies and services including Cloudflare, React, Tailwind, Shopify, and WordPress. The catalogue entries are the project's own Claude Code workflow components.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add jezweb/claude-skills --skill proposal-writergit clone --depth 1 https://github.com/jezweb/claude-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jezweb/claude-skills/proposal-writer)<a href="https://agentmods.dev/skills/jezweb/claude-skills/proposal-writer"><img src="https://agentmods.dev/badge/skills/jezweb/claude-skills/proposal-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jezweb/claude-skills/proposal-writer"><img src="https://agentmods.dev/badge/skills/jezweb/claude-skills/proposal-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00085 | $0.02535 |
| Opus 5.5 | $0.00034 | $0.01014 |
| Sonnet 5.5 | $0.00017 | $0.00507 |
| Haiku 4.5 | $0.00009 | $0.00253 |
Grade A, and why
proposal-writer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Proposal Writer
Produces proposals for service businesses — web development, consulting, trades, professional services, creative agencies. The goal is a document that wins the work by showing you understood the problem, have a clear plan, and are easy to work with.
Before You Start
Gather these inputs. Ask for anything missing:
- Client name and business — who is this for, what do they do
- What they asked for — the brief, the problem, the conversation summary
- What you are proposing — your recommended solution at a high level
- Pricing — your numbers, or ask for guidance on range
- Timeline — how long, any fixed deadlines
- Tone — match the client relationship (new vs existing, corporate vs casual, local tradie vs enterprise)
If the user has notes from a discovery call or email thread, use those to write the "project understanding" section in the client's own language.
Proposal Structure
Present sections in this order. Every section earns its place — cut any that do not apply.
1. Project Understanding
This is the most important section. It proves you listened. Restate the client's problem in their words, not yours. Show you understand what they are trying to achieve, not just what they asked you to build.
Too corporate:
We understand that your organisation is seeking to leverage digital transformation to enhance customer engagement across multiple touchpoints and drive sustainable growth through an integrated online presence.
Right tone:
You have been running the business for 12 years on word-of-mouth alone, and it has worked — you are booked out most weeks. The problem is that when someone searches "plumber Newcastle" you do not show up, and you are losing jobs to competitors with half your experience. You want a website that shows up in local search and makes it easy for people to call or book online.
Rules for this section:
- Use the client's language, not industry jargon
- Reference specific details from the conversation ("you mentioned", "as we discussed")
- State the business problem, not just the technical requirement
- Keep it to 2-3 short paragraphs
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 212 lines · 85 tokens per session scan A ba52a8eedd84
proposal-writer is a skill published in the GitHub repository jezweb/claude-skills (1,079 stars, last pushed 18d ago), licensed MIT. It adds 85 tokens to every session and 2,535 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
brainstorm-feature
SDLC intake that turns a rough idea into an approved BRD-lite brief (Why lane) or delivery contract (Direction lane) at docs/brd/brd-[slug].md, sized by SNC tier.
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…
scenario-team-admin
Use when administering a Scenario team from an agent through MCP: restricting which models a team or project can run (model access control, allowlist, blocklist), inviting or removing team and project members, changing roles, capping a member's Creative Unit spend, creating or deleting projects, auditing API keys and…
data-evolution-analysis
Analyze data evolution patterns in construction organizations. Assess digital maturity and data strategy for construction companies.