Tools reference

Returns the workspaces you can reach, your role in each, and your user ID. A workspace where your role or the organization’s plan doesn’t include agent tools is listed with the reason. Takes no arguments.

Returns the projects you can reach, most recent activity first. Call it first when no project is bound.

Returns a summary of the project (totals, and counts by type and by page), then one row per thread. Each row shows the thread’s one-line summary when it has one. Merged duplicates are hidden and counted on the thread they were merged into.

list_items reads the 2,000 most recent threads in a project. When a project has more, the result says so.

Returns threads that mention a word or phrase. It searches replies as well as the first message, so it also finds threads where the match is only in a reply.

Returns everything needed to work on one thread:

• the first message and every reply, in order;
• the page and URL;
• the anchor that identifies the pinned element;
• the source file, line, component, commit and branch, when the site was built with Skyelight Build, and a link to the file when the project is linked to a repository;
• the screenshot taken when the thread was created, and any images people attached, as images the model can read;
• the Linear issue the thread was sent to, if any, and reaction counts;
• the agent task set when someone handed the thread off: investigate, plan or fix.

Each call returns up to 4 images, each up to 4 MB. The result names any image it skipped, with its link and the reason. If someone moved the pin to another element after the thread was created, the result says the screenshot and page context are from before the move. If the screenshot was deleted under the workspace’s retention setting, the result says so. See Anchoring, context and screenshots.

Returns the people in a workspace: name, email, role and user ID. Use it to find the person to assign or mention.

Posts a reply on a thread, as you. Use it when the work is done, or to report what the agent found when it is stuck.

The item must be a thread. You can’t reply to a reply.

Creates a new thread on a page, as you. Use it for a new finding, such as an audit result. To report on a thread the agent is already working on, use post_update.

Skyelight sets the type, writes a summary and sends notifications for the new thread, the same as for a thread created in the app.

Sets a thread to open, deferred or resolved. Post a reply with post_update first, so the person who reported it can read what changed. Use deferred for valid work that is postponed.

Assigns a thread to a person, or unassigns it. The assignee gets the same notification as for an assignment in the app.

A resolved thread must be reopened before you can assign it.

Returns what changed on a project since you last looked: new threads, new replies grouped by thread, threads resolved or deferred, and threads assigned to you or mentioning you. Call it at the start of a session.

Without since, whats_new reads from your bookmark on that project and moves the bookmark forward. Your first call looks back 7 days. With since, it reads from that time and leaves the bookmark where it is.

Returns what you need to write a project review or hand-off: counts and breakdowns, who took part, resolved threads and their last message, deferred threads and the reason given, open threads, and the longest conversations quoted in full. Every entry includes its item ID, so each statement in the document can be traced to its thread.

The overview returns every count and the first 25 rows of each section. A section returns 100 rows, or 5 conversations, per call. Each result ends with the call that fetches the next page.

Returns the decisions a project made in its threads, quoted: threads resolved or deferred after a discussion, with the last messages of each. It also returns types people corrected, outcomes that recur, and the project’s existing rules.

Adds a rule the team agreed on to the project context, under “Rules learned”, with who added it, the date and the threads it came from. Skyelight reads the project context when it sets a thread’s type, so a saved rule affects future threads. Agents read the rules through decision_log.

Only workspace owners and admins can save rules. Skyelight refuses an exact duplicate, and a rule that would take the project context past 20,000 characters.

Returns threads by the code that rendered the pinned element, using the file and line that Skyelight Build stamps on each element. Pass a file or a component to see every thread about it before you edit it. Pass neither to get the stamped files ranked by open and deferred threads.

find_by_source only finds threads left on builds stamped by Skyelight Build.

Returns existing threads that may report the same thing. Pass the text you are about to report, or an existing item. Each match lists why it matched: shared words, the same page, the same element or the same source file. Matching compares text and doesn’t call an AI model.

Merges duplicate threads into one. Each duplicate is hidden from thread lists and counts as an extra report on the thread you keep. Nothing is deleted.

All the threads must be in the same project, and they must be threads, not replies. A call takes up to 50 duplicates. If the thread you keep was itself merged into another thread, the duplicates go to that one. Returns merged (how many threads were merged) and canonicalId (the thread they went to). The tool is marked destructive, so most clients ask before running it, and a merge can’t be undone. See Duplicates.