Working with an agent

This page lists prompts for common tasks with a connected agent, and the tools each one runs. You don’t need to name tools in a prompt. Describe the result you want, and the agent chooses the tools.

Start a session by catching up

What’s new on the checkout project since I last looked?

whats_new returns new threads, new replies, threads resolved or deferred, and threads assigned to you or mentioning you. It reads from your bookmark on the project and moves the bookmark forward, so the next call starts where this one ended.

Clear what’s assigned to you

Work through the Skyelight items assigned to me. For each one, fix it, reply on the thread with what you changed and the PR link, then resolve it.

1. list_items with assignee: "me" lists the threads assigned to you.
2. get_item reads each thread, with the screenshot, the page, and the source location when the build is stamped by Skyelight Build.
3. The agent changes the code.
4. post_update replies on the thread, where the person who reported it can read it.
5. set_status resolves the thread, or defers it with the reason in the reply.

If the agent can’t fix a thread, it can use post_update to report what it found and leave the thread open.

Check a file before you edit it

Before you change PricingTable.tsx, is there any open feedback on it?

find_by_source lists every thread left on elements that the file rendered, nearest line first. Without a file name, it returns the files with the most open and deferred threads. Both need a build stamped by Skyelight Build.

Triage and clean up duplicates

Go through open items on the dashboard page and merge any that report the same problem.

find_similar scores likely duplicates and lists why each one matched. The agent reads the threads to confirm they report the same problem, and merge_items merges them into one. The thread you keep counts every report. See Duplicates.

To check for an existing thread before the agent creates one, include that in the prompt:

Report that the date picker overlaps the footer on /settings, unless someone already has.

Write a project review or decision log

Write a hand-off document for the marketing site project. Quote the threads and cite their ids.

project_review returns the counts, resolved threads and how they ended, deferred threads and the reasons given, open threads, and the longest conversations in full. decision_log returns what the team decided in its threads. Both tools quote the threads and include each thread’s ID, so you can check each statement in the document against its thread.

Keep a rule the team agreed on

The team keeps saying buttons use sentence case. Save that as a rule for this project, citing the threads.

save_rule adds the rule to the project context. Skyelight reads that context when it sets the type of new threads, and agents read the rules through decision_log. Only workspace owners and admins can save rules.

Review what the agent writes

Thread text comes from the people reviewing your app, and an agent can treat text it reads as instructions. A thread could ask the agent to save a rule, resolve other threads or change code it shouldn’t touch. Skyelight marks every tool as read-only or write, and most clients ask before they run a write tool. Read what the agent proposes before you approve it, especially calls to save_rule, merge_items and set_status.