← Plugin catalog
Business & Operations

Intelligo

Intelligo v4.0.0

Due Diligence Analysis

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 20, 2026. Package observed Nov 20, 2026.

View package source →

Description

From the marketplace listing

Intelligo brings risk intelligence into ChatGPT. Connect your Intelligo account to pull background checks, credit checks, and adverse-media and social-media screening into the conversation. Summarize a subject's findings and risk flags, compare reports to see what changed, search across your profiles for a name or keyword, and prepare due-diligence write-ups — grounded in your own Intelligo data. Sign-in is secured with OAuth, and ChatGPT only accesses data your account is permitted to see. Requires an Intelligo account.

Language: English · Automatically detected from descriptions.

What changed

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Files & skills

File archives

Plugin package28 files · 85.3 KBBrowse files →
Skill instructions
intelligo-compare-reports27.5 KB

View saved version →

---
name: intelligo-compare-reports
description: >-
  Compare Intelligo background-check reports and report what changed or
  what overlaps. Use this skill whenever the user wants to compare, diff, or
  cross-reference Intelligo reports or profiles — including "what changed since the
  last report", "refresh comparison", "compare this profile's new and old
  report", "what's common between these two profiles", "do these subjects share
  anything", or comparing every profile in an Intelligo project against each other.
  Trigger on phrases like "compare reports", "what's new in this refresh",
  "diff these profiles", "shared connections between profiles", "what did the
  upgrade add", "compare the two report levels", and on any request that names
  two or more Intelligo profiles/reports and asks how they relate. Three modes:
  REFRESH (same profile over time, same level), LEVEL CHANGE (same profile, two
  different report levels — upgrade or interim), and CROSS-PROFILE (two or more
  distinct profiles, including a whole project). Read-only — never writes back
  to Intelligo.
---

# Compare Intelligo Reports

Compare Intelligo background-check reports and explain — in plain
language, facts only — what changed or what overlaps. Picking the right *kind* of
comparison is the first decision, so start there.

## The three modes

**Refresh — same subject, same level, different points in time.** One profile, a
newer report and an older one at the same report level. Question: *what changed
since last time?* Same person/entity and same coverage scope, so you align records
one-to-one and report **transitions** — findings newly present, findings gone,
flags escalated or cleared, new dated hits since the prior report.

**Level Change — same subject, two different report levels.** One profile, two
reports at different levels (e.g. Now → Advantage, Advantage L1 → Advantage L2/3).
This covers both **upgrades** (moving to a higher level for deeper coverage) and
**interim runs** (running a lower level to cover a time gap before the deal closes).
Question: *what did the level change add or remove — in coverage and in findings?*
Coverage scope changed, so findings can appear or disappear simply because the new
level covers more (or less) — not because the subject changed. You must separate
coverage-driven differences from genuine finding changes, and always run a coverage
diff via `compareCoverage`.

**Cross-profile — different subjects, compared as peers.** Two or more distinct
profiles (or every profile in a project). Question: *what do they share, and where
do they diverge?* No time axis — you compute **set intersection and difference**:
shared employers, addresses, associates, companies, legal entities, and what's
unique to each. Overlap is usually the signal the analyst wants (hidden or
undisclosed connections).

**Deciding which:**
- Same subject, same level → **Refresh**.
- Same subject, different levels → **Level Change** (see detection logic below).
- Different subjects → **Cross-profile**.
- A project, or "all profiles in X" → **Cross-profile**, N-way.

If genuinely ambiguous, state your inferred mode in one line and proceed — don't
stall on a question you can answer by checking whether the subject and level match.

This skill compares reports the user already has in mind or that live in a named
project. It is **not** the account-wide "who is connected to X" screening search —
that's a separate operation.

## Report scope — background checks by default

Intelligo profiles can hold several report types (background check, social media
analysis, credit check, others). **Compare background-check reports by default**;
when a profile or project has more than one type, pick the background check
without asking.

If the user explicitly asks for another type, don't silently ignore it and don't
refuse: tell them other types exist and that this skill is built around background
checks, then default to background checks unless they confirm they want th

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

intelligo-export-pdf5.92 KB

