gp-current-pending
Prepare the NSF Current and Pending (Other) Support entries for a senior person — every current award, pending proposal (including this one), in-kind support and its person-months — for the PI to enter and certify in SciENcv. Use for "current and pending", "CPS", "other support", "list my awards".
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- gp-current-pending
- description
- Prepare the NSF Current and Pending (Other) Support entries for a senior person — every current award, pending proposal (including this one), in-kind support and its person-months — for the PI to enter and certify in SciENcv. Use for "current and pending", "CPS", "other support", "list my awards".
03 SKILL.md 正文
gp-current-pending
Generated and certified in SciENcv by the person (Gate). The agent assembles a complete, checked list.
Procedure
- Collect from the PI's records (Research.gov Awards, NSF award
letters in
award/, UVMClick FP records, emails):- Current awards: sponsor, number, title, PI role, start/end, total amount, person-months per year (calendar/academic/summer).
- Pending proposals, including the one being prepared: same fields, proposed dates and amount.
- In-kind contributions (visiting positions, lab/compute access with value or "no monetary value").
- Any appointments or support outside UVM.
- Check the person-month overlap. The summer months requested across all NSF awards and proposals must not exceed 2 per year. If they do, state the overlap and how the PI intends to handle it.
- Write
proposal/submission-docs/cps-input.mdas a table with one row per item, plus an "Overall objectives" and a "statement of potential overlap" for each item. SciENcv requires both. - Hand off to the PI: SciENcv → NSF Current and Pending (Other)
Support. Enter the rows, certify, and export the PDF to
submission-docs/cps-<PI>-<year>.pdf. - Verify the exported PDF:
- every row from step 3 is present;
- this proposal is listed as pending with the right amount and dates;
- the certification is present.
- Upload with
gp-researchgov.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code