mirror of
https://github.com/getcargohq/cargo-skills.git
synced 2026-09-14 19:17:15 +08:00
8994350ebb
Measured instead of guessed. Of the 176 credits-based actions, 148 were reachable from a routing surface — the stage map, the phase guides, alternatives.md, a recipe. The other 28 were reachable only from their own provider playbook, which is findable if you already know which provider to open. That is the wrong way round. The worst of it: headcount had no section at all. It is the most-asked company attribute and the first row of the custom-datapoints feasibility gate, and not one of the four salesNavigator.find* actions appeared anywhere in the stage map. New section carries all four, plus the only historical series (companyEnrich.getWorkforce), plus linkedin.findCustomHeadcount for the roles the fixed buckets don't have, plus the companyId prerequisite that quietly turns a 0.25 action into 0.30 on a list that arrived without one. "Who works at this domain" was not a documented question either. It is not the same as searching a population by title, and it has two answers at very different prices. New section, with the trap stated: looping hunter.searchDomain to build a list is the pitfall its own playbook warns about. Also adds rocketreach, mixrank and societeInfo to Enrich/Sourcing — societeInfo reaches French registry data (NAF code, collective agreement, filed accounts) that nothing else in the catalog does — and gives Hiring intent a second index at the same price. 154/176 now. The remaining 22 stay unrouted on purpose, and the CHANGELOG says why for each: the four LinkedIn engagement actions would undercut the acceptable-use refusal to batch-blast them, three natives belong to other skills, searchLeadsLegacy costs 300x its replacement, and the rest are finer grain on an already-routed surface rather than separate questions. One thing the build caught: adding aiArk.analyzePersonality re-introduced a term the codex package deliberately strips, since the directory rejected person-level inference. Kept for the channels that carry it, with matching PACKAGE_EDITS so the package still removes it. Dropped the forager rung rather than add machinery for a last-resort action priced 20x above its own chain. All 67 anchors verified. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019wkwbhrEoE5KW9A1CKBmcA