prima-scope-score

What it does when it runs

Given an account already classified by `prima-icp-check` and scanned by `prima-signal-scan`, estimates the probability that it actually subcontracts structural fabrication (steel/enclosures) rather than manufacturing 100% in-house — Notion's "Equipment Procurement Scope" criterion, which almost never has hard public data behind it. Outputs a 0-100 score + tier (`tier_1`/`tier_2`/`tier_3`), always with a traceable rationale citing the specific signals behind it — never a bare number. Two hard overrides dominate the weighted score: explicit "100% in-house/vertically integrated" evidence forces `disqualified_inhouse` regardless of everything else; a confirmed Import Genius import match forces `confirmed_outsources`. Also sets `needs_manual_scope_confirmation` for P1 accounts — a P1 never reaches `prima-draft` on tier alone. Cat4-only, by inclusion: only `company_category = Cat4` proceeds to scoring — `Cat1`, `Cat2`, `Cat3`, and `UNKNOWN` all return unscored (`scope_tier = N/A-<category>`), since Cat1/Cat2's own scope criterion is polarity-inverted from Cat4's (direct in-house operation is what qualifies them, not what disqualifies them) and Cat3 already has a human-confirmed `notion_scope`. Use this after `prima-signal-scan` (needs its capacity-expansion freshness) and before `prima-committee`.

Automated analysis of the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply

None found.

Hosts it reaches

No third-party host appears in the skill or its bundled files.

Tool permissions it declares

No allowed-tools in the frontmatter. It does act, so it runs under whatever permissions your session already grants.

Actions present in the files

network