Grants
alirezarezvani/claude-skills
NIH grant research skill for clinical researchers. An agent skill from alirezarezvani/claude-skills.
Write compelling award submissions, grant applications, and competition entries.
$ npx skills add jezweb/claude-skills --skill award-application -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jezweb/claude-skills award-application --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/writing/skills/award-application .claude/skills/award-application && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "award-application" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/award-application into .claude/skills/award-application/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "award-application", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/award-applicationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jezweb/claude-skills --skill award-application -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jezweb/claude-skills award-application --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/writing/skills/award-application .agents/skills/award-application && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "award-application" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/award-application into .agents/skills/award-application/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "award-application", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jezweb/claude-skills --skill award-application -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jezweb/claude-skills award-application --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/writing/skills/award-application .cursor/skills/award-application && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "award-application" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/award-application into .cursor/skills/award-application/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "award-application", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jezweb/claude-skills.git --path plugins/writing/skills/award-application--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jezweb/claude-skills --skill award-application -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jezweb/claude-skills award-application --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/writing/skills/award-application .gemini/skills/award-application && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "award-application" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/award-application into .gemini/skills/award-application/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "award-application", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jezweb/claude-skills award-applicationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jezweb/claude-skills --skill award-application -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/writing/skills/award-application .github/skills/award-application && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "award-application" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/award-application into .github/skills/award-application/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "award-application", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jezweb/claude-skills --skill award-application -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jezweb/claude-skills award-application --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jezweb/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/writing/skills/award-application .opencode/skills/award-application && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "award-application" agent skill from https://github.com/jezweb/claude-skills/tree/main/plugins/writing/skills/award-application into .opencode/skills/award-application/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "award-application", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
award-applicationWrite compelling award submissions, grant applications, and competition entries.
Award Application is an agent skill from jezweb/claude-skills. Write compelling award submissions, grant applications, and competition entries. Maps achievements to selection criteria using evidence-based narratives. Use whenever the user is applying for a business award (Telstra, chamber of commerce, industry awards), a grant, a competition, or any submission demonstrating merit against defined criteria.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Skills for Claude Code CLI such as full stack dev Cloudflare, React, Tailwind v4, and AI integrations. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 64965d9. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Award Application loads about 2.3k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 1,215 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jezweb/claude-skills at commit 64965d9, republished under its MIT licence (© jezweb). 1,215 words, ~2,273 tokens.
.claude/skills/award-application/SKILL.md (or your agent's skills folder).Produces award submissions and grant applications that address every criterion with quantified evidence. The goal is a document where every paragraph earns points on the scorecard.
Ask the user for:
If the user has a URL for the award, fetch the criteria page. Many awards publish judging guides or past winner profiles — these are gold for understanding what evaluators value.
Create a working table before writing anything:
| Criterion | Key achievement | Evidence/metric | Story or example |
|---|---|---|---|
| Innovation | AI workflow automation | Report time: 3 days to 4 hours | Staff training program, 12 people |
| Growth | Revenue increase | 40% YoY, $X to $Y | New service line launched Q2 |
| Community | Pro bono program | 200 hours, 15 local orgs | Bushfire recovery site builds |
Every criterion must have at least one entry. A blank row means a missing section in the submission — and missing sections lose marks or trigger automatic rejection.
If the user cannot provide evidence for a criterion, flag it explicitly. Better to know the gap now than to submit vague filler.
Address criteria in the exact order they appear on the application form. Judges often score sequentially — don't make them hunt for your answer to criterion 3 buried in the criterion 1 section.
For each criterion, use the STAR structure:
Keep each criterion response self-contained. A judge reading only that section should understand the achievement without needing context from other sections.
The first sentence of every section should be your strongest claim.
Wrong approach:
Founded in 2018, Acme Digital began as a two-person consultancy. Over the following years, we grew steadily, adding new team members and services. In 2025, we achieved significant growth.
Right approach:
Acme Digital grew revenue 40% in 12 months ($850K to $1.19M) while maintaining a 94% client retention rate. This growth came from a deliberate shift into AI-powered automation services, launched in Q1 2025.
Chronology can appear in the body as context, but never as the opening.
Judges compare applicants. Numbers make comparison easy and your claims credible.
| Vague | Quantified |
|---|---|
| "Significant growth" | "Revenue increased 40% ($850K to $1.19M)" |
| "Many clients" | "127 active clients across 3 states" |
| "Improved efficiency" | "Reduced report generation from 3 days to 4 hours" |
| "Community involvement" | "Donated 200 hours of pro bono work to 15 local organisations" |
| "Award-winning team" | "Team of 8, including 2 certified Google Partners and 1 Shopify Expert" |
If exact numbers are not available, use defensible approximations with qualifiers: "approximately", "more than", "over the past 12 months".
Remove adjectives. Replace them with evidence.
| Telling | Showing |
|---|---|
| "We're innovative and forward-thinking" | "Trained 12 staff in AI tools, reducing average report time from 3 days to 4 hours" |
| "We deliver exceptional customer service" | "Net Promoter Score of 72, with 94% client retention over 3 years" |
| "We're passionate about our community" | "Built 6 pro bono websites for Hunter Valley bushfire-affected businesses in 2025" |
Many awards auto-disqualify entries that exceed word limits. If the limit is 500 words, submit 480-500. Using significantly fewer words than allowed leaves points on the table.
When tight on words:
Vague claims without evidence. "We are industry leaders in digital innovation" means nothing without proof. Every claim needs a number, a name, or a specific example.
Hyperbole and superlatives. "The most innovative company in the region" invites scepticism. Let the evidence speak — if it is the strongest entry, the judges will reach that conclusion themselves.
Missing selection criteria. Even one unaddressed criterion can mean rejection. If you genuinely have nothing for a criterion, acknowledge it honestly and pivot to what you do have: "While we have not yet expanded internationally, our domestic growth of 40% positions us for..."
Company history dump. Founding date, mission statement, and values belong in a one-sentence context line, not a full paragraph. Judges want achievements, not autobiography.
Passive voice and hedging. "It is believed that our approach may have contributed to improved outcomes" vs "Our approach cut processing time by 60%." Be direct.
Too vague:
Acme Digital is committed to innovation and staying ahead of industry trends. We regularly explore new technologies and implement cutting-edge solutions for our clients. Our team is passionate about finding better ways to solve problems and we believe innovation is at the core of everything we do.
Right approach:
In Q1 2025, Acme Digital deployed AI-powered content workflows across 40 client accounts, reducing average content production time from 5 days to 8 hours per campaign. The system combines automated research, draft generation, and human editorial review — maintaining quality (client satisfaction held at 4.7/5) while cutting costs 35%. We trained all 12 team members in prompt engineering over a 6-week internal program, making AI literacy a baseline skill rather than a specialist function. Three clients have since adopted similar internal workflows based on our methodology.
The second version names the innovation, quantifies the impact, explains how it was implemented, and shows downstream effects — all in fewer words than the vague version.
First-time applicants: Judges expect polish from repeat entrants. Compensate by being exceptionally specific with evidence. First-timers often win on the strength of a genuine story well told.
Small business competing against large: Don't try to match their scale. Highlight agility, personal service, per-capita impact, and percentage growth (a 40% revenue increase is impressive regardless of starting size).
Resubmitting after a loss: If feedback was provided, address every point raised. If not, strengthen the weakest section and add any new achievements since last submission. Mention continued commitment if appropriate: "Building on our 2025 entry, we have since..."
Multiple categories: Tailor each submission separately. Reusing identical text across categories signals low effort and often misaligns with different criteria weightings.
© jezweb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/writing/skills/award-application of jezweb/claude-skills.
Open the folder on GitHubat commit 64965d9
Award Application next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Award Application this skilljezweb/claude-skills | 1.1k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Grantsalirezarezvani/claude-skills | 28k | — | ~3.7k | Automated safety check: Pass | MIT | |
| Research GrantsK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~4.3k | Automated safety check: Notes | MIT | |
| Competitive Platform Analysisaffaan-m/ECC | 275k | 1 repos | ~3k | Automated safety check: Pass | MIT | |
| Competitive Report Structureaffaan-m/ECC | 275k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Pp Grantsmvanhorn/printing-press-library | 2.1k | — | ~1.5k | Automated safety check: Notes | Apache-2.0 |
alirezarezvani/claude-skills
NIH grant research skill for clinical researchers. An agent skill from alirezarezvani/claude-skills.
K-Dense-AI/scientific-agent-skills
Supports research proposal preparation and review for NSF, NIH, DOE, DARPA, and Taiwan NSTC, including opportunity-specific requirements, aims, review criteria, budgets, broader impacts, forms, and…
affaan-m/ECC
A skill your agent uses when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins.
affaan-m/ECC
Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis…
mvanhorn/printing-press-library
Find open US federal research funding and benchmark award sizes — Grants.gov open opportunities plus awarded NIH RePORTER and NSF grants, keyless.
sickn33/agentic-awesome-skills
Generate a properly formatted CHANGELOG.md entry in Keep a Changelog format from a commit range or PR.
jezweb/claude-skills
Build conversational AI voice agents on the ElevenLabs platform.
jezweb/claude-skills
Generate custom favicons from logos, text, or brand colours.
jezweb/claude-skills
Set up Tailwind v4 + shadcn/ui themed UI with dark mode. An agent skill from jezweb/claude-skills.
jezweb/claude-skills
All-in-one project configuration and health management. An agent skill from jezweb/claude-skills.
jezweb/claude-skills
Test website responsiveness across viewport widths using browser automation.
jezweb/claude-skills
Build MCP servers in Python with FastMCP. An agent skill from jezweb/claude-skills.
Write compelling award submissions, grant applications, and competition entries. Award Application is an agent skill from jezweb/claude-skills. Write compelling award submissions, grant applications, and competition entries.
Award Application fits situations like: the user is applying for a business award (Telstra; chamber of commerce; industry awards); any submission demonstrating merit against defined criteria.
Run `npx skills add jezweb/claude-skills --skill award-application -a claude-code`. Or copy the skill folder (plugins/writing/skills/award-application in jezweb/claude-skills) into .claude/skills/award-application in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jezweb/claude-skills --skill award-application -a codex`. Or copy the skill folder (plugins/writing/skills/award-application in jezweb/claude-skills) into .agents/skills/award-application in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jezweb/claude-skills --skill award-application -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/award-application, .gemini/skills/award-application, .github/skills/award-application and .opencode/skills/award-application in your project.
SKILL.md names no scripts, command-line tools or credentials: Award Application is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Award Application is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Award Application: Grants (alirezarezvani/claude-skills, 28k stars), Research Grants (K-Dense-AI/scientific-agent-skills, 48k stars), Competitive Platform Analysis (affaan-m/ECC, 275k stars) and Competitive Report Structure (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jezweb (a GitHub user) maintains it in jezweb/claude-skills, which has 1,051 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 5, 2026.
Source: jezweb/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.