ericrisco/rsc-harness / skills/social-publisher
social-publisher
VerifiedUse when planning a posting schedule, building a multi-platform content calendar, or reshaping one source asset into channel-native posts across X, LinkedIn, Instagram, Threads, Bluesky, TikTok, Facebook or YouTube — cadence, best-time slots, per-platform format limits, API publish caps, and a dated CSV or JSON calendar a scheduler can import. NOT the brand voice the posts speak in (that is `brand-voice`), NOT the editorial strategy of what to make (that is `content-engine`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.8 KB |
| evals/README.md | markdown | 993 B |
| evals/cases.yaml | config | 3.5 KB |
| references/calendar-schema.md | markdown | 4.0 KB |
| references/platform-limits.md | markdown | 4.4 KB |
| scripts/verify.shexecutable | script | 7.9 KB |
evals/README.md
View on GitHub# Evals — social-publisher
These cases are routing + capability checks for a human or an LLM judge; there is no
automated test runner beyond `scripts/verify.sh` (which lints an emitted calendar
file, not these prompts). To run them: read `cases.yaml` and confirm the skill's
`description` would fire on every `should_trigger` prompt (including the non-obvious
"same caption flopped" symptom and the Catalan "reaprovechar" phrasing), that each
`should_not_trigger` prompt routes to the named sibling instead (`brand-voice`,
`video-shorts`, `community`, `content-engine`), and that a calendar generated for the
`capability` scenario satisfies every line of its `must_include` rubric — native
per-platform variants, sane 2026 cadence, best-time slots flagged as hypotheses, a
schedulable table with the required columns, surfaced publish-limit/approval gates,
and no invented brand voice or topics. To check an actual emitted calendar, point
`scripts/verify.sh` at the CSV/JSON it produced.
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 |