$npx -y skills add jezweb/claude-skills --skill award-applicationWrite 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
| 1 | # Award Application Writer |
| 2 | |
| 3 | 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. |
| 4 | |
| 5 | ## Process |
| 6 | |
| 7 | ### Step 1: Gather the brief |
| 8 | |
| 9 | Ask the user for: |
| 10 | |
| 11 | - Award/grant name and organiser |
| 12 | - Selection criteria (the exact list, verbatim if possible) |
| 13 | - Word limits (per criterion and/or total) |
| 14 | - Judging rubric or weighting (if publicly available) |
| 15 | - Category entered (if multiple categories exist) |
| 16 | - Whether this is a first submission or a resubmission |
| 17 | - Any specific achievements, metrics, or stories they want included |
| 18 | |
| 19 | 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. |
| 20 | |
| 21 | ### Step 2: Map achievements to criteria |
| 22 | |
| 23 | Create a working table before writing anything: |
| 24 | |
| 25 | | Criterion | Key achievement | Evidence/metric | Story or example | |
| 26 | |-----------|----------------|-----------------|------------------| |
| 27 | | Innovation | AI workflow automation | Report time: 3 days to 4 hours | Staff training program, 12 people | |
| 28 | | Growth | Revenue increase | 40% YoY, $X to $Y | New service line launched Q2 | |
| 29 | | Community | Pro bono program | 200 hours, 15 local orgs | Bushfire recovery site builds | |
| 30 | |
| 31 | 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. |
| 32 | |
| 33 | If the user cannot provide evidence for a criterion, flag it explicitly. Better to know the gap now than to submit vague filler. |
| 34 | |
| 35 | ### Step 3: Write the submission |
| 36 | |
| 37 | 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. |
| 38 | |
| 39 | For each criterion, use the STAR structure: |
| 40 | |
| 41 | - **Situation**: Brief context (1-2 sentences). What was the starting point or challenge? |
| 42 | - **Task**: What needed to happen? What was the objective? |
| 43 | - **Action**: What specifically did you/the business do? Be concrete. |
| 44 | - **Result**: What changed? Quantify the outcome. |
| 45 | |
| 46 | Keep each criterion response self-contained. A judge reading only that section should understand the achievement without needing context from other sections. |
| 47 | |
| 48 | ### Step 4: Review against limits |
| 49 | |
| 50 | - Check word counts per section and total |
| 51 | - Verify every criterion is addressed |
| 52 | - Confirm all claims have supporting evidence |
| 53 | - Read the opening line of each section — does it lead with impact? |
| 54 | |
| 55 | ## Writing Approach |
| 56 | |
| 57 | ### Lead with impact, not chronology |
| 58 | |
| 59 | The first sentence of every section should be your strongest claim. |
| 60 | |
| 61 | **Wrong approach:** |
| 62 | > 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. |
| 63 | |
| 64 | **Right approach:** |
| 65 | > 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. |
| 66 | |
| 67 | Chronology can appear in the body as context, but never as the opening. |
| 68 | |
| 69 | ### Quantify everything possible |
| 70 | |
| 71 | Judges compare applicants. Numbers make comparison easy and your claims credible. |
| 72 | |
| 73 | | Vague | Quantified | |
| 74 | |-------|-----------| |
| 75 | | "Significant growth" | "Revenue increased 40% ($850K to $1.19M)" | |
| 76 | | "Many clients" | "127 active clients across 3 states" | |
| 77 | | "Improved efficiency" | "Reduced report generation from 3 days to 4 hours" | |
| 78 | | "Community involvement" | "Donated 200 hours of pro bono work to 15 local organisations" | |
| 79 | | "Award-winning team" | "Team of 8, including 2 certified Google Partners and 1 Shopify Expert" | |
| 80 | |
| 81 | If exact numbers are not available, use defensible approximations with qualifiers: "approximately", "more than", "over the past 12 months". |
| 82 | |
| 83 | ### Show, don't tell |
| 84 | |
| 85 | Remove adjectives. Replace them with evidence. |
| 86 | |
| 87 | | Telling | Showing | |
| 88 | |---------|---------| |
| 89 | | "We're innovative and forward-thinking" | "Trained 12 staff in AI tools, reducing average report time from 3 days to 4 hours" | |
| 90 | | "We deliver exceptional customer service" | "Net Promoter Score of 72, with 94% client retention over 3 years" | |
| 91 | | "We're passionate about our community" | "Built 6 pro bono websites for Hunter Valley bushfire-affected businesses in 2025" | |
| 92 | |
| 93 | ### Respect word limits absolutely |
| 94 | |
| 95 | 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. |
| 96 | |
| 97 | When |