Skyelight

Workspaces you can reach, with the role you hold in each, and who you are. Use when you do not know what exists yet, to find which workspace a project belongs to, or to learn your own user id.

{
  "type": "object",
  "properties": {}
}

Projects you can reach, newest activity first, across every workspace unless one is named. Start here when no project is bound — `list_items` needs a project id and this is where one comes from.

{
  "type": "object",
  "properties": {
    "workspaceId": {
      "type": "string",
      "description": "Narrow to one workspace. Optional."
    }
  }
}

List feedback items (bugs, ideas, comments) people left on a Skyelight project. Returns a summary of the project plus matching items. Start here to see what is outstanding. An item's hand-off (investigate, plan, fix) is set by the team and binding: on investigate or plan, reply on the thread and change no code.

{
  "type": "object",
  "properties": {
    "projectId": {
      "type": "string",
      "description": "Project to read. Optional when a project is bound or the workspace has only one; otherwise the error lists the projects and their ids."
    },
    "page": {
      "type": "string",
      "description": "Only items on one page, e.g. \"/checkout\"."
    },
    "type": {
      "type": "string",
      "description": "Item type, e.g. \"bug\", \"idea\", \"feedback\"."
    },
    "status": {
      "type": "string",
      "enum": [
        "open",
        "deferred",
        "resolved"
      ],
      "description": "Defaults to everything. \"deferred\" is work someone put off until later — outstanding, but deliberately not now."
    },
    "assignee": {
      "type": "string",
      "description": "A user id, \"me\" for whoever this connection belongs to, or \"none\" for unassigned items."
    },
    "task": {
      "type": "string",
      "enum": [
        "investigate",
        "plan",
        "fix",
        "none"
      ],
      "description": "Only items a person handed to an agent with this task (Hand off in the app), or \"none\" for items with no hand-off. Combine with assignee to find your own. Investigate and plan mean reply on the thread with no code changes; fix means make the change."
    },
    "limit": {
      "type": "number",
      "description": "Max items (default 50)."
    }
  }
}

Find items whose thread mentions some text. Searches replies as well as the original message, so an item someone already diagnosed in a reply still turns up.

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Text to look for."
    },
    "projectId": {
      "type": "string",
      "description": "Project to search. Optional when a project is bound or the workspace has only one; otherwise the error lists the projects and their ids."
    },
    "status": {
      "type": "string",
      "enum": [
        "open",
        "deferred",
        "resolved"
      ]
    },
    "limit": {
      "type": "number"
    }
  },
  "required": [
    "query"
  ]
}

Report back on an item: what you found, what you changed, a link to the PR. Posts as a reply on the thread the feedback was left on, so the person who reported it sees the answer where they asked. Use this when you finish work on an item, and when you get stuck.

{
  "type": "object",
  "properties": {
    "itemId": {
      "type": "string",
      "description": "Item id from list_items."
    },
    "body": {
      "type": "string",
      "description": "What you found or changed, in plain language for the person who reported it."
    },
    "mentions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "People to notify, by name, email or id from list_members (\"me\" is you). Write @Name in the body where you mention them."
    },
    "links": {
      "type": "array",
      "description": "Optional links — a PR, a commit, a deploy.",
      "items": {
        "type": "object",
        "properties": {
          "label": {
            "type": "string"
          },
          "url": {
            "type": "string"
          }
        },
        "required": [
          "url"
        ]
      }
    }
  },
  "required": [
    "itemId",
    "body"
  ]
}

Open a new thread on a page, as the person whose connection you are using. Only available on a person's own connection — an agent reporting what it found or changed uses post_update on the thread it was working, so the answer lands where the question was asked.

{
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Full URL of the page this is about."
    },
    "body": {
      "type": "string",
      "description": "What you want to say."
    },
    "selector": {
      "type": "string",
      "description": "CSS selector for the element, if there is one."
    },
    "projectId": {
      "type": "string",
      "description": "Optional if a project is bound."
    },
    "pageTitle": {
      "type": "string"
    },
    "mentions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "People to notify, by name, email or id from list_members (\"me\" is you). Write @Name in the body where you mention them."
    },
    "assignee": {
      "type": "string",
      "description": "Who should take it: a name, email or id from list_members, or \"me\"."
    }
  },
  "required": [
    "url",
    "body"
  ]
}

