← Hoot LensCONTENT HISTORY

Update to Hoot Lens

Snapshot Oct 29, 2026 · 00:06 UTC · version 0.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Hoot Lens and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Connect Hoot Lens and choose an authorized website to investigate without changing capture settings.",
  "included_files": [],
  "name": "setup",
  "skill_md_contents": "---\r\nname: setup\r\ndescription: Connect Hoot Lens and choose an authorized website to investigate without changing capture settings.\r\n---\r\n\r\n# Set up Hoot Lens\r\n\r\n1. Connect the packaged `hootlens` MCP server through the host's sign-in flow. The user signs in and chooses sites and permissions. Start with read and replay. Never ask for a pasted token.\r\n2. Call `whoami` and `list_projects`. Confirm the site the user intends. Ask them to choose if several sites could match. If none are reachable, explain the access state without inspecting another account.\r\n3. For an existing site, begin with `review_findings` and one supporting `get_session_narrative`. Cite observed behavior, IDs and sample sizes. A connection does not prove recording works.\r\n4. If the owner requests a new site, use the packaged Hoot Lens workflow. Creation needs explicit `sites:create` approval for all sites, an available slot, a stable retry key, balanced or strict privacy and required visitor consent.\r\n5. Missing permissions require the user's decision to reconnect and approve them. Setup does not automatically change capture, grant visitor consent or authorize writes.\r\n"
}

SHA-256 of public snapshot: 1f955be092e24a3438fdee1d6205cb964d1aa0dfdb43f3baafe5aa6a5357ae06