award-application
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.
What this skill does
# 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 ofRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.