Share something with Skyelight for review, and get a link people can pin feedback on. Two ways: - code: one file Skyelight hosts at its own link with the review badge on it. A whole HTML page, or one React component with an export default (Tailwind classes and npm imports work; local imports such as @/components do not). For Claude prototypes, v0 snippets and single pages. Publishing again with the same prototypeId, or the same name in the same project, makes a new version at the same link. - url: an app already deployed (a Lovable, v0, Bolt or Vercel project: anything with more than one file). Adds its address to the project's Review Links and returns a script tag to add to the app's <head> (index.html, or the root layout); add it and redeploy. Owners and admins. Returns the share link and the project link; give both to the person. A hosted link is public to anyone who has it.

{
  "type": "object",
  "properties": {
    "code": {
      "type": "string",
      "description": "For Skyelight to host: the complete file, never a summary or an excerpt. Or give url."
    },
    "url": {
      "type": "string",
      "description": "Where the app is deployed, e.g. https://my-app.lovable.app. Or give code."
    },
    "name": {
      "type": "string",
      "description": "What it is, in a few words. Names the hosted link and, when no project is given, a new project."
    },
    "kind": {
      "type": "string",
      "enum": [
        "html",
        "react"
      ],
      "description": "With code; worked out from it when left out."
    },
    "projectId": {
      "type": "string",
      "description": "Optional: the project to put it in. Left out, a new project is made for it."
    },
    "prototypeId": {
      "type": "string",
      "description": "With code: to publish a new version of a prototype published before."
    },
    "workspaceId": {
      "type": "string",
      "description": "When you are in more than one workspace and give no project, from list_workspaces."
    },
    "source": {
      "type": "string",
      "description": "With code: where it was made, shown as its logo in Skyelight: \"claude\", \"claude-code\", \"openai\" (ChatGPT), \"cursor\", \"windsurf\", \"v0\", \"lovable\" or \"other\". Name yourself."
    }
  }
}

The people in a workspace: name, email, role and id. Call it when you are asked to tell, ask or hand something to someone by name, then pass their name or id to assign, or in mentions on create_item or post_update.

{
  "type": "object",
  "properties": {
    "projectId": {
      "type": "string",
      "description": "Optional if a project is bound."
    },
    "workspaceId": {
      "type": "string",
      "description": "Instead of a project, from list_workspaces."
    }
  }
}

Hand an item to a person, who is notified the way an assignment in the app notifies them. Pass null as the assignee to unassign it. Only owners, admins and collaborators can assign; a resolved item has to be reopened first.

{
  "type": "object",
  "properties": {
    "itemId": {
      "type": "string",
      "description": "Item id from list_items."
    },
    "assignee": {
      "type": [
        "string",
        "null"
      ],
      "description": "A name, email or id from list_members, \"me\", or null to unassign."
    }
  },
  "required": [
    "itemId",
    "assignee"
  ]
}

Move an item to open, deferred or resolved. Use it to close the loop after you have fixed something and said so — post_update first, so the person who reported it reads what changed, then set_status. "deferred" is for work that is real but not now.

{
  "type": "object",
  "properties": {
    "itemId": {
      "type": "string",
      "description": "Item id from list_items."
    },
    "status": {
      "type": "string",
      "enum": [
        "open",
        "deferred",
        "resolved"
      ]
    }
  },
  "required": [
    "itemId",
    "status"
  ]
}

Everything needed to work one item: the whole thread in order, the page and URL it is on, the anchor identifying the element the person pointed at, and the pictures — what the page looked like when it was pinned, plus anything people attached — returned as images you can look at rather than links you cannot.

{
  "type": "object",
  "properties": {
    "itemId": {
      "type": "string",
      "description": "Item id from list_items."
    }
  },
  "required": [
    "itemId"
  ]
}

Everything needed to write an accurate project review or hand-off document: the shape of the work, every resolved thread and how it ended, what was deferred and why, what is still open, and the longest conversations quoted in full, which is where decisions were made. Every entry carries its item id, so each claim in your document can be traced back to its thread. Quote; do not invent outcomes the threads do not state.

{
  "type": "object",
  "properties": {
    "projectId": {
      "type": "string",
      "description": "Project to review. Optional if a project is bound."
    },
    "section": {
      "type": "string",
      "enum": [
        "resolved",
        "deferred",
        "open",
        "discussions"
      ],
      "description": "Omit for the overview (all counts, first rows of each section). Name one to read it in full, a page at a time."
    },
    "offset": {
      "type": "number",
      "description": "With section: where to start, from the previous result's 'more' line."
    }
  }
}

