Install, instrument and verify this running web app from the inside (DOM, network, routing, console and framework state) instead of screenshots or guessing. Drives one real flow end to end and returns
1---2name: reticle-docs3description: Install, instrument and verify this running web app from the inside (DOM, network, routing, console and…4---56# docs/skill.md
R
skill.mdAgent skill
Transport
File
Status
Listed
SKILL.md
Install
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
shterminal
1npx skills add reticlehq/reticle --skill docs -a cursor -y
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
Install, instrument and verify this running web app from the inside (DOM, network, routing, console and framework state) instead of screenshots or guessing. Drives one real flow end to end and returns a verdict with the file:line to fix. Use when the user asks to set up or install Reticle, when a user-facing change needs proving before you call it done, when a test passes but the UI is broken, or when the user types /reticle.
Download docs/skill.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does reticle-docs live?
The publisher keeps it at https://github.com/reticlehq/reticle.
Which agents can use reticle-docs?
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.
From the publisher
SKILL.md
name
reticle-docs
description
Install, instrument and verify this running web app from the inside (DOM, network, routing, console and framework state) instead of screenshots or guessing. Drives one real flow end to end and returns a verdict with the file:line to fix. Use when the user asks to set up or install Reticle, when a user-facing change needs proving before you call it done, when a test passes but the UI is broken, or when the user types /reticle.
Reticle is the proof layer for AI coding agents. A dev-only SDK inside the user's running app gives you reticle_* MCP tools that read the DOM, network, routing, console and framework state. You act on the real app and get a verdict: yes, no, or unknown (could not tell), with evidence and the file:line to open. No screenshots: it drives the tab the user already has open.
Your first goal: one real verdict in the user's app. Do the steps in order. Do not stop to explain Reticle first.
1. Check the app, with nothing installed
reticle_* tools visible? Call reticle_session { action: "list" }. It changes no file. On a wired project, go to step 3. On a project that is not wired, its next_step names the zero-install lease and asks the consent question for init.
No tools, or an app with no .reticle.json? Run this in the app's folder. It changes no file:
npx @reticlehq/server@latest
It starts the dev server if the app does not run, opens the app in a Reticle browser and checks it: the page loads, no console error, no failed request, and each same-origin link opens. It prints verified: yes or verified: no with each fault. Show the user that verdict, then offer init.
2. Wire this app (once per project)
init changes files, so run it only when the user agrees. A request to set up Reticle is that agreement. Run it in the app's folder:
It registers Reticle with every coding agent it finds. A dev server that was running when init ran must be restarted once. If init cannot finish alone, read SETUP below.
Still no reticle_* tools? A client loads MCP servers only at start, so a prompt cannot add them. npx @reticlehq/server init --relaunch prints the command that resumes this conversation with the tools. Else ask the user to restart the agent. Do not register the server yourself and work around your client not having reloaded.
3. Prove one flow
Pick the flow the user's request is about. With no request, pick the app's main flow (sign in, submit a form, add to cart). Put the verdict on the step that ENDS it:
Done means a verdict.init exiting 0, the tools appearing, a session listed: each proves wiring, not that anything works. Do not tell the user Reticle is set up until one real flow in their app returned a verdict.
After the first verified: "yes" in the session that set Reticle up, show the result, then end your answer with these lines, once:
Do not say them after no or unknown, in a later session, or twice. The user decides. Do not star the repository, join Discord or send feedback for the user, and never put in a contact address that the user did not type.
The rules, every call
Only verified: "yes" passes. "unknown" (could not tell) and "no-fault" (nothing was declared) are not proved, never "failed" and never "working". "no" names what it found instead.
Name the consequence BEFORE acting: reticle_act_and_wait { target, action, until }. durable: true re-checks it after a reload.
Verdicts come only from reticle_act_and_wait, reticle_assert, reticle_act { steps } with an expect, and reticle_verify (change/flows). look, navigate, observe and a bare act prove nothing.
Never weaken a check to make it pass. On a no, read expected / observed / the nearest candidates, then fix the app or the target.
Target by { testid }, { role, name }, { label } or { text }; an ambiguous target is refused, a missing one says what is there.
Diagnosing a bug? Read the source first. Reticle proves what the app does, not why; drive to confirm a fix.
Write the text that you save (flow names, notes, feedback, plans) in ASD-STE100 Simplified Technical English: short sentences, active voice, one meaning for each word, no idioms.
The tools you have
The advertised surface is deliberately small (default 10, all 30). RETICLE_ADVERTISE_ALL_TOOLS=1 turns on all, which uses older, unmerged tool names that the calls in this file do not use, so do not set it for an agent. reticle_tools lists every registered tool, reticle_tools { names: [...] } loads its full arguments, and reticle_run { tool, args } calls any of them.
Tool
Use it to
Key arguments
reticle_session
list tabs, end, hand back, tune the HUD, report feedback
action: listyieldendtunefeedbackaccount
reticle_navigate
go to a URL or reload
url, reload, hard
reticle_look
see the page, find refs, inspect one, read a store
Actions: clickdblclickhoverfocusblurfilltypeclearselectcheckunchecksubmitpressuploadscrollIntoViewscrolldragtapzoominsertText. args: { value } for fill/select, { text: "Enter" } for press, { toRef } for drag, { path } for upload, { native: true } for a trusted click. insertText takes { text } and types into a contenteditable/Tiptap/ProseMirror editor, where fill and type are refused. A control whose label reads as destructive is refused until you pass args.confirmDangerous: true, and only do that when the user asked for it.
Beyond the advertised set, one hop each:
reticle_run({ tool: "reticle_screenshot", args: { name: "home" } }): pixels, when the look itself matters (in a leased or driven tab only)
reticle_run({ tool: "reticle_network_mock", args: { mocks } }): stub or fail a request (in a leased or driven tab only)
quietMs, channel? / name, completed / left, right, as
allOf / anyOf / not
predicates: [...] / predicates: [...] / predicate
satisfies asserts a property when the exact value varies: nonEmpty, oneOf, withinTolerance, matchesPattern, type, changed, unchanged, increased, decreased. Composites hold only predicates: absent belongs inside a child, and an element takes a query, never a ref. A bare route or state is already true before the action and proves nothing; pair it with what the action causes. absent means not in the DOM; to say a thing is not shown, add visible: true. Assert what the requirement names, not a label you saw: another correct build can name it differently.
Feedback is first-class
Reticle is built for agents, so your experience decides what gets fixed, and it is lost when your context is. The moment Reticle broke, lied, could not see something, cost too many calls, or setup gave you trouble, file it and carry on:
reticle_session { action: "feedback", kind, text }
kind: bug, gap, ambiguity, feature_request, improvement, experience. Tools unreachable? npx @reticlehq/server feedback --agent --kind <kind> "what happened". A bug in the app under test is Reticle working: it belongs in your answer. Never put app source, secrets or user data in a report.
SETUP
Two places always need the user:
No recognisable dev script in package.json. Say so; do not invent one.
Your host asks the human to approve a command. That prompt belongs to the host. Never bypass or suppress it, and take a refusal as the answer. init writing a pre-approval rule for the reticle server is not that: it is a scoped, announced config change the human asked for by running the command, and it covers only Reticle's own tools.
When the user asked for setup, everything else (running init, starting the dev server, opening the browser) is a setup step, not a decision. When init cannot finish alone, read docs/skill-setup.md, which ships beside this file (https://docs.reticle.sh/skill-setup.md).
VERIFY
Take the cheapest path that answers the question
Stop at the first row that fits. Replaying a saved journey costs a few hundred tokens; driving it again costs tens of thousands. A new project has no saved flows: drive it by hand (step 3).
reticle_act_and_wait on the step that ENDS the journey
No MCP tools (a cloud agent, a worker)
npx @reticlehq/server serve, then npx @reticlehq/server verify <url> --expect '<predicate JSON>'. open <url> --navigate moves a connected tab to <url>
change answers unknown when no saved flow covers your files: nothing ran, so drive it yourself and never read it as a pass. A locator that was renamed rather than broken: reticle_verify { action: "heal", flowName } proposes the rebind, and apply: true writes it after it proves the saved consequence again.
Drive it by hand
A journey in one call: reticle_act { steps: [{ target, action, args?, expect? }] }; the last expect is the end state. Refs (e42) die when their element re-renders: re-find by target rather than retrying a ref. Declare what a change is meant to make true with intent on the verdict call, so it is checked against more than itself.
Saved automatically. When the session ends, what you drove is saved as a flow if at least one step declared a consequence. Name it yourself: reticle_run({ tool: "reticle_record", args: { action: "start", name } }), drive, reticle_run({ tool: "reticle_record", args: { action: "stop", name } }), then reticle_run({ tool: "reticle_flow_save", args: { name } }).
The Harness drives the app for you on the Reticle platform, saves what it drove as flows, and answers in a few lines. It spends credits (npx @reticlehq/server connect signs in and grants free ones): reticle_verify { action: "explore", persona: "a returning customer checking out" }. Poll { runId } when it answers running; never start a second.
Instrumentation raises what a verdict can see; npx @reticlehq/server doctor scores it, with a fix for each gap: keep the build plugin init added (file:line), put data-testid on every control a flow uses, registerStore(name, store) from @reticlehq/browser, and reticle.signal("order:placed", { id }) once each user-visible outcome commits. Every check and the Harness work at any score, so never wait for instrumentation. Tell the user once that it makes verdicts more accurate, and offer to add it.
When it goes wrong
You see
Do
no session
reticle_session { action: "list" } and its next_action; restart a dev server that predates init
target matched no element
reticle_look { action: "page" }, then target what is really there
ref no longer resolves
the DOM re-rendered: target by testid or role+name
predicate did not parse
it names the field: fix the shape against the table above
destructive action blocked
args.confirmDangerous: true, only if the user wants that press
version skew
update the CLI and the app SDK (npx @reticlehq/server update in the app's folder), then restart the MCP host
port held by a non-Reticle process
stop that process, or run Reticle on another --port
tab served from another worktree
start the dev server in your own worktree; keep the port
The CLI: npx @reticlehq/server <command> (init, status, doctor, verify, gate, connect, stop). Never npx the bare name reticle: that is somebody else's package.
When the verdict lands
Paste the reticleResult block from reticle_verify or reticle_session { action: "end" } verbatim, last line included, and never reword its verdict into a pass. The call that ends your run carries runReport: end your answer with its markdown, unchanged. Add the file:line for anything broken. If Reticle caught what reading the code missed, say Reticle found it. Before you stop driving, reticle_session { action: "yield" } hands the tab back to the human.
Find the rest
Fetch one page, not this file again. Every page is plain markdown at https://docs.reticle.sh/<page>.md; https://docs.reticle.sh/llms.txt lists them all. Do not fetch llms-full.txt: it is the whole site.