本文へ移動
cccskills
無料GitHub で公開

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md8.9 KB

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:

CriterionKey achievementEvidence/metricStory or example
InnovationAI workflow automationReport time: 3 days to 4 hoursStaff training program, 12 people
GrowthRevenue increase40% YoY, $X to $YNew service line launched Q2
CommunityPro bono program200 hours, 15 local orgsBushfire 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.

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

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Generate AI images using Gemini or GPT APIs directly. Covers model selection (Gemini for scenes; GPT Image 2 for text rendering, batch variations, multi-reference compositing; GPT Image 1.5 for transparent icons), the 5-part prompting framework, API calling patterns, multi-turn editing, and quality assurance. Produces photorealistic scenes, icons, illustrations, OG images, posters, infographics, and product shots. Use when building websites that need images, creating marketing assets, or generating visual content. Triggers: 'generate image', 'ai image', 'create hero image', 'make an icon', 'generate illustration', 'create og image', 'poster', 'infographic', 'image variations', 'gpt-image-2', 'ai art', 'image generation'.

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

app-docs

無料

Generate complete user documentation for a web app with screenshots. Browses the app via browser automation, screenshots every screen, and produces a structured user guide with step-by-step instructions, annotated screenshots, workflow diagrams, and reference tables. Supports quick (key screens), standard (all pages), thorough (every state and flow), and exhaustive (publishable documentation suite). Triggers: 'document the app', 'user guide', 'app documentation', 'screenshot docs', 'generate user docs', 'help docs', 'how-to guide', 'write the docs'.

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

Australian business English for professional writing — warm, direct, EN-AU spelling (colour, organise, centre), no filler words. Use whenever the user is writing for an Australian audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

Run an independent code review using the OpenAI Codex CLI in headless mode. Gets a second opinion from a different model family (the current Codex models) on recent changes, a PR, a commit, or the whole app — covering bugs, regressions, security, data consistency, UX/state bugs, performance risks, and testing gaps. Saves a severity-prioritised report to .jez/reviews/. Triggers: 'codex review', 'review with codex', 'independent code review', 'what does codex think', 'get codex to review'.

日本語の概要は準備中です。原文の説明を表示しています。

jezweb/claude-skills1,0582026年10月9日 更新

jezweb のスキルをすべて見る

このスキルの問題を報告する