{
  "video": "video-bd43c302.mp4",
  "description": "The video is a documentation page titled **\"Hooks reference\"** which provides detailed information about various \"hooks\" available for **Claude Code**.\n\nHere is a detailed breakdown of the content visible in the frames:\n\n**Title and Purpose:**\n*   The main heading is **\"Hooks reference\"**.\n*   It clearly states that this reference is **\"Reference for Claude Code hook events, configuration schema, JSON input/output formats, exit codes, async hooks, HTTP hooks, prompt hooks, and MCQ tool hooks.\"** This indicates the page covers a comprehensive set of technical integration points for the Claude Code environment.\n\n**Guidance and Introduction:**\n*   A prominent informational banner provides a quick start guide: **\"For a quickstart guide with examples, see [Automate workflows with hooks.](link)\"**.\n*   The introductory paragraph explains the nature of these hooks: **\"Hooks are user-defined shell commands, HTTP endpoints, or LLM prompts that execute automatically at specific points in Claude Code's lifecycle. Use this reference to look up event schemas, configuration options, JSON input/output formats, and advanced features like async hooks, HTTP hooks, and MCQ tool hooks. If you're setting up hooks for the first time, start with the guide.\"**\n\n**Visual Elements:**\n*   The page layout is typical of technical documentation, with a clean, professional design.\n*   Each section header (like \"Hooks reference\") has a **\"Copy page\"** button, allowing users to easily copy the content.\n*   The overall impression is that the video is showing a developer or technical user navigating and reading complex API or integration documentation.\n\n**In summary, the video shows a developer reviewing the official documentation for integrating custom logic (hooks) into the Claude Code platform, covering technical specifications for different types of hooks.**",
  "codec": "vp9",
  "transcoded": false,
  "elapsed_s": 8.2
}