OPC Skills is a curated marketplace and toolchain of AI agent skills designed for solopreneurs, indie hackers, and one-person companies. The repository contains 9 skills (reddit, twitter, producthunt, domain-hunter, logo-creator, banner-creator, nanobanana, seo-geo, requesthunt, archive) that each provide structured prompts and Python scripts to automate tasks like market research, SEO/GEO optimization, domain hunting, logo/banner creation, and social media analysis. Skills are distributed via the Agent Skills standard (`npx skills add`) and also available as a Claude Code plugin. The project includes a full website at opc.dev powered by a Cloudflare Worker (website/worker.js) with per-skill pages, a blog, SEO/GEO optimization, and install statistics tracking. CI/CD pipelines deploy the website, test installs across platforms, and fetch install stats daily. The codebase follows a consistent architecture: each skill has a SKILL.md with YAML frontmatter, optional Python scripts following a credential → API wrapper → per-endpoint script pattern with TOON (Token-Oriented Object Notation) output, and dependencies declared between skills. While primarily an application, it has data-research characteristics due to its heavy use of external API scraping for market signals (Reddit, Twitter, ProductHunt) and SEO analytics. The repository is actively maintained with frequent releases, a changelog, and an agent-assisted development workflow (Ralph). Notable strengths include the reusable skill template pattern, cross-session memory via the archive skill, and the standalone SEO audit script. Key risks include reliance on multiple third-party API keys, tight coupling between some skills, and fragility in the install stats scraper.
This repository is a sample application for the Google Home Local SDK, demonstrating how to create a local fulfillment for a smart light device. It consists of three main parts: the local home app (in the `app` directory) that discovers and controls the device using various network protocols (UDP, mDNS, UPnP for discovery; UDP, TCP, HTTP for control); a virtual device (in the `device` directory) that simulates a smart light using the Open Pixel Control (OPC) protocol and supports the same discovery and control protocols for testing; and a Cloud Function (in the `functions` directory) that acts as a placeholder for the cloud-to-cloud backend, handling account linking and returning placeholder responses for SYNC and QUERY intents (while deferring EXECUTE and QUERY to the local fulfillment). The local home app uses a strategy pattern to delegate discovery and execution handling to protocol-specific implementations. The virtual device encapsulates the OPC protocol logic in a reusable component that is independent of the underlying transport mechanism.