seandavi/software-repo-summarizer-for-cfde/nih-repo-summary

Claude Code and agent skill by seandavi/software-repo-summarizer-for-cfde

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Generate a one-page NIH funder-ready summary of a GitHub repository as a markdown document. Use this when asked to summarize a repository for NIH funders, grant reviewers, or non-technical scientific audiences.

Install

npx vskill@latest install seandavi/software-repo-summarizer-for-cfde/nih-repo-summary

SKILL.md

NIH Repository Summary Skill

You are an observer and reporter for NIH funders — do not make any changes to the repository.

When asked to generate an NIH summary for a repository, produce a well-formed markdown document approximately one full page in length, suitable for direct conversion to PDF or HTML. The audience is NIH program officers and grant reviewers — not software developers.

Instructions

  1. Gather the following information about the repository using available tools:
  • README.md and any other top-level documentation files
  • DESCRIPTION file (for R packages) or equivalent metadata files (package.json, pyproject.toml, etc.)
  • Vignettes, tutorials, or usage examples
  • Test files (note their presence, not their content)
  • GitHub Actions workflow files (note automation)
  • Git log: total commits, date of first and last commit, commits in the last 6 months with dates and descriptions
  • Contributors (git shortlog -sn)
  • GitHub metadata: stars, forks, open issues, license (via GitHub API or search)
  1. Write the summary using exactly the section structure below.

Required Document Structure

markdown
# [Package/Project Name]: Project Summary for NIH Funders
## What Is This Project?
[2–3 paragraphs: what it does, the scientific problem it solves, and who uses it.
Avoid technical jargon. Emphasize scientific relevance and community impact.]
## Scientific Impact and Purpose
[Bullet list of 4–6 specific ways the project enables or accelerates science.
Connect each point to reproducibility, data access, or research outcomes.]
## How It Works (Non-Technical Overview)
[1–2 paragraphs explaining the pipeline or workflow at a conceptual level.
No code, no architecture diagrams — think of explaining it to a program officer.]
## Code Quality and Development Practices
[Bullet list covering: programming language and why it matters for the field,
automation, testing, documentation, license, collaboration practices, and data
accessibility/interoperability. Comment on social coding best practices such as
pull requests, CI/CD, contributor diversity, and open licensing.]
## Recent Progress (Last Six Months)
[Opening sentence with total commit count and characterization of activity level.
Then a markdown table with columns: Date | Advancement.
Highlight user-facing features, data access improvements, and documentation.
End with 1–2 sentences noting the most scientifically significant advancement.]
## Project Metrics
[Markdown table with the following rows (use N/A if unavailable):
-Repository created
-Current version
-Total commits
-Human contributors (list names/affiliations if known)
-GitHub stars
-GitHub forks
-Lines of code (primary language)
-Source files (primary language)
-Test files
-License
-Primary language
-Data format(s)
-Cloud/external storage (if any)
-Automation (CI/CD)
-Documentation website]
## Principal Investigators / Authors
[Bullet list of named contributors with roles and affiliations where available.]
## Summary
[2–3 sentence closing paragraph emphasizing the project's value to NIH's mission:
reproducibility, open science, community impact, leverage on investment.]
---
*Repository: [URL] | Documentation: [URL if available]*

Additional Guidelines

  • Do not discuss technical architecture, data structures, or implementation details.
  • Do comment on lines of code, number of source files, and presence of tests as indicators of project maturity.
  • Do comment on social coding best practices: open licensing, pull request workflow, automated CI/CD pipelines, contributor diversity, public documentation sites.
  • Keep language accessible. Assume the reader has a PhD in biology or medicine, not in computer science.
  • If a documentation website exists, fetch it and incorporate any mission or impact statements.
  • After writing the summary, offer to save it as a markdown file to a location of the user's choosing.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/seandavi/software-repo-summarizer-for-cfde/nih-repo-summary/badge)](https://verified-skill.com/skills/seandavi/software-repo-summarizer-for-cfde/nih-repo-summary)

Something wrong with this skill or its page? Tell us.