Flask review loop

Flask is where people and agents iterate on media. An asset is one piece of work, its versions are its iterations, and feedback sits on the moment of the version it was left on: typed comments, drawings on the frame, and voice, camera or screen recordings with their transcripts. Agents read and answer that feedback through the Flask MCP server.

Think of it as GitHub for media: versions are commits, feedback threads are review comments, and the working files attached to a version are the code behind it.

First: is Flask connected?

If the flask MCP server's tools are available (get_guide, upload_file_start, feedback_list, ...), call get_guide(topic: "instructions") once, before any other Flask tool, and follow it. It is Flask's playbook and the source of truth for every detail: upload steps, limits, plans, ids, sharing. This skill only says when to reach for Flask.