Installs into .claude/skills of the current project.
Are you the author of Source Command Latch Gate?
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-latch)
---
name: source-command-latch-gate
description: Manually run latch gate on a coding or build request. Use when the user invokes latch-gate or /latch-gate in Cursor.
---
# Latch gate for Cursor
Latch Cursor skill boundary: this workflow is safe for project-synced skills
and the Cursor plugin.
Before any Shell fallback, 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 fallback.
Prefer the `latch_gate` MCP tool and pass the user's request verbatim. If MCP is
unavailable, resolve `latch_home` as `${CURSOR_PLUGIN_ROOT}` when set, otherwise
use the absolute checkout in the project-sync footer, select native `cursor`
for plugin installs or the backend in that footer, and run
`bin/run_latch_gate.sh` with `LATCH_GATE_BACKEND` and `LATCH_MODEL_BACKEND` set.
Always show the returned **Latch gate** findings before edits, including the
recommendation, rationale, cited node ids/titles/status, source receipt, better
next action, and uncovered claims. A skipped/error gate does not authorize a
mutation. Do not silently redirect a MODIFY or DO_NOT_PROCEED verdict.
