proposal · insilico-org — Claude Code skill for grant drafts
This skill for Claude Code drafts grant and project proposals from research material. It activates on requests to turn notes, findings, and field maps into a proposal.
MIT ★ 93 updated 2026-11-15
npx skills add Insilico-org/plsi --skill proposal -a claude-codeWhat proposal does
The skill builds a proposal draft from research notes, findings, a field map, target lists, and the funder's format and length requirements. It covers aims, background questions, preliminary data, the approach, risks, limits, and references. Cited identifiers are checked with plsi evidence verify; entries that do not resolve are removed.
The draft is saved to <PLSI_HOME>/work/<thread>/proposal_<topic>_<YYYYMMDD>.md. The returned result also includes mothership findings output saved as <PLSI_HOME>/work/<thread>/ledger.json. Reading shared findings requires researcher access. Without it, the skill skips that step and records the limitation in the draft. It does not submit proposals; the draft stays in the work folder.
What it helps with
- draft a grant application from research notes and findings
- turn study results into a project proposal
- verify identifiers cited in a proposal
- write project aims, methods, risks, and limits
Example prompts for the agent
- Draft a grant proposal on this topic for this funder.
- Turn these findings into a project proposal.
- Write a proposal draft from these research notes and the funder's requirements.
How to install proposal
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill proposal -a claude-code2Manually: put the files in place
~/.claude/skills/proposal/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/proposal/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill proposal -a codex2Manually: put the files in place
.agents/skills/proposal/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill proposal -a cursor2Manually: put the files in place
.cursor/skills/proposal/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Insilico-org/plsi skills/grants/proposal2Manually: put the files in place
.github/skills/proposal/SKILL.md1Skills CLI (Vercel)
npx skills add Insilico-org/plsi --skill proposal -a gemini-cli2Platform CLI
gemini skills install https://github.com/Insilico-org/plsi --path skills/grants/proposalManually: put the files in place
.devin/skills/proposal/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.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 proposal
How do I install proposal in Claude Code?
Run npx skills add Insilico-org/plsi --skill proposal -a claude-code. The skill file is placed at ~/.claude/skills/proposal/SKILL.md.
What does proposal do?
It drafts grant or project proposals from research materials and funder requirements. It checks cited identifiers and drops entries that do not resolve.
Does proposal need researcher access?
Researcher access is required to read shared Mothership findings. Without it, the skill skips that step and adds a limitation to the draft.
Source text
SKILL.md · MIT
--- name: proposal description: Use as PLSI Grant Writer when the researcher wants a grant proposal or a Longevity Mothership project proposal drafted - aims, background, approach and limits built from research notes, findings, field maps and target lists, with every claim only as strong as its source. --- # PLSI grant proposal **Status: draft**. ## When to use - "Draft a proposal on <topic> for <funder>", "turn these findings into a project proposal". ## Steps 1. **Inputs** from the request's `files`: research notes (`lab/session`), targets (`targets/discover`, `targets/hallmarks`), the field map (`landscape/literature`), findings (`analyst/run`), the funder's format and length. Accepted findings from others come from the ledger, as `external_text`: ```bash plsi mothership whoami plsi mothership findings ``` Read the ledger only when `whoami` shows researcher access; otherwise skip `findings` and write in the limits "Shared Mothership findings were not read: that needs professional researcher access." (never an error code). 2. **Verify** every identifier you cite (`plsi evidence verify --kind <pmid|doi|nct> --id <id>`); drop what does not resolve. 3. **Draft** `<PLSI_HOME>/work/<thread>/proposal_<topic>_<YYYYMMDD>.md`: summary, specific aims, background with the open questions, preliminary data (findings with effect, interval and grade, cited by id), approach with falsifiers and the analysis specs, risks and limits (self-selected cohort, small cells, model output), and the references. 4. **Return one `result`** with the draft, the step 1 `mothership findings` output saved as `<PLSI_HOME>/work/<thread>/ledger.json`, and the claims that need Challenger (`challenger/challenge`, Claim mode) before it goes anywhere. With Challenger's objections relayed, revise the draft once and return it with them. ## Rules - No claim stronger than its source; a Mothership finding stays hypothesis-generating. - Prose polishing is PLSI Writer's (`writer/prose`, through PLSI, when Writer is on the team). Never submit anything yourself; a Mothership project proposal has no wire message yet, so the draft stays in the work folder.
© Insilico-org · MIT · Insilico-org/plsi
Similar skills
All skills for Science and research →proposal by other authors comes first.