- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add reticlehq/reticle --skill fix-what-i-pointed-at -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add reticlehq/reticle --skill fix-what-i-pointed-at -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add reticlehq/reticle --skill fix-what-i-pointed-at -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add reticlehq/reticle --skill fix-what-i-pointed-at -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/reticlehq/reticle/tree/HEAD/skills/fix-what-i-pointed-atDe l'éditeur
"The spacing on that card is wrong" is unactionable in chat and precise in the app. The Reticle HUD in the running app has a Notes panel. The human clicks Add notes, points at an element, and types what is wrong. Each note becomes a mark carrying the element, the note, and the file:line, so the round trip that usually costs a screenshot, a description, and two clarifying questions costs one call.
Not set up? Follow the reticle skill: it installs Reticle, asks the user before init changes the app's files, and proves one flow.
reticle_session({ action: "review", sessionId })
{
"marks": [
{
"id": "m1",
"note": "this button is misaligned",
"label": "button \"Pay\"",
"source": { "file": "src/Checkout.tsx", "line": 42 },
"fix": "Open src/Checkout.tsx:42 and fix: this button is misaligned."
}
],
"pendingCount": 1
}
Check this at the start of a session, and again whenever the human has been in the app. Reading never consumes a mark, so list → fix → verify → resolve is safe to run in any order.
source.file at source.line. This is the whole point: no hunting for which component rendered that button.note asks for. If the note is ambiguous, the element label and its source usually disambiguate it. Ask the human only when they genuinely do not.reticle_act_and_wait and name the consequence, or reticle_look { action: "element" } on the element for a layout or theme complaint. A visual fix confirmed by looking at it is how the mark gets reopened.reticle_session({ action: "review", sessionId, resolve: "m1" })
Resolve only after the fix is verified. A resolved mark is a promise to the human that the thing they pointed at is done.
Say so against that mark and leave it unresolved. A mark silently dropped is worse than an open one: the human believes it was handled and finds out later. If the note describes intended behaviour rather than a bug, say that too, and let them decide.
They pointed at "that button". Report on "the Pay button on checkout", with what you changed and the evidence it now works. Marks come from people who are looking at the screen, not at the repo, so a report full of file paths and no user-facing language answers the wrong question.
Everything else: curl https://docs.reticle.sh/llms.txt. If a mark arrived without a usable source pointer, that is worth a reticle_session { action: "feedback" } with kind: "gap".
Pick up the bugs a human flagged by pointing at them in the running app, each arriving with the element, the note they typed, and the source file and line. Use when the user says they marked or flagge
---name: fix-what-i-pointed-atdescription: Pick up the bugs a human flagged by pointing at them in the running app, each arriving with the element, the…---# skills/fix-what-i-pointed-at/SKILL.mdVue d'ensemble
Pick up the bugs a human flagged by pointing at them in the running app, each arriving with the element, the note they typed, and the source file and line. Use when the user says they marked or flagged something, when starting a session on an app someone has been clicking through, when a designer or PM has left feedback in the UI, or when the user describes a problem as "that button there" without saying which file.
FAQ
Téléchargez skills/fix-what-i-pointed-at/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/reticlehq/reticle.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.