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 analysis instructions, reference material, and result shape. Run it against a board and you get a batch of insights, anchored to nodes and edges.

Default skills ship with the platform. Skills you author are scoped to your org, where domain knowledge belongs: compliance, cloud, and naming conventions.

The Insight Skills screen

Manage the catalogue in Settings → Insight Skills.

An empty catalogue starts with Load Default Skills. Create Skill opens the form for one of your own.

Expand

1. 1

   Instructions are the skill

   The primary prompt an analysis follows — be specific about your stack, or the insights come back vague.

2. 2

   Category files it in the catalogue

   Keeps a browsable list browsable as the catalogue grows past a screenful.

3. 3

   Results mode decides the next analysis

   Replace keeps only the latest batch; Append stores the new batch beside the old ones so you can read a trend.

Authoring one

The form asks for a name, slug, and the parts that shape an analysis:

• Instructions: the primary prompt the analysis follows. This is the skill. Be specific about your stack and what you consider a problem, because vague instructions produce vague insights.
• Category: how the skill files itself in the catalogue, so a browsable list stays browsable as it grows.
• References: named documents an analysis reads on demand, such as your team's security standards, a cloud well-architected checklist, or an internal ADR.
• Results mode: Replace or Append, below.
• Colour and estimated duration: the accent on the skill's chip, and the "this takes about five minutes" hint someone sees before they start one.

Instructions can include template variables for detected stacks, languages, archetypes, and the current board, so one skill can adapt per board.

Results mode decides what a second analysis does to the first:

Use Replace for current state and Append for trends.

Replace only takes over on boards covered by the new analysis: the board you ran it against and any board where its trails start. A board reached by an earlier run keeps its existing batch if the new run does not reach it.

What an analysis hands back

An analysis returns a batch of insights attached to elements. Each insight has a priority and a signal: risk, opportunity, strength, or observation. Insights covers the signals.

Each insight can also carry a traced path, affected elements, and a suggested graph change with reasoning.

Running one

There are two ways to start an analysis:

• From chat. The choice sits on the new-thread panel, under Response Format. Start a thread with With Insights and ask your question. Chat matches a skill to it, or runs the one you name. See Chat.
• From a plugin. /insights in the code plugin or the connect plugin runs your workspace's skills from the coding session. No model provider is needed on the platform side.

The Insights Bar lists a board's insights on the canvas. It displays them; it does not start an analysis.

The review-status funnel

Every insight has a review status before the team acts on it:

Status is set per insight, not per batch — moving one insight from Draft to Approved doesn't touch the rest of the batch it arrived in. A person moves each one along the ladder, so machine-generated insights wait for judgment before anyone treats them as settled.

From an insight to an intent

An insight you agree with becomes an intent, with the analysis attached for developers. Insights covers delivery chips.

Publishing insights with a board

Publications can include insights, aspects, and skills. Include insights and stakeholders see signals on the elements they concern without an account or edit access. Publishing Boards covers the wizard.

What's next