# Evals — linkedin-strategy

These cases are run by the skill-eval harness (or read by hand) to confirm three things. First, that `linkedin-strategy` loads on account-level prompts — positioning/POV, content pillars, cadence, the personal-vs-company-page distribution choice, and the SSI/social-selling rhythm — including the non-obvious "I post but get no inbound" framing and the Spanish phrasing. Second, that it stays off single-asset and API prompts, routing each to the named sibling (`linkedin-content`, `linkedin-carousels`, `linkedin-outreach`, `linkedin-api`, `social-publisher`) — every `route_to` id is a real skill in the catalog. Third, that the capability scenario exercises the full loop: read `02-DOCS/wiki/linkedin/` first, decide positioning/pillars/cadence/distribution/SSI-rhythm grounded in the account's own data, write a dated decision record back naming the metric it bets on and a review date, and route single-asset work out. There is no automated scorer here — judge `must_include` coverage against the model's output, and run `scripts/verify.sh 02-DOCS/wiki/linkedin/` to confirm any decision record the run produces is structurally complete.
