fix-what-i-pointed-at
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
Install / Use
npx skills add reticlehq/reticle --skill fix-what-i-pointed-atInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of fix-what-i-pointed-at
fix-what-i-pointed-at scores 85/100 on our quality scale, 2521st of 4,702 Development & Engineering skills we index.
Its SKILL.md is 3.4 KB long, split into 5 sections with 3 code examples: a solid amount of guidance for an agent.
With 1,271 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 10 days ago, so fix-what-i-pointed-at is actively maintained.
- Our last check on 2026-11-04 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
fix-what-i-pointed-at compared with similar skills
All 4 of these similar skills score higher than fix-what-i-pointed-at; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| fix-what-i-pointed-at (this skill)by reticlehq | 85 | 1.3k | 10d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
Frequently asked questions
- How do I install fix-what-i-pointed-at?
- Run
npx skills add reticlehq/reticle --skill fix-what-i-pointed-at. The install tabs above show the steps for each supported agent. - Which AI agents does fix-what-i-pointed-at work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is fix-what-i-pointed-at safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is fix-what-i-pointed-at still maintained?
- The repository was last updated 10 days ago, so fix-what-i-pointed-at is actively maintained.
Skill content
View source on GitHubname: fix-what-i-pointed-at description: 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. license: Apache-2.0 metadata: version: 3.5.0 homepage: https://www.reticle.sh repository: https://github.com/reticlehq/reticle
The human pointed at the bug. Go fix it.
"The spacing on that card is wrong" is unactionable in chat and precise in the app. Reticle's running app has a Flag a bug control: the human clicks it, points at an element, and types what is wrong. Each flag 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 installed? RETICLE_INSTALL_SOURCE=npx_skill npx @reticlehq/server@latest init, then the install-and-verify skill.
Drain the marks
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.
The loop
- Read the marks. Group them if several point at the same file: one edit often answers three.
- Open
source.fileatsource.line. This is the whole point: no hunting for which component rendered that button. - Fix what the
noteasks for. If the note is ambiguous, the element label and its source usually disambiguate it. Ask the human only when they genuinely do not. - Verify in the app, do not eyeball it. Re-drive the affected control with
reticle_act_and_waitand name the consequence, orreticle_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. - Resolve it:
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.
When you cannot fix one
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.
Report back in their vocabulary
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".
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
