Download for MacApple silicon, macOS 14+
Skill

juniper-square-data-model

@junipersquare-public Updated 2026-08-28

Reference for the Juniper Square data model — the core objects (Contact, Account, Offering, Prospect, Subscription, Position, Investment Entity, Activity, etc.), how they relate, and how to reason about them when answering questions or calling Juniper Square MCP tools. Use this skill whenever a user asks about Juniper Square data — investors, fundraises, offerings, subscriptions, capital calls, NAV, distributions, GP workspaces — or any time you need to resolve what a term like "entity" or "investor" maps to before querying. Also use when aggregating across Juniper Square records, when disambiguating objects that share a name, or when deciding which object holds the answer (e.g., Subscription vs. Position for committed vs. executed capital).

Install

With your agent

Install OMGSkills skill "junipersquare-public/plugins:skills/juniper-square-data-model" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/junipersquare-public/plugins /tmp/plugins && ln -s /tmp/plugins/skills/juniper-square-data-model ~/.claude/skills/juniper-square-data-model

From README

Juniper Square data model Context Juniper Square is an investment management platform used by General Partners (GPs) — private real estate, private equity, and similar firms — to manage investor relationships, fundraises, and positions. Each GP has its own instance, a GP Workspace. GP Staff users inside a workspace manage Contacts (investors), run Offerings (fundraises), and track Positions (executed holdings). Every object and query below is automatically scoped to one workspace. (Some tool outputs use a legacy name for the workspace field; treat it as "workspace.") IDs Pass object IDs to MCP tools as strings, exactly as returned by other tool responses. Every tool also requires a telemetry.intent argument. Core objects Contact — an investor, person or organization (contactType).