research-proposal-development — Claude Code skill: setup guide
Structures research proposals around sponsor solicitations, testable aims, and reviewer logic. Useful for grant applications.
npx skills add hanhuark/mechanical-engineering-research-skill --skill research-proposal-development -a claude-codeWhat research-proposal-development does
The skill establishes a multi-step routine to assemble research proposals. It starts by extracting eligibility guidelines, deadlines, budget caps, required narrative sections, and evaluation criteria directly from solicitation documents. Each aim connects to a hypothesis, an execution method, concrete success metrics, and risk mitigations.
The workflow relies on two internal guides: references/proposal-development.md for drafting the main narrative and visual figures, plus references/budget-and-justification.md for building and reconciling budget justifications. Preliminary data serves strictly as feasibility evidence rather than guaranteed performance.
During final reviews, the workflow forces numerical cross-checking between the workbook and project text. When institutional clearances or external commitments are involved, it mandates explicit flagging instead of improvised compliance language.
What it helps with
- extract proposal guidelines, deadlines, and criteria from solicitations
- map scientific aims to testable hypotheses and risk mitigation steps
- reconcile budget justifications against narrative schedules and workbooks
- design informative proposal figures for feasibility and concept workflows
Example prompts for the agent
- Review the preliminary data section using the criteria in
references/proposal-development.md - Align our proposed aims with the evaluation guidelines from the solicitation
- Check budget numbers between the workbook and justification narrative
How to install research-proposal-development
1Skills CLI (Vercel)
npx skills add hanhuark/mechanical-engineering-research-skill --skill research-proposal-development -a claude-code2Manually: put the files in place
~/.claude/skills/research-proposal-development/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/research-proposal-development/
1Skills CLI (Vercel)
npx skills add hanhuark/mechanical-engineering-research-skill --skill research-proposal-development -a codex2Manually: put the files in place
.agents/skills/research-proposal-development/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hanhuark/mechanical-engineering-research-skill --skill research-proposal-development -a cursor2Manually: put the files in place
.cursor/skills/research-proposal-development/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hanhuark/mechanical-engineering-research-skill research-proposal-development2Manually: put the files in place
.github/skills/research-proposal-development/SKILL.md1Skills CLI (Vercel)
npx skills add hanhuark/mechanical-engineering-research-skill --skill research-proposal-development -a gemini-cli2Platform CLI
gemini skills install https://github.com/hanhuark/mechanical-engineering-research-skill --path skills/research-proposal-developmentManually: put the files in place
.devin/skills/research-proposal-development/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add hanhuark/mechanical-engineering-research-skill --skill research-proposal-development -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about research-proposal-development
How to install research-proposal-development in Claude Code?
Run npx skills add hanhuark/mechanical-engineering-research-skill --skill research-proposal-development -a claude-code in your terminal. The configuration writes to ~/.claude/skills/research-proposal-development/SKILL.md.
What does research-proposal-development do?
It guides researchers through constructing reviewer-aligned grant applications, structuring hypotheses, figures, budgets, and risk matrices.
Which reference documents does this skill consult?
It reads references/proposal-development.md for narrative and visual planning, and references/budget-and-justification.md for subawards and budget justifications.
Source text
SKILL.md · MIT
--- name: research-proposal-development description: Develop research proposals with solicitation alignment, reviewer-focused logic, evidence-bounded preliminary results, milestones, risks, and compelling figures. Use for federal, foundation, equipment, partnership, or internal research proposals. --- # Research Proposal Development ## Purpose Turn an important research question into a reviewer-decision-ready proposal. Preserve the investigator's scientific direction and distinguish verified preliminary evidence, proposed work, assumptions, and collaborator-dependent commitments. ## Route To Reference Read `references/proposal-development.md` before drafting a full narrative, responding to review criteria, planning proposal figures, integrating preliminary results, or polishing a submission. Read `references/budget-and-justification.md` before building a budget, writing a budget justification, preparing a subaward budget, or reconciling the budget with the narrative. ## Workflow 1. Extract the solicitation's scope, eligibility, deadline, budget and duration constraints, required sections, evaluation criteria, and special requirements from primary sources. 2. Frame the need: high-value application or scientific barrier, current state, precise gap, reason it endures, and the proposed solution's testable advance. 3. Map every aim or thrust to a hypothesis, method, measurable success criterion, risk, mitigation, deliverable, and reviewer criterion. 4. Use preliminary results as evidence of feasibility, not proof of promised outcomes. Label planned partnerships, facilities, datasets, and external commitments unless confirmed. 5. Make the figure plan do work: system concept, evidence of feasibility, causal mechanism, work plan, and quantitative success metrics. ## Writing Rules Each paragraph should answer one reviewer question. Avoid generic impact claims, unexplained work packages, and a list of tasks that does not produce knowledge. Explain why the team, methodology, and timeline make the proposed advance credible. ## Final Review Check factual solicitation alignment, budget/timeline consistency (recompute the justification against the workbook and the narrative), references, labels on preliminary versus proposed material, and all claimed collaborator, institutional, or facility commitments. Flag requirements that require institutional review rather than inventing compliance language.
© hanhuark · MIT · hanhuark/mechanical-engineering-research-skill