← CrunchbaseCONTENT HISTORY
WHAT CHANGED
Update to Crunchbase
Snapshot Nov 11, 2026 · 00:08 UTC · version 1.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Crunchbase and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Resolve a private-market entity and prepare a concise Crunchbase-grounded pre-meeting company brief or snapshot, including asking for the company when an explicit Crunchbase brief request omits its identity. Use only when the user explicitly asks for Crunchbase, selects Crunchbase as the data source, or follows up on an active Crunchbase company brief. Do not use for broad landscapes, recent-round screens, market-wide capital analysis, saved-list operations, public-equity research, Crunchbase pricing or account support, or generic company research when Crunchbase was not requested.",
"included_files": [
{
"relative_path": "LICENSE",
"size_in_bytes": 1067
},
{
"relative_path": "NOTICE",
"size_in_bytes": 239
},
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 557
},
{
"relative_path": "assets/crunchbase-icon-blue.png",
"size_in_bytes": 25215
},
{
"relative_path": "references/company-snapshot.md",
"size_in_bytes": 2701
},
{
"relative_path": "references/entity-resolution.md",
"size_in_bytes": 3487
},
{
"relative_path": "references/output-contract.md",
"size_in_bytes": 4407
},
{
"relative_path": "references/query-core.md",
"size_in_bytes": 4503
}
],
"name": "crunchbase-company-tearsheet-generator",
"skill_md_contents": "---\nname: crunchbase-company-tearsheet-generator\ndescription: Resolve a private-market entity and prepare a concise Crunchbase-grounded pre-meeting company brief or snapshot, including asking for the company when an explicit Crunchbase brief request omits its identity. Use only when the user explicitly asks for Crunchbase, selects Crunchbase as the data source, or follows up on an active Crunchbase company brief. Do not use for broad landscapes, recent-round screens, market-wide capital analysis, saved-list operations, public-equity research, Crunchbase pricing or account support, or generic company research when Crunchbase was not requested.\nlicense: MIT\n---\n\n# Company Tearsheet Generator\n\nPrepare a focused company snapshot for meeting preparation. Do not present it as full commercial, technical, or investment diligence.\n\n## Clarification contract\n\n1. Reuse a company name, user-supplied domain, or previously resolved company identity from the conversation. If none is present, make no Crunchbase call and ask for the company.\n2. Ask for meeting purpose, audience, or mandate only when the requested tailoring depends on an unresolved choice. Bundle blocking inputs into one concise question; offer alternatives as proposals rather than selecting them for the user.\n3. A request for an untailored company brief is enough to prepare a general brief. Do not ask about irrelevant preferences, re-ask answered questions, or seek authorization already given. “Use the defaults” accepts only previously disclosed defaults; propose any material default that has not been disclosed and wait for acceptance.\n4. When identity evidence is supplied, make the minimum resolution call. Ask the user to choose only if several credible candidates remain. Ask again only if the answer introduces a new blocking ambiguity.\n\n## Operating contract\n\nTool names below are Crunchbase basenames. Resolve them to the actual fully qualified names exposed by the connected Crunchbase server before calling them; do not guess a host prefix. If a required capability is unavailable, report the missing connection or tool and stop the dependent work.\n\n1. Resolve the named company first with `cb_expert_resolve_entity`, using the narrowest collection, concise situational context, and `cb_entity_get: null` for identity-only resolution. It is the only allowed expert tool; never call another tool whose basename contains `expert`.\n2. Use a confident resolver match directly. When the resolver returns several credible candidates, show linked choices and ask the user to select. Use `cb_entity_autocomplete` only when the resolver has a recoverable outage or returns no usable match or candidates.\n3. Pass a domain only when the user supplied it or it came from a previously resolved record. Never invent or infer a domain from model memory. A supplied domain is identity evidence, not permission to browse it.\n4. Retrieve the profile separately with `cb_entity_get`, explicit top-level fields, and only decision-relevant cards. Never request default cards.\n5. Before a structured search, resolve the required predicate and order contracts through `cb_reference` unless a successful resolution is already available in the current session. Reuse valid contracts and refresh only the affected metadata once after a validation error, as specified in `references/query-core.md`. Do not resolve projection-only fields. Reuse returned similar organizations and search projections; keep the competitor query set bounded to the requested scope.\n6. Keep this skill read-only. Never call a `cb_list_*` write tool.\n7. Use neutral record language. Show `—` for a null; the legend is “— indicates no value was returned for that field.” For an empty search, say “No records matched the stated filters.” Disclose observed, decision-relevant limitations as specified in `references/output-contract.md`; never infer that an event did not occur from an absent record.\n8. Link the canonical company and competitors to organization profile URLs. Include the as-of date and state that the brief is Crunchbase-grounded. Separate facts, interpretation, risks, and questions to test. Resolve every bundled `references/...` path relative to the directory containing this `SKILL.md`. Never mention skill folders, skill or reference files, instruction loading, plugin or package paths, caches, or attempts to locate bundled resources in any user-visible message.\n9. Stop on authentication, permission, or metering errors. A resolver-only outage permits one same-provider fallback sequence; other service failures require an accurate limitation. Do not retry a failed fallback or invent identifiers. Do not substitute external research unless the user requested it.\n\n## Procedure\n\n1. Read `references/entity-resolution.md` before resolving identity.\n2. Read `references/company-snapshot.md`, `references/query-core.md`, and `references/output-contract.md` before profile retrieval and composition.\n3. Retrieve only the company, financing, team, event, and peer fields needed for the requested meeting context.\n4. End with the strongest counterinterpretation or question that could materially change the assessment.\n"
}SHA-256 of public snapshot: 8ed5288cfd82334677df75f0975a7523fed33bbf26f26f3f0ab0854498f6738a