Update to GrantData

{
  "description": "Turn reviewed nonprofit research into a proposal case, strategy brief, board memo or source packet with clear claims, partner roles and next decisions. Use when the user wants a reusable deliverable rather than another search answer.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 355
    },
    {
      "relative_path": "references/packet-and-citation-cleanup.md",
      "size_in_bytes": 1572
    }
  ],
  "name": "research-packet",
  "skill_md_contents": "---\nname: research-packet\ndescription: Turn reviewed nonprofit research into a proposal case, strategy brief, board memo or source packet with clear claims, partner roles and next decisions. Use when the user wants a reusable deliverable rather than another search answer.\n---\n\n# Research packet\n\nRead [shared evidence rules](../azimuth-research/references/evidence-rules.md). Identify the audience, decision and requested artifact. Reuse the work and accepted choices already present. For a local issue/program case, assemble the need diagnosis, direct/adjacent analogs, claim-to-evidence table, delivery roles, applicant assets, cost basis and funder-specific requirements. Use `program-evidence` and `funder-review` for missing research; do not call a draft reviewed merely because it has every heading.\n\nFor a fundraising strategy, use `fundraising-strategy-process` and its relevant references. For a source brief or presentation, read [packet and citation cleanup](references/packet-and-citation-cleanup.md). Produce the requested usable artifact, with one recommendation/decision and material gaps visible. Capacity, relationship access, commitments and private budgets must come from user context or appropriate verified evidence.\n\nUse native host document abilities to create files when available and requested. Otherwise deliver reusable text/tables in the conversation. Document generators, stored workspaces, hosted packets and monitoring from other Azimuth tools are not available on this connection. State the actual artifact location; drafting a message or application does not send or submit it.\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\nProduce the requested document with ChatGPT's document abilities when available; otherwise deliver reusable text and tables in the conversation.\n"
}