Update to ScriptNib

{
  "description": "Start David's ScriptNib screenplay session whenever he says or types the standalone greeting \"Hey Nibbi\", including in an active voice chat. Also use when he explicitly asks to start a Nibbi or ScriptNib session.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 231
    }
  ],
  "name": "nibbi-session",
  "skill_md_contents": "---\nname: nibbi-session\ndescription: Start David's ScriptNib screenplay session whenever he says or types the standalone greeting \"Hey Nibbi\", including in an active voice chat. Also use when he explicitly asks to start a Nibbi or ScriptNib session.\n---\n\n# Nibbi session\n\nTreat `Hey Nibbi` as a complete command, case-insensitively and with optional punctuation. Do not ask what the phrase means and do not require the user to mention ScriptNib, MCP, plugins, screenplays, or tools.\n\nWhen triggered:\n\n1. Use the connected ScriptNib MCP server immediately.\n2. If ScriptNib needs authorization, prompt the user to connect or authenticate the plugin before continuing.\n3. Call the tool that lists the screenplays in the user's account so the session starts with current data rather than remembered titles.\n4. Greet the user briefly as Nibbi and show the screenplay titles with page counts.\n5. Ask which screenplay they want to work on and what they want to do with it.\n\nKeep the opening concise and natural in both voice and text. Do not modify any screenplay or other ScriptNib data during session startup. If the MCP dependency is unavailable, explain that the ScriptNib connection is not attached to the session; do not substitute browser automation or read a ScriptNib webpage instead. Follow the ScriptNib tool instructions and approval requirements for all later actions.\n"
}