Skill：reticle
AI agents can generate code, but still struggle to understand what they build. Reticle brings Jev-style machine-native runtime perception to web & desktop applications.
适用场景
代码提效
适合角色
介绍
以下内容整理自开源仓库 `reticlehq/reticle` 的 README / SKILL.md 摘要：
# Reticle
Reticle embeds a dev-only SDK in the user's running app and exposes it to you as `reticle_*` MCP tools. You look, act, observe, and assert against the real app. No screenshots, and no browser download for the verify loop: it drives the tab the user already has open.
This file is the whole critical path and nothing else. Everything it leaves out is at `https://docs.reticle.sh`, one page at a time.
## Your first action, before you read the rest
Do not spend a turn working out which path you are on.
**`reticle_*` tools visible?** The machine is set up. Go straight to the project:
```bash
RETICLE_INSTALL_SOURCE=skill_file npx @reticlehq/server@latest init
```
**Not visible?** Hand the user one line to run in a terminal, outside this client, and stop there:
```bash
curl -fsSL https://raw.githubusercontent.com/reticlehq/reticle/main/install/install.sh | sh
irm https://raw.githubusercontent.com/reticlehq/reticle/main/install/install.ps1 | iex # Windows
```
It registers the MCP server with every agent it can reach; they reopen this client and the tools are there. Do not instead register it yourself and then work around your client not having reloaded: that is the sequence that breaks.
`init` is ONBOARDING, and where it stops: wire, boot, wait for a session. Idempotent, reporting `·` for what is already there. Then the FIRST RUN, which proves anything at all:
```
reticle_verify { action: "explore", persona: "<the journey worth proving>" }
```
Name the journey: Reticle can list the buttons, not which one matters. `explore` SAVES what it drove, so later runs replay with no model.
Everything between here and there is a rule the steps assume. Read it as you go, not before you act.
## Installed means a verdict was produced
**Setup is not complete until you have driven one real flow in the user's app and produced a verdict.** Writing config files is not installed. Every earlier point looks like success and is not:
- `init` exited 0. Wired, and connected. Nothing is PROVED: that is the first run.
- The `reticle_*` tools appeared. Your client can reach a daemon. The app is very likely still uninstrumented.
- A session is listed. The app dialled in. The user has still seen nothing happen.
**Do not tell the user Reticle is set up until a verdict exists.** The common failure is an agent that writes the config, reports success, and leaves somebody with an uninstrumented page. The command exits non-zero when that happens: believe the exit code over the report.
## Setup runs to the end without you
**Do not stop, and do not ask the user anything, until their app is running with Reticle inside it and a session is connected.** Everything between here and that point is yours to do: run `init`, fix the wiring it could not, start the dev server, op
---
**说明**：内容由公开仓库整理，使用前请自行核对是否适合你的场景。
安装方式
1. 打开仓库：https://github.com/reticlehq/reticle 2. 查找 SKILL.md 或 README 中的安装章节 3. 克隆或下载所需 Skill 子目录到本地 skills 路径（如 `.cursor/skills/` 或 `.claude/skills/`） 4. 重启 / 重载 Agent 客户端 5. 用一条真实任务验证 Skill 是否被正确加载
适用平台
- Claude