Update to GrantData

{
  "description": "Verify a named funder or partner's current program fit, instrument, eligibility, amount basis and approach route. Use to qualify historical funding leads, refresh stale evidence or build a source-backed account plan.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 349
    },
    {
      "relative_path": "references/public-routes-and-capital.md",
      "size_in_bytes": 2754
    }
  ],
  "name": "funder-review",
  "skill_md_contents": "---\nname: funder-review\ndescription: Verify a named funder or partner's current program fit, instrument, eligibility, amount basis and approach route. Use to qualify historical funding leads, refresh stale evidence or build a source-backed account plan.\n---\n\n# Funder review\n\nRead [shared evidence rules](../azimuth-research/references/evidence-rules.md). Start with the applicant, concrete case and selected funder/partner rather than an undifferentiated web prospect list. Resolve identities using `search`/`fetch`; use selected-peer observations or purpose rows only when the relevant tools are available. An incoming funding card for a foundation does not list its outgoing grants.\n\nInspect current official guidelines, application/program pages, original award/filing records, reports and project announcements with native search. Keep warehouse age, source publication date and date checked distinct. Old warehouse visibility does not establish inactivity; an active website does not establish an open relevant cycle. Do not roll a past deadline into a new year.\n\nBuild an account row with program/instrument; applicant/geography/activity fit; amount and individual-award basis; current cycle and timezone if stated; invitation/application/sponsor route; official contact/channel; relationship provenance; materials/readiness; source/check date; and proposed pursue, validate, steward, hold or set-aside disposition. Leave uncertain amounts and contacts unknown. Do not turn a multi-year aggregate, cohort total or deal value into a typical grant check.\n\nFor public bridge, DAF/donor or housing-finance research read [public routes and capital](references/public-routes-and-capital.md). Those methods add source-backed leads, not warm relationships. Prioritize an application or outreach only when route and case fit are supported; otherwise prioritize the missing checks. Include the applicant's capacity and timing before proposing a solicitation plan.\n\nFor a roster, preserve unresolved entities and material blockers in a short queue. Follow [research review](../azimuth-research/references/research-review.md) for conflicts and explicitly requested enrichment. Native research supplies current checks; the MCP does not silently call another web-search provider.\n\n## In ChatGPT\n\nGrantData is used through the Apps connection; users mention @GrantData in a conversation. Treat the selected public connection as the scope of a GrantData answer. Every public tool is read-only. Do not use private mail, file, or consulting-source connectors to answer a GrantData-scoped request, even when the host account has access to them. If the user wants separate private-source research, distinguish that work and its source from GrantData's public evidence.\n\nUse ChatGPT's native web search for currentness checks and original sources, and cite the page actually checked.\n\nRoutine lookups return text-first results. The peer-funder comparison can render a table component when the host supports app views; still summarize the strongest patterns and the coverage limit in prose.\n\nThe guides are available as plugin skills and through `list_research_workflows` and `get_research_workflow`.\n\nUse ChatGPT's document abilities for a packet when the user asks, and state that nothing was saved to GrantData. The owner connection may expose a save tool, but it is outside the public plugin's capability. Never switch to it to satisfy a public connection save request or represent a needs-review candidate as graph publication or permanent strategy memory.\n\nThe public connection cannot email a funder or submit an application. If asked, state this limit and offer a draft after verifying the intended funder and opportunity. Historical grant observations alone do not establish a live application route.\n"
}