award-application

jezweb/claude-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/jezweb/claude-skills --skill award-application
0 commentsdiscussion
summary

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.

skill.md

Award Application Writer

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.

Process

Step 1: Gather the brief

Ask the user for:

  • Award/grant name and organiser
  • Selection criteria (the exact list, verbatim if possible)
  • Word limits (per criterion and/or total)
  • Judging rubric or weighting (if publicly available)
  • Category entered (if multiple categories exist)
  • Whether this is a first submission or a resubmission
  • Any specific achievements, metrics, or stories they want included

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.

Step 2: Map achievements to criteria

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.

Step 3: Write the submission

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:

  • Situation: Brief context (1-2 sentences). What was the starting point or challenge?
  • Task: What needed to happen? What was the objective?
  • Action: What specifically did you/the business do? Be concrete.
  • Result: What changed? Quantify the outcome.

Keep each criterion response self-contained. A judge reading only that section should understand the achievement without needing context from other sections.

Step 4: Review against limits

  • Check word counts per section and total
  • Verify every criterion is addressed
  • Confirm all claims have supporting evidence
  • Read the opening line of each section — does it lead with impact?

Writing Approach

Lead with impact, not chronology

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.

Quantify everything possible

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".

Show, don't tell

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"

Respect word limits absolutely

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:

  • Cut setup/context sentences first (judges know the industry)
  • Combine STAR elements where natural
  • Remove hedging language ("we believe", "we feel that", "it could be said")
  • One strong example beats three weak ones

What Different Awards Look For

Business awards (Telstra, local chamber, BEC)

  • Growth trajectory with numbers
  • Innovation in products, services, or operations
  • Leadership and team development
  • Community contribution and social impact
  • Resilience and adaptability (especially post-COVID, post-disaster)

Industry/professional awards

  • Technical excellence and methodology
  • Client outcomes with measurable results
  • Thought leadership (publications, speaking, mentoring)
  • Industry contribution beyond your own business

Grants

  • Clear problem statement (what needs fixing and why it matters)
  • Feasibility (can you actually deliver this?)
  • Budget justification (every line item tied to an activity)
  • Measurable outcomes (how will you know it worked?)
  • Alignment with the grant's stated objectives

Anti-Patterns

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.

Example: Innovation Criterion

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.

Context Rules

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.

how to use award-application

How to use award-application on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add award-application
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/jezweb/claude-skills --skill award-application

The skills CLI fetches award-application from GitHub repository jezweb/claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/award-application

Reload or restart Cursor to activate award-application. Access the skill through slash commands (e.g., /award-application) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.652 reviews
  • Mateo Gonzalez· Dec 20, 2024

    Solid pick for teams standardizing on skills: award-application is focused, and the summary matches what you get after install.

  • Aarav White· Dec 20, 2024

    Registry listing for award-application matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Pratham Ware· Dec 16, 2024

    I recommend award-application for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Anaya Brown· Dec 16, 2024

    award-application reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Chen Li· Dec 4, 2024

    We added award-application from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Kiara Lopez· Nov 23, 2024

    Keeps context tight: award-application is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Li Lopez· Nov 19, 2024

    award-application fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Daniel Reddy· Nov 11, 2024

    award-application has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Yash Thakker· Nov 7, 2024

    Useful defaults in award-application — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Chinedu Chawla· Nov 7, 2024

    award-application is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 52

1 / 6