Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

award-application奖项申请

Agent Skill

award-application 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

9,480

周安装

399

GitHub Stars

750

下载量

3,320
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:award-application(奖项申请)
来源仓库:https://github.com/jezweb/claude-skills
仓库路径:skills/award-application
安装命令:
npx skills add https://github.com/jezweb/claude-skills --skill award-application
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

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

简介

生成符合评审标准的奖项申请和资助材料。

  • 适用于撰写竞赛申报书或科研基金提案。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。
  • 确保每个段落都针对评分标准进行优化。
  • 需提供奖项名称、评选标准、字数限制等关键信息才能使用。
  • award-application 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.77%
按下载量换算1,188

Claude

31.69%
按下载量换算1,052

Cursor

20.36%
按下载量换算676

Gemini CLI

9.41%
按下载量换算312

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills