Skip to main content
ClaudeWave
Skill853 repo starsupdated yesterday

award-application

This skill helps applicants write compelling award submissions and grant applications by mapping their achievements directly to published selection criteria using quantified evidence and structured narratives. Use it when preparing any merit-based application including business awards, grants, competitions, or submissions scored against defined rubrics.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/jezweb/claude-skills /tmp/award-application && cp -r /tmp/award-application/plugins/writing/skills/award-application ~/.claude/skills/award-application
Then start a new Claude Code session; the skill loads automatically.

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 strong
cloudflare-apiSkill

Hit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email routing, cache purge, WAF rules, redirect rules, zone settings, Worker routes, D1 cross-database queries, R2 bulk operations, KV bulk read/write, Vectorize queries, Queues, and fleet-wide resource audits. Produces curl commands or scripts. Triggers: 'cloudflare api', 'bulk dns', 'custom hostname', 'email routing', 'cache purge', 'waf rule', 'd1 query', 'r2 bucket', 'kv bulk', 'vectorize query', 'audit resources', 'fleet operation'.

cloudflare-worker-builderSkill

Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax, API route conflicts, HMR issues, or deployment failures.

d1-drizzle-schemaSkill

Generate Drizzle ORM schemas for Cloudflare D1 databases with correct D1-specific patterns. Produces schema files, migration commands, type exports, and DATABASE_SCHEMA.md documentation. Handles D1 quirks: foreign keys always enforced, no native BOOLEAN/DATETIME types, 100 bound parameter limit, JSON stored as TEXT. Use when creating a new database, adding tables, or scaffolding a D1 data layer.

d1-migrationSkill

Cloudflare D1 migration workflow: generate with Drizzle, inspect SQL for gotchas, apply to local and remote, fix stuck migrations, handle partial failures. Use when running migrations, fixing migration errors, or setting up D1 schemas.

db-seedSkill

Generate database seed scripts with realistic sample data. Reads Drizzle schemas or SQL migrations, respects foreign key ordering, produces idempotent TypeScript or SQL seed files. Handles D1 batch limits, unique constraints, and domain-appropriate data. Use when populating dev/demo/test databases. Triggers: 'seed database', 'seed data', 'sample data', 'populate database', 'db seed', 'test data', 'demo data', 'generate fixtures'.

hono-api-scaffolderSkill

Scaffold Hono API routes for Cloudflare Workers. Produces route files, middleware, typed bindings, Zod validation, error handling, and API_ENDPOINTS.md documentation. Use after a project is set up with cloudflare-worker-builder or vite-flare-starter, when you need to add API routes, create endpoints, or generate API documentation.

tanstack-startSkill

Build a full-stack TanStack Start app on Cloudflare Workers from scratch — SSR, file-based routing, server functions, D1+Drizzle, better-auth, Tailwind v4+shadcn/ui. Use whenever the user mentions TanStack Start, asks to scaffold a full-stack Cloudflare app with SSR, wants an SSR dashboard, or asks for a React 19 + Cloudflare Workers app with file-based routing and server functions — even if they don't name TanStack Start specifically. No template repo — Claude generates every file fresh per project.

vite-flare-starterSkill

Scaffold a full-stack Cloudflare app from the vite-flare-starter template — React 19 + Hono + D1+Drizzle + better-auth + Tailwind v4+shadcn/ui + TanStack Query + R2 + Workers AI. Run setup.sh to clone, configure, and deploy. Use whenever the user wants a batteries-included Cloudflare full-stack app, vite-flare-starter scaffold, or a React + Cloudflare app with auth + database + Workers AI ready to go.