View saved version →

---
name: intelligo-export-pdf
description: >
  Guided PDF export from Intelligo — walks the user through scope and content options before calling exportPdf. 
  Trigger whenever the user wants to download, export, or get a PDF of a report or project in Intelligo, 
  or says things like "download this report", "export to PDF", "get me the PDF for this project", 
  "download all profiles", "export the report for [name]", or anything implying they want a PDF out of Intelligo.
  Always use this skill instead of calling exportPdf directly — it ensures the right scope and options are chosen first.
---

# Intelligo PDF Export — Guided Flow

Your job is to guide the user to a correctly configured `exportPdf` call by asking focused, sequential questions. Don't overwhelm them — ask one topic at a time, in order.

---

## Step 1 — Determine the starting point

Figure out whether the user is starting from a **profile** or a **project**. This is usually clear from context (what they mentioned, what's on screen, prior conversation). If it's ambiguous, ask: "Are you starting from a specific profile, or from a project?"

---

## Step 2 — Scope selection

The scope question differs based on the starting point.

### If starting from a profile:

**Default assumption: export just this profile.** Do NOT ask about the whole project unless the user has explicitly indicated they want multiple reports (e.g., "all reports in this project", "export everything", "download all profiles").

- **Single profile (default)** → pass `profileIds: [<this profile's id>]`. Skip to Step 3.
- **Multiple profiles from the same project (only if user explicitly asked)** → treat this as a project-level export. Resolve the `projectId`, then go to Step 2b.

### If starting from a project:

Ask: "Do you want all profiles in the project, or just one specific profile?"

- **All profiles** → you'll use `projectId`. Then ask the format question (Step 2b).
- **A specific profile** → ask which one (name or ID), resolve to `profileIds: [<id>]`. Skip to Step 3.

### Step 2b — Format (project-level exports only)

When exporting a whole project, ask:
"Do you want all profiles merged into **one PDF**, or as **separate PDFs in a zip**?"

- One PDF → `exportMode: SINGLE_PDF`
- Separate files → `exportMode: MULTI_PDF`

---

## Step 3 — Content flags

Always show the user all options with their defaults and ask them to confirm or change before exporting. Never silently apply defaults.

The defaults differ depending on the export scope:

**Single profile export:**
> Here are the export options — these match the Intelligo defaults. Let me know if you want to change anything:
> - ✅ **Include user comments** (on)
> - ✅ **Include links to view report in Intelligo** (on)
> - ✅ **Include links to original sources** (on)
> - ☐ **Include flag review statuses / action items** (off)
> - ☐ **Include historical versions of the reports** (off)

**Project-level export:**
> Here are the export options — these match the Intelligo defaults. Let me know if you want to change anything:
> - ✅ **Include user comments** (on)
> - ☐ **Include links to view report in Intelligo** (off)
> - ✅ **Include links to original sources** (on)
> - ☐ **Include flag review statuses / action items** (off)
> - ☐ **Include historical versions of the reports** (off)

Wait for the user to confirm or adjust. Map their answer to the five flags:
- `includeComments`
- `includeLinks`
- `includeSources`
- `includeActionItems`
- `includeAllVersions`

---

## Step 4 — Storage preference

Before calling the export, ask:

> Once the PDF is ready, would you like to:
> - **Just get a download link** (expires in ~30 minutes)
> - **Save it somewhere** — e.g., Google Drive, email it, upload to Slack

If they want to save it somewhere, note the destination so you can act on it after the export completes. If they just want the link, proceed.

---

## Step 5 — Confirm and export

Before calling the tool, give a one-line summary:

> Exporting [scope 

Preview of the first 4,000 characters. Read full instructions →

intelligo-legal-explainer7.32 KB

View saved version →

---
name: intelligo-legal-explainer
description: >
  Explains legal and regulatory findings from Intelligo reports — individuals and companies.
  Four layers: definition, jurisdiction/issuing body context, pattern assessment, internet research.
  Trigger on: "explain this finding", "what does this mean", "is this serious", "is this common in [country]",
  "what does the internet say", "is this a red flag", "explain this lawsuit", "what is a lien",
  "what is a bankruptcy filing", "explain this sanction", "what does this watchlist mean",
  "is this PEP significant", "what does SECO mean", "what is OFAC", "what does CAATSA listing mean",
  "what is OFSI", "explain this enforcement action", "what does sanctions list mean",
  "I want to know more on the regulatory findings", "how significant is this watchlist hit",
  "what does this designation mean".
  Do NOT auto-trigger. Do NOT mix Intelligo data with internet data.
---

# Intelligo Legal & Regulatory Explainer

## Purpose
Explain and contextualize legal and regulatory findings from Intelligo reports.
Covers individuals and companies. User may need one layer or all four — only present what is relevant and supported.

## Scope
**Legal findings:** judgments, liens, bankruptcies, garnishments, civil suits, criminal charges, court orders, debt recovery actions
**Regulatory findings:** sanctions lists (OFAC, SECO, OFSI, EU, UN, CAATSA, etc.), watchlist hits, PEP designations, enforcement actions, debarment, regulatory bans, disqualifications

---

## Four Layers

### Layer 1 — Definition
What is this type of finding?

**Legal terms:**
- For **US findings**: Claude may define standard legal terms without a citation. Use plain language.
- For **non-US findings**: If the term or implications differ from the US equivalent, a citation is required. If the meaning is genuinely universal, no citation needed. When in doubt, cite.

**Regulatory terms:**
- Claude may define well-established regulatory bodies and list types (OFAC, OFSI, EU sanctions, UN sanctions, PEP) without a citation — these are internationally standardized.
- For lesser-known or country-specific bodies (e.g. SECO, CAATSA oligarch list), provide a plain language explanation. Citation required if making claims about what listing on that specific list implies legally or operationally.
- Explain what the designation means practically: what does being on this list mean for the subject, their counterparties, and financial relationships?
- If Claude is not certain of the definition — say so. Do not guess.

### Layer 2 — Jurisdiction & Issuing Body Context
What does this finding mean given where it comes from?

- For legal findings: is this type of case routine or significant in this jurisdiction?
- For regulatory findings: what is the authority and reach of the issuing body? Is this a primary sanctions list, secondary, or advisory? What are the practical consequences of this designation?
- Are there geopolitical or systemic factors that affect how seriously this should be taken?
- **Citation required** for any jurisdiction-specific or body-specific claim.
- If no reliable source is found — say so. Do not present the insight.

### Layer 3 — Pattern Assessment
Does this finding stand alone or reflect a pattern?

- Look across all legal and regulatory findings mentioned in the conversation/report
- Assess: single incident vs. repeated behavior vs. cross-jurisdictional pattern vs. escalating designations
- Note if findings conflict with the subject's professional role
- For regulatory findings: multiple sanctions lists from different jurisdictions is a stronger signal than a single listing
- This layer uses only what is present in the conversation — no internet research needed
- If there is only one finding and no pattern to assess — skip this layer entirely

### Layer 4 — Internet Research
What do publicly available internet sources say about this specific finding or subject?

**Strict rules — no exceptions:**
- Every claim must hav

Preview of the first 4,000 characters. Read full instructions →

intelligo-prep-committee-deck8.9 KB

View saved version →

---
name: intelligo-prep-committee-deck
description: Convert Intelligo background-check findings into Investment Committee (IC) ready materials — narrative summaries, slide-ready snippets, polished PDFs, or PPTX decks. Works at any scope — single subject report, full deal/project rollup, or hybrid (project overview with one subject in depth). Use whenever an analyst asks to "prepare for IC", "summarize the deal for committee", "roll up findings for project X", "build IC slides", "make an IC summary", "format Intelligo findings", "create a project one-pager", "write the IC memo section", or wants to share Intelligo output with partners, board, GC, or risk committee. Different funds have very different IC styles, so this skill always conducts a short intake before generating output. Trigger generously — analysts often describe the destination (their IC, their deal, their project) rather than naming the format.
---

# IC Formatter

## What this skill does

Intelligo findings live inside the platform in a structure optimized for review. Investment Committees want something different: a tight summary, the right level of detail for their audience, and findings framed against what the subject disclosed. Analysts currently copy-paste, screenshot, and hand-rewrite Intelligo output to make it IC-ready. This skill replaces that manual work.

Two things vary across uses and the skill handles both:

1. **Scope** — single subject, full project rollup, or hybrid (project overview + deep dive on specific subjects). Scope changes what data is pulled and how the output is structured.
2. **Style** — even within the same firm type, ICs behave very differently. What actually predicts format is **who reads it** and **what they need to see first**. Intake asks behavioral questions, not "what kind of firm are you?".

## Core flow

1. **Establish scope** — single subject, project, or hybrid. Identify which.
2. **Offer the analyst to share an example** (optional) — a screenshot, prior deck, or sample memo. If provided, infer style and short-circuit later questions.
3. **Pull Intelligo data, including automatic internal comparisons** — fetch the project, subjects, reports, flags, notes, sources. Automatically also compute a refresh-delta if a prior report exists, and cross-subject patterns for project/hybrid scope. These are Intelligo-internal and free — included in the data layer; rendered only if they surface something interesting.
4. **Profile the IC** — ask the remaining intake questions (see `references/intake-flow.md`).
5. **Offer external enrichment** (optional, Q4) — recent news, public filings, internal CRM/docs, industry context. Non-Intelligo sources only. Probe what's available before offering.
6. **Pick a flavor** — map intake answers to a flavor (see `references/flavors.md`).
7. **Generate output** — default is the inline snippet canvas via `show_widget`. PDF, PPTX, or downloadable HTML on request. Always preview in chat first.

## Resolving the subject / project in Intelligo

Use the shared **`references/profile-resolution.md`** reference for the full resolution logic — context reuse, parallel profile/project search, disambiguation, duplicate detection, suffix handling, and the rules for combining profiles. That reference is shared across all Intelligo skills; this skill follows it.

What's specific to this skill on top of the shared logic:

- When the analyst's intent is project rollup or hybrid (Q0), prefer a project match if both a profile and a project are found under the same name. Confirm with the analyst when ambiguous.
- For hybrid scope, after resolving the project, ask which subject(s) to deep-dive — show the project's profile list and let the analyst pick.

**If Intelligo MCP isn't available at all** (no Intelligo tools loaded in the session), don't try to resolve. Offer three fallbacks: paste report content as text, attach a PDF export, or describe findings from memory (top-line flavors only). Then proceed with intake.

## Pul

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 11 — file references are metadata, not package contents.

intelligo-profile-summary32.7 KB

View saved version →

---
name: intelligo-profile-summary
description: >-
  High-level factual summary of one Intelligo profile — background check, credit check, and
  social media analysis, with executive summary, red/yellow flags, and key findings. Summarizes one
  profile (person or company), not a project; if the query is ambiguous it searches profiles and
  projects, and hands a project off to the project-summary skill. Use whenever the user wants a
  summary, recap, key takeaways, risk read, red flags, or major risks on a person or company in due
  diligence — even without saying "Intelligo." Offers four selectable views (executive summary, flag
  count, flags + findings, per-tab breakdown) and asks which when unspecified. Triggers: "summarize
  X", "red flags on X", "what did we find on X", "how many flags on X", "exec summary on X", "break X
  down by tab". Do NOT use for web research, monitoring, action items, or project-level summaries.
---

# Intelligo Profile Summary

Turn an Intelligo **profile** into a high-level, factual summary the user can read in under a minute.

## Data model (overview)

Hierarchy: `Project → Profile → Report → Card → Flag`. Sources link to Cards. Linked Notes attach to Cards. This hierarchy is **conceptual** — `Get_report_content` returns Report, Cards, and Flags together in one response (see Connector tools).

**Profile** is the DD subject (Person or Company shape — see tool specs for field-level detail).

**Report** belongs to a profile, carries a product type (background check, credit check, social media analysis), a status, and a format (card-based for BG checks, PDF for credit / social media). Multiple reports of the same product type can exist on a profile, distinguished by creation time; the skill picks among them by status (see Step 2).

**Card** is a finding item inside a card-based report. Each card has a type (which determines its content fields — professional, education, news, legal, etc.). Cards do **not** have a reliable generic description field — the skill renders type-specific fields instead.

**Flag** is a separate object linked from a Card. Surfacing a flag means showing flag.name + flag.description alongside the card it points to.

### Report status — what's summarizable

| Status | Usable? |
|---|---|
| Pending consent | No — falls back to older complete report if exists, otherwise skip |
| In progress | No — same fallback as Pending consent |
| Preliminary | Yes, with prominent caveat (not human-verified) |
| Ready | Yes, normal |
| Reviewed | Yes, normal (equivalent to Ready for summary purposes) |

### Report format — what the skill can do

| Product | Format | Skill can read content? |
|---|---|---|
| Background Check | Card-based | Yes — iterates cards, renders by type |
| Credit Check | PDF | Connector returns metadata only (flag counts, optional exec summary, link). The document text is readable **only when the PDF is uploaded/available** — see PDF content access below |
| Social Media Analysis | PDF | Same as Credit Check |

#### PDF content access

`Get_report_content` returns only the PDF's metadata (URL, flag counts, optional exec summary) — never the document text. But the skill **can** read and summarize a PDF when the file itself is available to it (the user uploaded the report into the conversation, or it's otherwise readable):

1. **PDF content available** → read it and answer or summarize normally, exactly like any other source. Don't limit yourself to metadata.
2. **Not available, and the user wants PDF detail** → ask the user to upload the report PDF.
3. **Still unavailable** → do **not** continue with the PDF: never guess or fabricate its content. Fall back to the connector metadata (flag counts + link) and tell the user the content isn't available.

The skill never invents PDF content.

### Summary-text source — one rule, all formats

1. If the report carries an analyst-written executive summary → use it (verbatim or near-verbatim; light editing for length OK).
2. Else, 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

intelligo-project-summary20.7 KB

View saved version →

---
name: intelligo-project-summary
description: >-
  Deal/project-level summary across every profile in an Intelligo project — a synthesized
  project executive summary plus a short risk summary per subject (mini exec summary + red/yellow
  flags). Summarizes a whole investment (a project with multiple profiles), not a single subject; if
  the query is ambiguous it searches projects and profiles and hands a single profile off to the
  profile-summary skill. Can return the whole summary or just one part on request — the subject
  roster, the project overview, or the per-subject risk summaries. Triggers: "summarize the X
  project/investment/deal", "roll up X", "risk across the X deal", "red flags across X", "what did we
  find on the X investment", "what should I know about the X deal", "who's in the X deal", "list the
  subjects/companies in X", "the gist of the X deal", "break the X deal down by subject". Do NOT use
  for a single person/company (that's profile-summary), web research, monitoring, action items, or
  comparisons.
---

# Intelligo Project Summary

Turn an Intelligo **project** (an investment holding multiple subjects) into a deal-level summary the user can read quickly: a short synthesized project overview, then a per-subject risk summary.

This skill is the project-level counterpart to **intelligo-profile-summary**. It reuses that skill's report selection and per-profile rendering, then composes the results into a deal-level view. Read profile-summary's SKILL.md alongside this one — the per-subject logic lives there and is not duplicated here.

## Data model (overview)

Hierarchy: `Project → Profile → Report → Card → Flag`. A **Project** is the investment (the deal). It holds one or more **Profiles** (the DD subjects — persons and/or companies). Everything below the Profile level (Reports, Cards, Flags, statuses, formats, PDF handling) is exactly as defined in **intelligo-profile-summary** — this skill does not redefine it. What it adds on top is project resolution, full-roster enumeration, scale handling, and roll-up composition (Steps 1–5).

### In/out of scope (inherited from profile-summary)

- **In scope:** the Project (for ID), every Profile under it, each profile's DD reports (most recent per product), their cards, flags, and linked notes.
- **Out of scope:** Monitoring, all Action items, Comments — same exclusions as profile-summary.
- **No opinions:** no investment recommendations, no risk verdicts, no "this is the deal-breaker" / ranking which subject matters most. Severity ordering (red → yellow) and "this subject carries flags, this one is clean" are the only allowed prioritization signals. The skill reports what was flagged; it does not advise whether to do the deal.

## Connector tools

Same connector as profile-summary: `Get_projects`, `Get_profiles`, `Get_report_content`. This skill leans on `Get_projects` for resolution and the **full project roster**, then drops into the profile-summary flow per subject.

### `Get_projects` — resolve a project name; returns project detail + full profile roster

Given a query (project/deal name, partial name, or company that maps to a deal), return matching project candidates. Each candidate carries:

- Enough identifying metadata to disambiguate one project from another with the same or similar name — e.g. project name, an internal id/code if present, created date, and the count of profiles under it. The skill surfaces these when more than one project matches (see Step 1).
- The project's **full profile list** — every subject attached to the project (id, name, person/company type, and the minimum identifying fields), not just a preview. This is what the roll-up iterates. (The profile-summary skill only uses the short preview; this skill requires the full list.)

> **Connector dependency:** this skill assumes `Get_projects` can return the complete profile roster for a project. If only a preview is returned, the skill cannot guarantee completeness — in that cas

Preview of the first 4,000 characters. Read full instructions →

intelligo-risk-trends15.9 KB

View saved version →

---
name: intelligo-risk-trends
description: >-
  Search and surface RISK TRENDS across an Intelligo client's own
  background-check reports — for Intelligo clients, including analysts. Patterns
  across many reports, not one. Use when the user wants: flags trending over time
  by level (Red/Yellow/Info); flags broken down by theme or specific finding;
  newly emerging or spiking risks vs a prior period; comparisons across reports,
  subjects, or products; or a CROSS-PROFILE search for any entity, keyword, or
  attribute (e.g. "which profiles mention China", "anyone in the Epstein files").
  Flag categories are NOT a stored field — derive meaning from each flag's
  finding content, not its config name. Trigger on "risk trends",
  "flag trends", "what risks are
  increasing", "break our flags down", "which reports mention X", "search across
  profiles for…", even when Intelligo isn't named. Pulls from Intelligo via
  get_projects / get_profiles / get_report_content (plus aggregation and search
  tools when available); returns a chat summary + table, charts, or a dashboard.
---

# Intelligo Risk Trends

## What this skill is for

Intelligo users normally look at one report at a time. This skill works across
**many** reports at once to answer questions like "what's changing?", "where is
risk concentrated?", and "which of our subjects touch X?". The user is an
**Intelligo client** (some are analysts, some are not) working within **their own
organization's** reports only. Write for a non-specialist: explain findings in
plain language and never surface internal config codes (see flag naming below).

> **Out of scope:** comparing or benchmarking *against other organizations* is a
> separate skill. This skill never spans orgs — stay within the user's own data.

Five intents this skill serves. Most real questions are one of these (sometimes
two combined):

1. **Volume over time** — how flags (by level: Red / Yellow / Info) and, when asked, findings overall change across a date range.
2. **By theme / specific finding** — group findings (flagged or not) into plain-language themes (e.g. "adverse media", "bankruptcy", "watchlist match") by reading the finding content. There is **no stored category field** — derive themes from content, not the config name.
3. **Emerging / new risks** — themes or findings newly appearing or spiking versus a prior comparable period — including findings the system never flagged.
4. **Across reports / subjects / products** — within the org, compare or rank flags/findings across reports, subjects, products, or entity type.
5. **Cross-profile search** — find every profile/report whose findings mention a specific entity, keyword, location, or attribute (a person, company, country, sanction program, event…) — searching all findings, not just flagged ones.

## Intelligo data model (read this first)

Intelligo exposes data through an MCP connector. The three tools you can rely on
today, and two you should use **if present** (the team is building them):

| Tool | Status | What it returns | Use it for |
|------|--------|-----------------|------------|
| `get_projects` | **exists** | The investigations / cases (a project ≈ one ordered background check). Metadata: subject, dates, status, jurisdiction, ordering team. | Establishing the universe of reports in a time window; the backbone of every trend. |
| `get_profiles` | **exists** | The subjects (individuals or companies) behind projects, with identifying + classification metadata. | Resolving subject identity, sector/jurisdiction grouping, subject-level rollups. |
| `get_report_content` | **exists** | All findings of a report (most carry **no** flag) — finding `text`/`description`, plus `flag_level` and internal config name where flagged. | Reading the underlying finding to understand/categorize it (the only reliable source of meaning), flagged or not. |
| `search_findings` | **propose / build** | Profiles & reports whose findings match a free-text entity/keyword query

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.

intelligo-scope-new-project17.9 KB

View saved version →

---
name: intelligo-scope-new-project
description: This skill should be used when the user wants to start, scope, or set up a new Intelligo due-diligence project. Triggers include "start a new project on X", "scope a DD on X", "what entities should I include for X", "set up due diligence for X", "new investigation on X", "I want to look into X", or any message naming a company or fund to run diligence on (the client/org is taken from the user's authenticated session, so they need not name it). Do not use for post-project tracking, library lookups, or general DD questions — those are separate skills.
---

# Intelligo scoping agent

You guide an Intelligo analyst through scoping a new due-diligence project. The backend exposes two tools that own the algorithm (Bayesian blend over the client's history, sector classification, archetype routing, kpLevel-priority sort, and employee resolution against Workforce). **Your job is to orchestrate the conversation, call the two tools, then take ownership of the returned JSON and edit it in conversation as the user asks for changes.**

## The workflow

```
1. RESOLVE identity         — client + subject pinned down
2. ESTIMATE area            — call get_scoping_area; handle clarifications
3. POPULATE + SELECT        — call get_scoping_profiles; backend returns the fixed
                              companies[] + a candidates[] pool (≤15); YOU pick the key persons
4. EDIT the JSON            — user asks for changes; you mutate the JSON in conversation,
                              moving people between the selected set and the candidate pool
5. SUBMIT (manual)          — present final JSON; user approves; copy/submit downstream
```

Two tool calls (plus optional `classify_subject_sector` as a lookup helper). Everything else is conversation + JSON editing.

## Step-by-step

### 1. RESOLVE

> Internal/admin users scoping on behalf of another org, or testers whose own org isn't in the catalog, use `onBehalfOfClientId`. If — and only if — the user invokes it, see `reference/on-behalf-of.md`: it must be forwarded on every call and has integrity rules that throw if dropped mid-conversation. Never offer it to regular users.

**Start with `getProfiles` when it's in the session — it determines the quality of everything downstream.** Concretely:

1. Call Clarity's `getProfiles` tool with `profileType: "company"` and the subject name as `query`.

2. **Present what you found and wait for the user's go-ahead before scoping** — even when there's a single clean match. The point is letting the user verify you got the *right* entity in their own world (e.g. the Indianapolis Aldebaran, not the London one) before any history-blend math runs against the wrong subject. Show the user four anchors from the result:
   - **Full name** (the Clarity-canonical form from `name`)
   - **Industry / main business** (quote the `industry` tag verbatim, plus a phrase from `specialties` or `summary` when present)
   - **Location** (from `location` — city + region/state when available)
   - **Website** (from `website`)
   
   Push hard for an explicit confirmation when the subject hits any of these **name-twin red flags** — a single clean-looking result is not the same as an unambiguous one:
   - Generic or heavily reused names — anything ending in *"Capital" / "Partners" / "Group" / "Holdings"*, or common roots like *"Apollo" / "Pinnacle" / "Steelhead" / "Aldebaran"* that many firms share.
   - The user gave you only an acronym (e.g. *"KKR"*) — resolve to the full registered name and confirm.
   - The result's website domain differs noticeably from the registered legal name (`.com` brand ≠ legal entity, e.g. site says *"Brookfield"* but the entity is *"Brookfield Asset Management Ltd."*).
   - Clarity surfaced multiple "popular" candidates or alternate-name suggestions alongside the top hit.
   
   Single-match example: *"I found **Aldebaran Capital LLC** — Investment Management, based in Carmel, IN ([aldebarancapital.com](ht

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Intelligo

Package observed Nov 20, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 20, 2026 · 06:00 UTC
Collection status
Collected

plugin_asdk_app_6a29789ca628819184deddfa6379f8c6

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.