← ClaudeAtlas

proposal-polishlisted

Funding-proposal editing mode (NSF Project Summary/Description, NIH Specific Aims, fellowship proposals). Keeps the vision-and-feasibility register a paper would trim, enforces claim-feasibility matching, edits the score-forming first pages hardest, and applies the shared L0 lexical policy. Never invents preliminary data, partners, funding history, or letters, and is not for evading AI-use disclosure.
skymanbp/sci-paper · ★ 5 · AI & Automation · score 70
Install: claude install-skill skymanbp/sci-paper
> **Normative authority:** `docs/SCIPAPER_STANDARD.md`. The L0 lexical policy > (Tier A, Tier B caps, em-dash zero) and the rewrite-eligibility invariants > (§6: numbers, citations, stance, qualifiers) apply to proposals exactly as to > papers. What changes is the **register**: a proposal is sold on vision plus > feasibility, so ambition language that `/sci-paper:paper` would trim is > appropriate here when a credible plan backs it. > > **Provenance:** adapted from academic-humanizer Layer 6 and its examples > (github.com/AIScientists-Dev/academic-humanizer, MIT License, Copyright (c) > 2026 AIScientists-Dev; that skill's paper-mode content now lives in > `/sci-paper:de-ai`). Restructured to the sci-paper feedback contract. # proposal-polish — funding-proposal editing mode ## When to use Editing or reviewing funding proposals: NSF Project Summary / Project Description (including CAREER), NIH Specific Aims / Significance / Innovation / Approach, fellowship and foundation proposals. **Not** for journal manuscripts (use `/sci-paper:paper` + `/sci-paper:paper-review`), and **never** to fabricate results, partners, funding history, or support letters. Using this skill does not remove the obligation to follow the funder's AI-use disclosure policy. ## Core register shift (vs. paper mode) A paper reports finished results; a proposal is scored on **vision plus feasibility**. Consequences: - **Keep and deploy ambition** ("long-term goal", "transformative", "establish a foundati