What changed on a project since you last looked: new threads, new replies grouped by thread, what was resolved or deferred, and what was assigned to you or mentioned you. Use when the user asks what has changed on a project since they last checked. Without `since` it reads from their bookmark and moves it forward; with `since` it reads that window and leaves the bookmark alone.

{
  "type": "object",
  "properties": {
    "projectId": {
      "type": "string",
      "description": "Optional if a project is bound."
    },
    "since": {
      "type": "string",
      "description": "Optional. A date or time (\"2026-09-01\", an ISO time) to read from instead of your bookmark."
    }
  }
}

Feedback by the code that rendered it, from the file and line the Skyelight build plugin stamps on each element. Pass a file (a path or just its name) or a component to see every thread about it before you edit it; pass neither to get the hot spots, every stamped file ranked by outstanding feedback.

{
  "type": "object",
  "properties": {
    "projectId": {
      "type": "string",
      "description": "Optional if a project is bound."
    },
    "file": {
      "type": "string",
      "description": "A source path or file name, e.g. \"src/components/PricingTable.tsx\" or \"PricingTable.tsx\"."
    },
    "line": {
      "type": "number",
      "description": "Optional. Threads nearest this line come first."
    },
    "component": {
      "type": "string",
      "description": "A component name, e.g. \"PricingTable\"."
    },
    "status": {
      "type": "string",
      "enum": [
        "open",
        "deferred",
        "resolved"
      ]
    },
    "limit": {
      "type": "number"
    }
  }
}

Has this already been reported? Pass the text you are about to report (and the page, if you know it) before create_item, or an itemId to find what an existing thread duplicates. Returns likely matches with why each matched: shared words, same page, same element, same source file. If two are the same problem, merge_items folds one into the other.

{
  "type": "object",
  "properties": {
    "projectId": {
      "type": "string",
      "description": "Optional if a project is bound or itemId is given."
    },
    "text": {
      "type": "string",
      "description": "What someone is about to report."
    },
    "itemId": {
      "type": "string",
      "description": "Instead of text: find duplicates of this item."
    },
    "page": {
      "type": "string",
      "description": "Optional. A page path or URL, e.g. \"/checkout\"."
    },
    "selector": {
      "type": "string",
      "description": "Optional. CSS selector of the element."
    },
    "includeResolved": {
      "type": "boolean",
      "description": "Default true: a resolved match may mean it came back. false to skip them."
    },
    "limit": {
      "type": "number",
      "description": "Max matches (default 5)."
    }
  }
}

Fold duplicate items into one, the way merging works in the app: the duplicates leave the list and count as extra reports on the item they were merged into. Use it only when find_similar and the threads themselves show they are the same problem. Owners, admins and collaborators can merge.

{
  "type": "object",
  "properties": {
    "itemId": {
      "type": "string",
      "description": "The item to keep. The others fold into it."
    },
    "duplicateIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Items that report the same problem."
    }
  },
  "required": [
    "itemId",
    "duplicateIds"
  ]
}

The decisions a project made in its threads, quoted: every thread resolved or deferred after a discussion, with the conversation, plus types people corrected and where outcomes keep recurring. Also returns the project's existing rules, so you can tell what is new. Use it to write a decision log, or to find rules worth keeping with save_rule.

{
  "type": "object",
  "properties": {
    "projectId": {
      "type": "string",
      "description": "Optional if a project is bound."
    },
    "since": {
      "type": "string",
      "description": "Optional. Only decisions after this date (\"2026-09-01\")."
    },
    "limit": {
      "type": "number",
      "description": "Decisions per page (default 15, at most 30)."
    },
    "offset": {
      "type": "number",
      "description": "Where to start, from the previous result's 'more' line."
    }
  }
}

Keep a rule the team agreed on ("sentence case in every button", "the brand gray stays, do not raise contrast bugs on it") in the project's context, under Rules learned. The classifier reads that context, and every agent reads it through decision_log, so it shapes future threads. Cite the threads it came from. Workspace owners and admins only; confirm with the person before saving.

{
  "type": "object",
  "properties": {
    "projectId": {
      "type": "string",
      "description": "Optional if a project is bound."
    },
    "rule": {
      "type": "string",
      "description": "The rule, in one plain sentence."
    },
    "sourceItemIds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Items the rule came from."
    }
  },
  "required": [
    "rule"
  ]
}