OPC Skills
An agent-skills pack from ReScienceLab aimed at “solopreneurs, indie hackers and
one-person companies” — Apache-2.0, 1.2k★ / 121 forks, about 11 skills, installable across
16+ agent tools (Claude Code, Cursor, Windsurf, Factory Droid, GitHub Copilot and others) through its
own installer. Standard structure: a folder per skill with SKILL.md and YAML frontmatter, scripts and
resources beside it, loaded on demand.
The skills are seo-geo, requesthunt, domain-hunter, logo-creator, banner-creator,
nanobanana, reddit, twitter, producthunt and archive. Market research on Reddit, Twitter and
Product Hunt; domain-name hunting; SEO work; logo and banner generation; content archiving.
T3 — the project’s own README, with no stated authorship policy for the skills and nothing measured.
Why it is a different animal
Every other skillpack in this corpus teaches an agent to build software. superpowers and compound-engineering-plugin package a development methodology; pm-skills and pm-skills-arsenal cover product management around it; superclaude-framework wraps the coding loop itself. OPC Skills’ subject is running the business — find a name, check whether anyone wants it, make the logo, get the traffic. The two SEO/marketing packs already here (agentic-seo-skill, claude-skills-ppc) are single-discipline; this one covers a whole one-person company’s non-coding work as a set.
That widens the claim the spoke has been tracking. The skills standard was pitched as a way to give an agent domain expertise, and the packs arriving have mostly proved it for engineering. This is evidence the format travels to work with no repository in it at all — where the “verification” a coding pack gets for free (tests, a compiler, CI) does not exist. Nothing in the pack replaces it, and nothing in the README acknowledges the gap.
Inter-skill dependencies
The structurally interesting part: skills depend on other skills. domain-hunter requires twitter
and reddit. That is composition declared inside the pack rather than left to the agent, and it is not
something the standard provides — the standard’s model is a flat set of skills whose
frontmatter the agent scans and selects from. The corpus’s other answers to composition sit outside the
skill: agentic-awesome-skills exposes compose_stack through an MCP server and lets the agent pick
IDs, validating structure only. OPC Skills hard-codes the edge instead. Three different places to put
composition — in the standard (absent), in a control plane (agentic-awesome-skills), in the skill itself
(here) — and no one has argued for one over the others.
Related
agentskills-spec · agentic-awesome-skills · superpowers · pm-skills · pm-skills-arsenal · agentic-seo-skill · claude-skills-ppc · superclaude-framework