From Intelligo
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/intelligo:intelligo-prep-committee-deckThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
assets/templates/disclosure-delta.mdassets/templates/executive-narrative.mdassets/templates/flags-by-severity.mdassets/templates/narrative-memo.mdassets/templates/one-pager-tear-sheet.mdassets/templates/project-rollup.mdreferences/flavors.mdreferences/intake-flow.mdreferences/profile-resolution.mdreferences/snippet-design.mdscripts/generate_snippets.pyIntelligo 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:
references/intake-flow.md).references/flavors.md).show_widget. PDF, PPTX, or downloadable HTML on request. Always preview in chat first.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:
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.
What to fetch depends on scope:
Single subject: subject identity (name, role, entity, jurisdictions), report metadata (level, dates, scope, coverage), flags by section with severity / title / finding text / source / date / review state / analyst notes, disclosure delta if available, coverage summary.
Project rollup: all of the above for every subject in the project, plus project identity, subject roster with per-subject flag counts, aggregate flag profile across the deal, red + analyst-elevated yellow findings attributed to subjects, deal-wide disclosure picture if applicable.
Hybrid: project rollup + full single-subject data for the deep-dived subject(s).
If a tool returns a different shape than expected, work with what you get; explain what's missing rather than fail.
Always produce both in this mode:
show_widget) — the analyst sees the snippets next to the conversation and clicks Copy on each block to paste into their slide deck. Primary copy surface.present_files) — the analyst can click to open the same content in their browser for a full-page view, to share with a teammate, or to archive.Both are generated from the same findings spec — same content, two surfaces. The widget is for fast copy; the file is for view / share / archive. The analyst doesn't have to pick — both are there.
Workflow:
scripts/generate_snippets.py).# widget version (no html/head/body wrapper, for show_widget)
python3 scripts/generate_snippets.py --widget findings.json /tmp/widget.html
# standalone version (full HTML document, for present_files)
python3 scripts/generate_snippets.py findings.json outputs/ic-snippets-<subject_slug>-<date>.html
show_widget with a descriptive title like ic_snippets_<subject_slug>.present_files so the analyst gets a clickable card pointing to the HTML file.Use the pptx skill. 1–4 slides per flavor: executive summary + flag counts, findings by severity, disclosure delta (if relevant), coverage + IC questions. Match the snippet visual style.
Use the pdf skill. Single document per the chosen flavor. Always include: cover/header with subject + report level + date, executive narrative, findings by severity, disclosure delta if applicable, coverage + Intelligo link as appendix.
references/profile-resolution.md — no internal IDs in conversation.references/profile-resolution.md — shared logic for resolving the user's reference to a single Intelligo profile (used by all Intelligo skills)references/intake-flow.md — the question treereferences/flavors.md — flavor catalog + audience × lead-with mapping tablereferences/snippet-design.md — visual spec for snippetsassets/templates/ — markdown skeletons per flavor (for PDF/PPTX rendering)scripts/generate_snippets.py — widget renderer; canonical source for snippet HTML structure and JSON schemaProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub intelligogroup/intelligo-agents-plugins --plugin intelligo