Last updated October 13, 2026
On this page
Insight Skills
An insight skill defines what an analysis looks for, so "run the security review" means the same thing on every board.
What an insight skill is
A skill holds an analysis's instructions and reference material. Running it against a board produces a batch of insights, anchored to nodes and edges. Default skills ship with the platform; skills you author are scoped to your org.
The Insight Skills screen
Manage the catalogue in Settings → Insight Skills.
In an empty catalogue, Load Default Skills adds the shipped skills. Create Skill opens the form.
- 1
Instructions are the skill
The primary prompt an analysis follows. Be specific about your stack, or the insights come back vague.
- 2
Category files it in the catalogue
Groups skills so you can still browse the catalogue once it grows past a screenful.
Authoring one
Besides a name, a slug, the Instructions and the Category, the form takes:
- References: named documents an analysis reads on demand, such as your security standards or an internal ADR.
- Colour and estimated duration: the skill chip's accent, and the time hint shown before an analysis starts.
Instructions can include template variables for the board and its detected stacks, languages and archetypes, so one skill adapts to each board.
Each analysis adds a new batch beside the earlier ones and removes nothing. A plugin that runs again replaces only its own results. /insights replaces the batch it last pushed for that skill on that board, and each /discover replaces the previous one's insights. Only unreviewed insights are removed; one moved into review stays.
What an analysis hands back
Each insight has a priority and a signal: risk, opportunity, strength or observation (the four signals). It can also carry a traced path, its affected elements and a suggested graph change with its reasoning.
Running one
- From chat. Ask for an analysis, or use the Assess this board quick start on a new thread. ProvenMap matches a skill to your request, or runs the one you name. See Chat.
- From a plugin.
/insightsin the code plugin runs your workspace's skills from the coding session;/assessin the workspace plugin runs a structured review from your AI host. Neither needs a model provider on the platform side.
/discover in either plugin adds insights under the Architecture Highlights skill, and a bound Sentry project turns issues into draft insights every hour (every source). The Insights Bar on the canvas lists insights but doesn't start an analysis.
The review-status funnel
Every insight carries a review status that says whether it's ready to act on:
A person sets the status of each insight; moving one doesn't change the rest of its batch.
From an insight to a work item
Turn an insight you agree with into a work item, with the analysis attached for developers. Insights covers the delivery chips.
Publishing insights with a board
A publication that includes insights shows stakeholders the signals on the elements they concern, with no account or edit access. Publishing Boards covers the wizard.
What's next
Insights
The concept side — what an insight is, and how a batch reads on the board.
Chat
Where an analysis starts in the portal — ask, and it comes back as a batch of insights.
Work items
Where an approved insight goes next: reviewed, developer-ready work.
Connecting Sources
Ground your analyses in the repos and documents behind the board.

