Skip to content

ericrisco/rsc-harness / skills/linkedin-strategy

linkedin-strategy

Verified

Use when a LinkedIn presence — personal brand or company page — needs an account-level decision spanning months: positioning and point of view, three to five content pillars, posting cadence, whether content lives on the founder's profile or the company page, and the social-selling rhythm, read from and written back to the presence's own learning wiki. NOT writing the post copy or hook (that is `linkedin-content`), NOT building a carousel deck (that is `linkedin-carousels`), NOT sending DMs (that is `linkedin-outreach`), NOT pulling raw analytics (that is `linkedin-api`).

FileKindSize
SKILL.mdskill md13.0 KB
evals/README.mdmarkdown1.2 KB
evals/cases.yamlconfig3.7 KB
references/ssi-and-pillars.mdmarkdown3.6 KB
references/wiki-records.mdmarkdown4.6 KB
scripts/verify.shexecutablescript4.0 KB

evals/README.md

View on GitHub
# 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.
deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json.Stars: 118kUpdated Claude CodeCodexVerifiedInstall