Token导航 LogoToken导航TokenDH.com
研究检索只读clawhub未标认证来源可访问clear审计通过

grantgrant 搜索

Agent Skill

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

总安装

10,932

周安装

451

GitHub Stars

公开资料未说明

下载量

3,572
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:grant(grant 搜索)
来源仓库:https://github.com/duclawbot/grant
安装命令:
openclaw skills install grant
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install grant

简介

Grant技能为个人与企业提供全面的资助情报系统服务。

  • 覆盖非营利组织、初创公司与科研项目的资金机会挖掘。
  • 自动匹配申请条件并生成材料清单,提升中标概率。grant 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 数据来源于公开数据库,更新频率取决于资助方披露节奏。
  • 重要申请前务必人工复核条款细节,避免误读导致资格不符。

SKILL.md

name
grant
description
>

Grant — Complete Grant Intelligence System

What This Skill Does

Grants are the most underutilized source of funding available to small businesses, nonprofits, researchers, and individuals. Billions of dollars go unclaimed every year — not because eligible applicants do not exist, but because the application process is opaque, time-consuming, and written in language designed for bureaucrats rather than the people the funding is meant to help.

This skill navigates that landscape. It finds the funding, builds the case, and writes the application.

Core Principle

Grant applications are not requests. They are arguments. The reviewer is not deciding whether to give you money — they are deciding whether your project best fulfills the grant objectives. Every word in a successful application is written from the reviewer perspective, not the applicant perspective.

Workflow

Step 1: Profile the Applicant

APPLICANT_TYPES = {
  "nonprofit":      { sources: ["government","foundation","corporate"], strengths: ["impact","track_record","partnerships"] },
  "startup":        { sources: ["innovation","R&D","export","accelerator"], strengths: ["innovation","market","team","scale"] },
  "researcher":     { sources: ["research_councils","university","industry"], strengths: ["methodology","significance","collaboration"] },
  "small_business": { sources: ["business_development","export","energy","hiring"], strengths: ["jobs","economic_contribution","innovation"] },
  "individual":     { sources: ["arts","education","community","professional"], strengths: ["story","impact","viability"] }
}

Step 2: Grant Identification

ELIGIBILITY_CHECKLIST = [
  "Organization type matches funder requirements",
  "Geographic location within funded area",
  "Project dates align with grant period",
  "Budget within grant range",
  "Activity type explicitly included in guidelines",
  "No conflict of interest with funder",
  "Organization in good standing"
]

GRANT_SCORING = {
  "eligibility_fit":   "0-3",
  "strategic_fit":     "0-3",
  "competition_level": "0-3",
  "effort_required":   "0-3",
  "funder_relationship": "0-3"
}
# Pursue grants scoring 10+. Below 8, ROI is poor.

Step 3: Application Architecture

Executive Summary

Written last, placed first. Maximum 200 words. If the reviewer reads only this, they should understand and want to fund it.

Problem Statement

PROBLEM_STRUCTURE = [
  "Scale: how many people or how much is affected",
  "Severity: what happens if this is not addressed",
  "Gap: why existing solutions are insufficient",
  "Urgency: why now"
]
# Use data, research citations, community consultation findings.
# Never frame the problem in terms of your organization needs.

Proposed Solution

What specifically will be done. How it addresses root cause not symptoms. Why this approach over alternatives. Your unique capability to deliver it.

Methodology

WORKPLAN_ELEMENTS = [
  "Phase-by-phase milestones with dates",
  "Team roles and relevant experience",
  "Partners and their specific contributions",
  "Risk identification and mitigation",
  "Timeline fits within grant period"
]

Outcomes and Evaluation

OUTCOMES_FRAMEWORK = {
  "outputs":   "Direct products — number trained, events delivered, reports produced",
  "outcomes":  "Changes that result — skills improved, behavior changed, access increased",
  "impact":    "Long-term change in community or sector"
}
# Every outcome needs a measurable indicator with baseline and target.

Budget

BUDGET_RULES = [
  "Every line item justified in narrative",
  "Administration under 15% unless justified",
  "Show co-contribution if required",
  "Costs verified against market rates",
  "No ineligible expenses included"
]

Step 4: Writing for Reviewers

REVIEWER_RULES = {
  "answer_the_question_asked":  "Read each question three times before writing",
  "lead_with_the_answer":       "First sentence answers. Elaboration follows.",
  "use_their_language":         "Mirror exact terminology from grant guidelines",
  "specificity_wins":           "'45 women trained in rural Victoria' beats 'help disadvantaged communities'",
  "evidence_everything":        "Every significant claim needs a source or statistic",
  "no_jargon":                  "Write for intelligent reviewer who is not a specialist"
}

SCORING_OPTIMIZATION = {
  "principle": "Allocate word count proportional to marks available per section",
  "checklist": "Every scoring criterion explicitly addressed before submitting"
}

Step 5: Post-Submission

IF_FUNDED = [
  "Review signed agreement before signing",
  "Enter reporting schedule in calendar",
  "Establish budget tracking system",
  "Document everything during delivery"
]

IF_UNSUCCESSFUL = [
  "Request reviewer feedback",
  "Distinguish fit issues from quality issues",
  "Revise and reapply if quality was the issue",
  "Thank funder and express interest in future rounds"
]

Grant Calendar

WORKBACK_SCHEDULE = {
  "8_weeks_out": "Eligibility confirmed, decision to apply made",
  "6_weeks_out": "Research complete, outline drafted",
  "4_weeks_out": "First draft complete, internal review done",
  "2_weeks_out": "Revised draft, budget finalized, attachments gathered",
  "1_week_out":  "Final review, proofread, technical submission test",
  "day_of":      "Submit by noon — never on deadline day evening"
}

Quality Check

  • [ ] Every section directly answers the question asked
  • [ ] Problem framed from beneficiary perspective not applicant perspective
  • [ ] All outcomes specific and measurable
  • [ ] Budget justified line by line
  • [ ] All eligibility criteria explicitly demonstrated
  • [ ] All reviewer scoring criteria addressed
  • [ ] Word limits respected
  • [ ] Attachments checklist complete

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

OpenClaw

92.48%
按下载量换算3,303

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

来源信息

继续浏览同类 Skills