Research Proposal Development
hashgraph-online/awesome-codex-plugins
Develop research proposals with solicitation alignment, reviewer-focused logic, evidence-bounded preliminary results, milestones, risks, and compelling figures.
Write a tight Statement of Work (SOW) that prevents scope creep and payment disputes.
Install Statement Of Work
$ npx skills add mohitagw15856/pm-claude-skills --skill statement-of-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills statement-of-work --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/statement-of-work .claude/skills/statement-of-work && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "statement-of-work" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/statement-of-work into .claude/skills/statement-of-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statement-of-work", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/statement-of-workType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill statement-of-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills statement-of-work --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/statement-of-work .agents/skills/statement-of-work && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "statement-of-work" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/statement-of-work into .agents/skills/statement-of-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statement-of-work", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill statement-of-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills statement-of-work --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/statement-of-work .cursor/skills/statement-of-work && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "statement-of-work" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/statement-of-work into .cursor/skills/statement-of-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statement-of-work", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/statement-of-work--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill statement-of-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills statement-of-work --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/statement-of-work .gemini/skills/statement-of-work && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "statement-of-work" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/statement-of-work into .gemini/skills/statement-of-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statement-of-work", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills statement-of-workInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill statement-of-work -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/statement-of-work .github/skills/statement-of-work && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "statement-of-work" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/statement-of-work into .github/skills/statement-of-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statement-of-work", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill statement-of-work -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills statement-of-work --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/statement-of-work .opencode/skills/statement-of-work && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "statement-of-work" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/statement-of-work into .opencode/skills/statement-of-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statement-of-work", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
statement-of-work- GitHub stars
- 1.4k
- Token cost
- ~980 tokens
- SKILL.md length
- 460 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write a tight Statement of Work (SOW) that prevents scope creep and payment disputes.
- Asked to write a SOW
- SKILL.md covers Required Inputs, Output Format, Quality Checks and Anti-Patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A scope of work
What it does
Statement Of Work is an agent skill from mohitagw15856/pm-claude-skills. Write a tight Statement of Work (SOW) that prevents scope creep and payment disputes. Use when asked to write a SOW, a scope of work, a project agreement, or to formalise what was agreed after a proposal. Produces an SOW — scope (and explicit exclusions), deliverables with acceptance criteria, timeline & milestones, payment schedule, assumptions, change-control, and terms. The contract layer after the proposal sells.
Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Proposals and quotes and Project management. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to write a SOW
- A scope of work
- A project agreement
- Formalise what was agreed after a proposal
Example prompts
- “/statement-of-work”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Statement Of Work loads about 980 tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 460 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 460 words, ~980 tokens.
Download SKILL.mdSave it as
.claude/skills/statement-of-work/SKILL.md (or your agent's skills folder).- name
- statement-of-work
- description
- Write a tight Statement of Work (SOW) that prevents scope creep and payment disputes. Use when asked to write a SOW, a scope of work, a project agreement, or to formalise what was agreed after a proposal. Produces an SOW — scope (and explicit exclusions), deliverables with acceptance criteria, timeline & milestones, payment schedule, assumptions, change-control, and terms. The contract layer after the proposal sells.
Statement of Work Skill
The proposal wins the deal; the SOW protects it. Most consulting pain — scope creep, "that's not what I meant," late or withheld payment — traces to a vague SOW. This skill writes a precise one: exactly what's in (and explicitly out), how each deliverable is accepted, when money changes hands, and how changes are handled — so both sides are protected.
Required Inputs
Ask for these only if they aren't already provided:
- The engagement — parties, and what was agreed (often from a
consulting-proposal). - Deliverables — the concrete outputs and how "done" is judged.
- Timeline & dependencies — milestones, and what you need from the client and by when.
- Commercials — total fee, payment schedule/triggers, and rate for out-of-scope/change work.
Output Format
Statement of Work — [project]
Between: [provider] and [client] · Effective: [date]
1. Scope — what will be done, specifically. Then explicit exclusions ("Out of scope: …") — the most valuable section; unsaid scope is assumed-included by clients.
2. Deliverables & acceptance criteria — each deliverable with how it's accepted (the objective bar, and a review window — e.g. "approved, or feedback within 5 business days, else deemed accepted").
| Deliverable | Acceptance criteria | Due |
|---|
3. Timeline & milestones — phases, dates, and client dependencies (their inputs/approvals — and what happens to the timeline if they slip).
4. Payment schedule — amounts tied to milestones/dates, invoicing terms, and late-payment terms. Deposit up front where appropriate.
5. Assumptions — what the plan and price depend on (access, environments, responsiveness) — so a broken assumption is a change, not a fight.
6. Change control — how scope changes are requested, priced (the change rate), and approved in writing before work proceeds. This is the anti-scope-creep clause.
7. Terms — IP/ownership (on payment), confidentiality, termination, liability — flag that legal should review for material engagements.
Show full SKILL.md (178 more words)Show less
Quality Checks
- Scope includes an explicit "out of scope / exclusions" list
- Every deliverable has objective acceptance criteria and a review/sign-off window
- Payment is tied to milestones/dates with late terms (and a deposit where apt)
- Client dependencies are listed, with the timeline consequence if they slip
- A written change-control process with a change rate is defined
- Assumptions the price depends on are stated
Anti-Patterns
- Do not leave scope open-ended — without exclusions, clients reasonably assume everything is included
- Do not omit acceptance criteria — "deliver a website" with no bar means endless revisions
- Do not skip change control — it's the clause that turns scope creep into billable change requests
- Do not ignore client dependencies — if their delay silently becomes your problem, you eat the cost
- Do not present this as final legal advice — recommend counsel review for significant contracts
Based On
Statement-of-work / contracting practice — explicit scope + exclusions, acceptance criteria, milestone payments, change control.
Example Trigger Phrases
- "Write a SOW."
- "Write the scope of work for this project."
- "Turn what we agreed into a project agreement."
- "Stop this project creeping in scope."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/statement-of-work of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Statement Of Work next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Statement Of Work this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~980 | Automated safety check: Pass | MIT | |
| Research Proposal Developmenthashgraph-online/awesome-codex-plugins | 1.3k | — | ~547 | Automated safety check: Pass | Apache-2.0 | |
| Frame A Proposalinkeep/open-knowledge | 4.5k | — | ~3.6k | Automated safety check: Pass | GPL-3.0 | |
| Customer Statustechwolf-ai/ai-first-toolkit | 132 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Onboarding Playbook Creationseb1n/awesome-ai-agent-skills | 206 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Research Grantsaipoch/medical-research-skills | 1.9k | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Frame A Proposal
inkeep/open-knowledge
Frame a new design proposal (RFC-shape) under proposals/ — problem before solution, named beneficiary and observable change, real alternatives, honest drawbacks, and a live open-questions backlog.
Customer Status
techwolf-ai/ai-first-toolkit
Synthesised view of account health and activity for managers overseeing customer-facing teams (Sales, CS, Professional Services, Presales).
Onboarding Playbook Creation
seb1n/awesome-ai-agent-skills
Design structured customer onboarding workflows with phased checklists, email templates, success milestones, and ownership assignments.
Research Grants
aipoch/medical-research-skills
Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan's NSTC when you need agency-compliant narratives, budgets, and review-criteria alignment for a specific solicitation/FOA/BAA.
Grant Writing Guide
wentorai/research-plugins
Write competitive research proposals with clear objectives and budgets
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Questions about Statement Of Work
What does Statement Of Work do?
Write a tight Statement of Work (SOW) that prevents scope creep and payment disputes. Statement Of Work is an agent skill from mohitagw15856/pm-claude-skills. Write a tight Statement of Work (SOW) that prevents scope creep and payment disputes.
When should I use Statement Of Work?
Statement Of Work fits situations like: asked to write a SOW; A scope of work; A project agreement; formalise what was agreed after a proposal.
How do I install Statement Of Work in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill statement-of-work -a claude-code`. Or copy the skill folder (skills/statement-of-work in mohitagw15856/pm-claude-skills) into .claude/skills/statement-of-work in your project. Claude Code loads it when a task matches its description.
How do I install Statement Of Work in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill statement-of-work -a codex`. Or copy the skill folder (skills/statement-of-work in mohitagw15856/pm-claude-skills) into .agents/skills/statement-of-work in your project. Codex loads it when a task matches its description.
Can I use Statement Of Work in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill statement-of-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/statement-of-work, .gemini/skills/statement-of-work, .github/skills/statement-of-work and .opencode/skills/statement-of-work in your project.
What does Statement Of Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Statement Of Work is instructions for the agent only.
Does Statement Of Work access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Statement Of Work safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Statement Of Work use?
Statement Of Work is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Statement Of Work use?
About 980 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Statement Of Work?
Skills that share tags, products or a category with Statement Of Work: Research Proposal Development (hashgraph-online/awesome-codex-plugins, 1.3k stars), Frame A Proposal (inkeep/open-knowledge, 4.5k stars), Customer Status (techwolf-ai/ai-first-toolkit, 132 stars) and Onboarding Playbook Creation (seb1n/awesome-ai-agent-skills, 206 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Statement Of Work?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.