ericrisco/rsc-harness / skills/linkedin-strategy
linkedin-strategy
VerifiedUse 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`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.0 KB |
| evals/README.md | markdown | 1.2 KB |
| evals/cases.yaml | config | 3.7 KB |
| references/ssi-and-pillars.md | markdown | 3.6 KB |
| references/wiki-records.md | markdown | 4.6 KB |
| scripts/verify.shexecutable | script | 4.0 KB |
references/wiki-records.md
View on GitHub# Wiki records — `02-DOCS/wiki/linkedin/`
The read/write loop's storage. Everything is append-only markdown so future strategy sessions compound instead of restarting from generic advice.
Every `.md` file written here is part of the `02-DOCS/wiki/` OKF v0.1 bundle, so each carries YAML frontmatter with a non-empty `type:` (the only required OKF field). Cross-references between files use **standard markdown links** (`[Text](./pillars.md)`) — never wikilinks (`[[...]]`). The domain lines `verify.sh` greps for (the dated heading, `Decision:`, the metric/bet field) stay exactly as below.
## File layout
```text
02-DOCS/wiki/linkedin/
positioning.md # current POV, niche of authority, who-it's-for; updated in place when it shifts
pillars.md # the live 3-5 pillars + any KILLED pillars with the date and reason
decisions/ # one append-only file per decision (preferred), dated filenames
2026-06-02-distribution-to-founder.md
2026-09-02-q3-review.md
what-worked.md # running log of what specific posts/pillars/formats earned dwell time + engagement
```
A running `decisions.md` log at the root is also accepted instead of `decisions/*.md` — pick one and stay consistent. `verify.sh` checks both shapes.
## Bootstrap (empty/absent dir)
When `02-DOCS/wiki/linkedin/` does not exist, create it with `positioning.md`, `pillars.md`, `decisions/`, and `what-worked.md` before you decide. Seed `positioning.md` with whatever the account already implies (title, current posts) so the first decision has a baseline to react to. Each of `positioning.md`, `pillars.md`, and `what-worked.md` gets OKF frontmatter — use `type: linkedin-positioning`, `type: linkedin-pillars`, and `type: linkedin-record` respectively (templates below).
## Decision-record template
Every record carries: a dated heading, a context-read line (what you grounded in), a decision line, the single metric it bets on, and a review date. Missing the metric or the review date means it is not a checkable bet.
```markdown
---
type: linkedin-decision
title: <short decision title>
description: <one-sentence summary of the choice>
tags: [linkedin, <pillars|cadence|distribution|ssi>]
timestamp: <YYYY-MM-DDTHH:MM:SSZ>
topic: linkedin
status: stable
---
# 2026-06-02 — <short decision title>
Context read: <what you pulled from the wiki — prior positioning, current pillars,
whether cadence held, top dwell-time performers, SSI trend, killed experiments>.
Decision: <the concrete choice — positioning / pillars / cadence / distribution /
social-selling rhythm, stated so the next session can act on it>.
Bets on metric: <the single steering metric + from -> to + window, e.g.
SSI 48 -> 65 within 90 days, or median dwell time +X%, or inbound DMs/week>.
Review date: <YYYY-MM-DD — when the next session checks whether the bet paid>.
```
`type` (required) + `timestamp` (ISO 8601, last meaningful edit) are the OKF surface; everything below the frontmatter is the domain content `verify.sh` checks. A running `decisions.md` log at the root carries one frontmatter block at the top (`type: linkedin-decision`); its dated `## ` entries are prepended newest-first and never edited.
## what-worked template
`what-worked.md` is a single running file; new review blocks are prepended newest-first under one frontmatter block at the top.
```markdown
---
type: linkedin-record
title: What worked — LinkedIn
description: Running log of which pillars, formats, and posts earned dwell time and SSI movement.
tags: [linkedin, what-worked, dwell-time, ssi]
timestamp: 2026-09-02T00:00:00Z
topic: linkedin
status: stable
---
## 2026-09-02 review
- Pillar "pipeline reliability" — RISING. 2 carousels in top-3 dwell time. Double down.
- Pillar "founder lessons" — FLAT. Text-only; try carousel format before sunsetting.
- Pillar "industry hot takes" — KILLED. Off-graph topic, suppressed reach. Slot reallocated to reliability.
- Format: carousels ~2.4x dwell vs text on this account. Weight calendar toward them.
- SSI: 48 -> 61 in 90 days. "Engage with insights" dimension moved most.
```
## What `scripts/verify.sh` checks
Read-only, network-free, pure bash + grep. Given `02-DOCS/wiki/linkedin/`:
1. The target directory exists.
2. At least one decision record exists (`decisions/*.md` or a root `decisions.md`).
3. Each record carries a date (`YYYY-MM-DD`), a `Decision:` line, and a named metric/bet field — a record missing the metric is a hard failure (a decision with no metric is an opinion).
A missing or empty target (a fresh presence with no wiki yet) is reported and exits 0 — no false failure. It enforces the compounding loop's integrity, not strategy quality (that is the capability eval).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |