.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/mvschwarz/openrig
home/skills/mvschwarz/openrig
mvschwarz avatar

mvschwarz/openrig

35 skills

View on GitHub
$npx skills add mvschwarz/openrig
SkillInstalls
agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…—agent-startup-and-context-ingestionUse when designing or auditing how an agent becomes useful after launch — AGENTS.md overlays, role files, skills, rig specs, workflow specs, startup…—backlog-captureQuickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.—brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.—claude-compaction-restoreUse when a Claude Code session has just compacted, is about to compact, reached context limit, resumed after /compact, or needs to rebuild its working mental…—context-builderGather and distill context from meetings, competitors, regulatory sources, and internal discussions.—development-teamHow the development pod coordinates implementation, QA, and design without skipping gates.—dogfoodSystematically explore and test a web application to find bugs, UX issues, and other problems.—exec-summaryGenerate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.—executing-plansUse when you have a written implementation plan to execute in a separate session with review checkpoints—forming-an-openrig-mental-modelUse when an agent is newly oriented to OpenRig and needs to form an accurate mental model of the system fast — what rigs are, how skills load, what the…—frontend-designCreate distinctive, production-grade frontend interfaces with high design quality.—mission-slice-sopUse when working a mission or slice — the full SDLC flow (intent → mini-requirements + proof contract → mockups → plan-lock → build → QA visual compare → `rig…—office-hoursYC-style product validation using six forcing questions. Pressure-tests a feature idea before it becomes a requirement — ensuring real demand, a clear wedge,…—openrig-architectUse when designing multi-agent topologies that run ON OpenRig — authoring RigSpec and AgentSpec files for new rigs, creating agent startup content (guidance /…—openrig-cmuxUse when opening OpenRig fleet terminals into cmux — turning a rig, pod, mission, slice, or saved view into live agent tiles via `rig terminal --provider…—openrig-herdrUse when opening OpenRig fleet terminals as a herdr wall — turning a rig, pod, mission, slice, or saved view into live interactive agent tiles via `rig…—openrig-installerUse when installing or upgrading OpenRig on a host, especially the V0.3.1 upgrade flow which includes the substrate-kernel → daemon-managed-kernel migration…—openrig-operatorUse when debugging host-side OpenRig runtime issues: daemon reachability, Codex permission or writable-root failures, command approval friction, rate…—openrig-userUse when operating OpenRig with the `rig` CLI and you need the shipped command surface for identity, inventory, communication, lifecycle, specs, recovery, or…—openrig-user-settingsUse when the user asks an OpenRig agent to read or change OpenRig configuration settings — workspace paths, file allowlists, progress scan roots, daemon…—orchestration-teamOperating manual for the orchestration pod. Covers lead vs peer roles, monitoring with rig commands, permission handling, implementation pair gating, dogfood…—plan-reviewMulti-perspective review of a feature plan or requirements doc before development begins.—queue-handoffUse when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps…—requirements-writerConversational intake that produces a structured requirements.md following a standardized PM schema.—review-teamComplete operating manual for the review pod. Covers everyday review discipline, anti-slop analysis, empirical verification, context priming, the full deep…—rig-lifecycleUse when reasoning about the rig lifecycle operations family (create / start / stop / resume / restore / snapshot / release / unclaim / destroy), reading or…—seat-continuity-and-handoverUse when replacing a seat's occupant (rebuild/handover/swap), reasoning about stable-seat-identity vs fluid-occupant-identity, choosing an old-occupant…—systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes—test-driven-developmentUse when implementing any feature or bugfix, before writing implementation code—ui-mockupCreate UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes…—using-superpowersUse when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions—vault-userYou have access to a HashiCorp Vault instance managed by this rig's environment.—verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output…—writing-plansUse when you have a spec or requirements for a multi-step task, before touching code—