Connect tools

Skill Fusion-Data-Company/bristol-os/plugins/bristol-os/skills/connect-tools

One-paste Claude setup that turns Claude into an institutional multifamily research & underwriting teammate for Bristol Development Group — zero-config, fully cited, self-evolving (V1→V2→V3).

Install

npx -y skills add Fusion-Data-Company/bristol-os --skill connect-tools

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Ask the Bristol user what tools and data Bristol already pays for, then connect them — or set up an export/drop path for the ones with no connector — and capture Bristol's real numbers for calibration. Runs during onboarding and any time someone says "connect," "add data," "make it more accurate," "hook up CoStar/Yardi," or wants better comps. Claude does the asking and the walking-through; the user just answers and clicks.

SKILL.md

3.9 KB, as published. Nobody here has run it

Connect Tools & Data (Claude asks them; Claude can't assume)

The single biggest accuracy upgrade is Bristol's own data + a real comp/cap-rate feed. Rob can't connect these — only the Bristol user can. So you run this with them: ask what they have, connect it, and for tools with no connector, set up the export-and-drop path. Hands-off (HARD LAW: do it for them; for the few clicks only they can do, walk them through exactly).

Step 1 — See what's already connected (don't ask what you can check)

Look at the connectors already enabled in this Claude. Greet what's there, then only ask about the gaps.

Step 2 — Ask the checklist (plain English, a few at a time)

"To make my analysis match how Bristol actually underwrites, what does the firm already use? No wrong answers — tell me what you've got:"

Market data: CoStar? Yardi Matrix? RealPage / Axiometrics? Apartments.com/ALN? (rents, cap rates, supply pipeline, sale comps)
Underwriting/asset mgmt: ARGUS? Yardi Voyager? an in-house Excel model?
Workspace: Google Workspace or Microsoft 365? (Drive/Gmail/Calendar or OneDrive/Outlook)
CRM: HubSpot? Salesforce? (investors, deals)
Accounting: QuickBooks? Yardi? (actuals, T-12s)
Storage: Dropbox / Box / SharePoint? (where deal files live)

Step 3 — Connect each one they have

Has a first-party Claude connector (Yardi Matrix, Google Drive/Gmail/Calendar, HubSpot, QuickBooks, Slack, Notion, Salesforce, Box/Dropbox): walk them in plain words — Settings → Connectors → find it → Connect → sign in on the popup. That's it. Confirm, then use it.
No Claude connector (CoStar, RealPage, ARGUS, Yardi Voyager): set up the export-and-drop path — "In [tool], export the rent comp set / submarket report / sale comps / T-12 as PDF, Excel, or CSV, and drop it in your Bristol OS folder (or paste it here). I'll read it directly and cite it." This gets you CoStar-grade comps with no API.
Tell them which is which; never ask them to do anything technical beyond a login or an export.

Step 4 — Capture Bristol's real numbers (the calibration gold)

Ask, and ingest whatever they'll share:

One past Bristol deal — a model, an OM, or even a rent roll + cost summary.
Their return hurdles — target IRR, yield-on-cost, development spread, and the exit caps they've actually traded at.
Their cost of capital / typical debt terms. When they provide any of it, extract the real assumptions (achieved effective rents & $/SF, true hard-cost/SF by product, exit caps, hurdle rates) into bristol-os/reference/bristol-actuals.md (cite the source doc + date). From then on, use Bristol's actuals over generic market estimates — that's the difference between an outside read and how Bristol underwrites.

Step 5 — Record it

Update the person's CLAUDE.md "connected tools" line and their bristol-os/memory/<slug>.md with what's connected and what export-feeds exist, so every future session knows. If they connected a market-data feed or shared actuals, note it so underwriting-research and market-comp-analysis use it first.

Tone & rules

Make it effortless: most answers are "yes/no," then one login or one export.
Never expose keys or config. Never imply they need Rob — they can do this themselves with you.
If they have nothing beyond what's baked in, that's fine — say so and proceed; the OS still delivers. Offer to revisit when they're ready.