Installs into .claude/skills of the current project.
Are you the author of Source Command Latch Gate Report?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/open-latch-source-command-latch-gate-report-latch)
---
name: source-command-latch-gate-report
description: Show a read-only report over recent latch gate activity. Use when the user invokes latch-gate-report or /latch-gate-report in Cursor.
---
# Latch gate report for Cursor
Latch operation id: latch-gate-report run
Before any Shell call, read the workspace `.cursor/mcp.json` and use
`mcpServers.latch.env.LATCH_PYTHON` when present, otherwise
`mcpServers.latch.command`, as `<CURSOR_MCP_PYTHON>` and `LATCH_PYTHON`. Never fall back to a
PATH `python3`; the MCP interpreter owns latch's native dependencies.
Use `latch_home` only to construct the absolute wrapper path. Do not export
`LATCH_HOME` or `CLAUDE_KB_HOME` in the Shell call; managed Cursor operation
receipts do not allow those environment assignments.
Latch Cursor skill boundary: resolve `latch_home` as `${CURSOR_PLUGIN_ROOT}`
when set, otherwise use the absolute checkout in the project-sync footer.
Translate any user-supplied date/limit filters
into arguments and run the host-appropriate `bin/latch_gate_report.sh` or
`.ps1` wrapper. Show the report as-is. This workflow reads structural logs; it
does not run a new gate, read raw prompts, or write decisions.
