Update to offgen

{
  "description": "Generate branded, consultant-quality PowerPoint decks with offgen. Use when the user asks for a presentation, slide deck, pitch, proposal, report or any .pptx built from one of their organization's offgen workflows, or asks what offgen can generate for them.",
  "included_files": [],
  "name": "offgen-presentations",
  "skill_md_contents": "---\nname: offgen-presentations\ndescription: Generate branded, consultant-quality PowerPoint decks with offgen. Use when the user asks for a presentation, slide deck, pitch, proposal, report or any .pptx built from one of their organization's offgen workflows, or asks what offgen can generate for them.\nlicense: Proprietary\ncompatibility: Requires the offgen MCP server (https://api.offgen.ai/mcp) to be connected.\nmetadata:\n  author: offgen\n  homepage: https://offgen.ai\n---\n\n# offgen presentations\n\noffgen turns a short brief into a finished PowerPoint deck on the user's own company template. Each organization configures **workflows**: reusable, branded deck recipes such as a sales proposal, a monthly report or an information memorandum. You pick a workflow, fill its inputs and offgen builds the `.pptx`.\n\nUse the `offgen` MCP tools. Never try to build the deck yourself from scratch when an offgen workflow fits.\n\n## Flow\n\n1. **List.** Call `list_workflows` with no arguments. Pick the workflow whose description best matches the request. Always address a workflow by its `id`, never by its display name. If several fit, or none clearly does, show the user the short list and ask.\n2. **Describe.** Call `describe_workflow` with that `workflowId`. Read `inputs` and `inputSchema`: which fields are required, their types and the allowed values of choice fields.\n3. **Gather inputs.** Fill every required input from the conversation. Ask the user only for required values you cannot infer. Dates are calendar days in `YYYY-MM-DD` format. Choice fields must use one of the listed values exactly.\n4. **Generate.** Call `generate_presentation` with `workflowId` and `inputs`. It returns a `runId` straight away with status `queued`. If it returns an error, fix the inputs it names and try again.\n5. **Poll.** Call `get_result` with the `runId`. Each call waits up to 55 seconds. While `pollAgain` is `true`, call `get_result` again with the same `runId`. Do not call other tools or read other skills between polls. `slidesEmitted` shows progress; a deck usually takes one to five minutes.\n6. **Share.** When `status` is `completed`, give the user the download link from the result as a clickable Markdown link. The link is signed, works without signing in and expires, so share it right away. Do not try to download, open or summarize the file yourself. When `status` is `failed`, tell the user the `error` message and offer to retry with changed inputs.\n\n## Tips\n\n- Tell the user which workflow you chose and why before generating, in one sentence.\n- One run makes one deck. For several decks, start the runs and then poll each `runId`.\n- `download_presentation` returns the same link as a completed `get_result`. Use it only to get a fresh link for an older run.\n- If a tool says the API key or sign-in is invalid, ask the user to reconnect offgen (API keys live at https://app.offgen.ai/settings/api-keys).\n"
}