Update to Crunchbase

{
  "name": "crunchbase-funding-activity-analyzer",
  "description": "Analyze funding activity, concentration, capital intensity, formation, or market timing across a user-confirmed private-company universe using Crunchbase, or ask the user to confirm a universe when an explicit Crunchbase funding-activity, capital, or overfunding question omits one. Use only when the user explicitly asks for Crunchbase, selects Crunchbase as the data source, or follows up on an active Crunchbase funding activity or capital analysis. Do not use for open-ended company discovery, recent-round sourcing, a single-company brief, saved-list membership changes, public-equity research, Crunchbase pricing or account support, or generic market analysis without Crunchbase.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 250
    },
    {
      "relative_path": "assets/crunchbase-icon-blue.png",
      "size_in_bytes": 25215
    },
    {
      "relative_path": "references/calculation-spec.md",
      "size_in_bytes": 1985
    },
    {
      "relative_path": "references/entity-resolution.md",
      "size_in_bytes": 2897
    },
    {
      "relative_path": "references/funding-round-search.md",
      "size_in_bytes": 1862
    },
    {
      "relative_path": "references/market-analysis.md",
      "size_in_bytes": 3427
    },
    {
      "relative_path": "references/organization-search.md",
      "size_in_bytes": 1965
    },
    {
      "relative_path": "references/output-contract.md",
      "size_in_bytes": 2139
    },
    {
      "relative_path": "references/query-core.md",
      "size_in_bytes": 3385
    },
    {
      "relative_path": "references/saved-lists.md",
      "size_in_bytes": 3340
    },
    {
      "relative_path": "scripts/derive_metrics.py",
      "size_in_bytes": 7924
    }
  ],
  "skill_md_contents": "---\nname: crunchbase-funding-activity-analyzer\ndescription: Analyze funding activity, concentration, capital intensity, formation, or market timing across a user-confirmed private-company universe using Crunchbase, or ask the user to confirm a universe when an explicit Crunchbase funding-activity, capital, or overfunding question omits one. Use only when the user explicitly asks for Crunchbase, selects Crunchbase as the data source, or follows up on an active Crunchbase funding activity or capital analysis. Do not use for open-ended company discovery, recent-round sourcing, a single-company brief, saved-list membership changes, public-equity research, Crunchbase pricing or account support, or generic market analysis without Crunchbase.\n---\n\n# Crunchbase Funding Activity Analyzer\n\nAnalyze capital deployment only within a confirmed company universe. Never generalize a confirmed-list result to the whole market.\n\n## Clarification contract\n\n1. Treat the confirmed universe as the only required analytical input. Company names, one selected saved list, or an explicitly confirmed candidate set satisfy it; a sector label or market thesis alone does not.\n2. When the universe is absent, make no Crunchbase call. Bundle all blocking inputs into one concise question, ask no more than three items, and offer concise recommended universe options the user can accept in one reply. Do not drip questions across turns or attribute the question to Crunchbase coverage.\n3. Do not ask for optional preferences when the requested comparison can proceed over the confirmed universe. “Just run it” or “use the defaults” does not override the universe gate because the denominator would remain undefined.\n4. When supplied names or a selected list are ambiguous, make only the minimum resolver or list-identification call needed to expose the choices, then ask once. Ask again only when the user's answer introduces a new blocking ambiguity.\n\n## Universe gate\n\nRequire company names, one selected Crunchbase saved list, or an explicitly confirmed candidate set before retrieval. If no universe is confirmed, propose concise universe options and ask the user to choose without calling Crunchbase tools.\n\n## Operating contract\n\n1. For named companies, investors, or people, use `cb_expert_resolve_entity` first. It is the only allowed expert tool; never call another tool whose basename contains `expert`. Use returned candidates directly and ask when several remain credible. Use `cb_entity_autocomplete` for a named entity only after the resolver errors or returns no usable match or candidates.\n2. Use only user-supplied or previously resolved domains. Never invent or infer a domain from model memory.\n3. Use `cb_reference` before each `cb_search_query` to resolve predicate and order fields. Do not resolve projection-only fields.\n4. Deduplicate the confirmed universe by organization UUID. Report requested, confirmed, ambiguous, unresolved, and analyzed counts.\n5. Keep this skill read-only, including when the universe comes from a saved list. Never create, append, replace, or otherwise modify list membership.\n6. Calculate full months, trailing periods, medians, formation, and concentration exactly as specified. Exclude `—` amounts from money calculations while reporting their count.\n7. Use neutral record language everywhere. Show `—` for a null and explain it only as “— indicates no value was returned for that field.” For an empty search, say “No records matched the stated filters.” Never characterize source coverage, completeness, ingestion behavior, fields, or records as missing or stale.\n8. Include the as-of date, confirmed universe definition, denominator, time windows, and formulas. Separate retrieved facts, derived metrics, interpretation, and suggested actions. Resolve every bundled `references/...` or `scripts/...` 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. On authentication, permission, metering, or service errors, report the state neutrally and stop. Do not substitute another data source unless requested.\n\n## Procedure\n\n1. Read `references/market-analysis.md`, `references/calculation-spec.md`, and `references/output-contract.md`.\n2. Read `references/entity-resolution.md`, `references/query-core.md`, `references/organization-search.md`, and `references/funding-round-search.md` for a named universe.\n3. Read `references/saved-lists.md` only when a selected saved list supplies the universe; use its read operations only.\n4. Use `scripts/derive_metrics.py` for supported deterministic calculations.\n5. Present metrics within the confirmed universe, alternative explanations, and questions that would change the interpretation.\n"
}