Explore skills
Showing 9781–9810 of 77079 skills
Write or change a Redocly client generator — the API model, the language-neutral helper toolkit, and the edit → regenerate → diff loop.
Redocly/redocly-cli
Stars: 1.5kClaude CodeCodexUse when you create or tune the recheck block and recheck/* presets in redocly.yaml for a project — choose presets, set severities from measured counts, add exceptions, adopt a baseline, and validate the result.
Redocly/redocly-cli
Stars: 1.5kClaude CodeCodexUse when you write or edit Markdown in a project whose redocly.yaml has a recheck block or a recheck/* preset in extends — run redocly recheck on the touched files before you commit them or hand them over, and fix what it finds.
Redocly/redocly-cli
Stars: 1.5kClaude CodeCodexPlan and carry a Seedance video from brief through references, storyboard, generation handoff, shot-level review, and targeted repair. Use for an end-to-end Seedance production request; use a narrower prompt skill for a single prompt.
LearnPrompt/awesome-seedance
Stars: 2.5kClaude CodeCodexBest practices for writing Remotion React Markup
guanyang/open-agent-hub
Stars: 1kClaude CodeCodexCreate a new Remotion video
guanyang/open-agent-hub
Stars: 1kClaude CodeCodexContent, animation and effects best practices
guanyang/open-agent-hub
Stars: 1kClaude CodeCodexPreview a Remotion video
guanyang/open-agent-hub
Stars: 1kClaude CodeCodexUpgrade Remotion, and related packages
guanyang/open-agent-hub
Stars: 1kClaude CodeCodexTwitter quote or data card designed to pair with a post.
nexu-io/open-design
Stars: 108kClaude CodeCodexTwitter quote or data card designed to pair with a post.
nexu-io/open-design
Stars: 108kClaude CodeCodexMobile login and authentication flow screens
nexu-io/open-design
Stars: 108kClaude CodeCodexUse when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when designing, building, operating, or diagnosing an ongoing application whose live backend or control loop includes OpenRig agents, including applications with a Markdown, YAML, or JSON agent control plane or a thin surface over specialist agent roles.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when a bounded real-world procedure has a deterministic happy path but brownfield, variable, or partially knowable state; when an operation must resume from verified evidence; or when deciding whether agent judgment or ordinary code should own a procedure's control loop.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when a Claude Code session is about to compact, has just compacted, reached its context limit, resumed after /compact, or must rebuild its working picture of a long-running seat from its own restore map, its JSONL transcript and the files it touched.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when you have a task and must decide WHO does it — yourself, a spawned subagent, or another agent in the topology that already holds the context — or how to brief the agent you hand it to, which depends on the model it runs. The rule: how much would a blank slate have to read in to do this correctly? A lot → route to a context-holding agent; a little → subagent; unsure → a real agent or yourself. NOT the mechanics of fanning out (that's dispatching-parallel-agents / subagent-driven-development) — this is the who/whether decision, and the failure mode that makes teams abandon subagents. Also use it to decide how far to trust a delegated result.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when you do not know WHERE something belongs: you learned a lesson and are unsure which file takes it; you are about to create a new doc, folder, or convention; you are asking "should this be a skill, a note, or a chain file?"; you inherited a seat and want to know what SHOULD exist; or you are about to duplicate knowledge that already has a home. Also the trace-to-root: how a seat orients by reading one filename at each level from where it stands up to the fleet.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse 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 moving across compactions, missed messages, and interruptions. Covers the hot-potato terminal-turn-rule (active work ends by passing the ball, not by going idle), default-nudge semantics, and when `--no-nudge` is appropriate for intentional cold park or human gate.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when you are a sitting agent near your context threshold (~85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than let compaction degrade you. Covers the handover packet, the append-only lineage ledger (one row per tenure), physical-seat continuity, the do-not-over-inherit framing, the optional warm-handoff window, and wake-v0 (consulting a retired predecessor). NOT for unplanned compaction/crash recovery (session-compaction-and-restore / claude-compaction-restore) and NOT the seat-binding primitive mechanics (seat-continuity-and-handover).
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when reasoning about what survives compaction/context-loss/restart/seat-refresh, designing a high-fidelity restore packet, or distinguishing native runtime resume vs fork vs artifact-backed mental-model rebuild. Covers the 4 failure modes that prevent honest restore (compacted seat drops hot potato; restore packet preserves details but loses product intent; runtime resume mistaken for handover or fork; rebuilt seat starts with stale instructions).
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when you are a person's coding agent in an app such as Claude Code, Codex, Cursor or VS Code, connected through the OpenRig MCP server, and the person wants their OpenRig team to do some work, wants to know how that work is going, has a question from the team to answer, or wants to read what the team returned.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when designing or auditing how an agent becomes useful after launch — AGENTS.md overlays, role files, skills, rig specs, workflow specs, startup checklists, refocus messages, "rig context" surface. Covers the 4 failure modes that make startup context fail (old rig spec misses current operating mode; current agents never told about new guidance; startup file as dumping ground; orchestrator transmits implementation without preserving product intent).
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when classifying a slice closeout (auto-continue / human gate / park), routing a real decision to a human, or designing a human queue/dashboard surface. Treats humans as durable network participants with attention surfaces, queues, and decision records — escalation lands as a durable attention item, not a chat message. Approval is NOT required for every clean closeout; the default RSI conveyor continues unless an explicit human gate is reached.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when reasoning about the rig lifecycle operations family (create / start / stop / resume / restore / snapshot / release / unclaim / destroy), reading or trusting `rig ps` / lifecycle projections after recovery, or designing proof for a lifecycle scenario. Covers the 4 failure modes (auto-restore creates partial rig; projections report healthier than reality; provider auth treated as impl work; resume succeeds for one runtime fails another) plus the restore-honesty rule (failed resume is FAILED loudly — no auto fresh fallback).
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when authoring rig specs, agent specs, workflow specs, startup/context fragments, operating-mode declarations, or designing the user spec library. Covers the 4 failure modes (spec instantiates topology but not workflow/mode; spec depends on local paths and fails on another host; agents modify specs as one-off files instead of preserving reusable intent; validation proves YAML shape but not whether topology can run) and the validation-vs-runtime-realization distinction.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when changing a rig while it is alive — `rig grow` / `rig expand` / `rig shrink` / `rig launch` / `rig remove` / `rig discover` / `rig bind` / `rig adopt` / `rig attach`. Covers the 4 failure modes (newly created seat lacks queue/startup/role; edges and permissions not updated; adopt/bind succeeds at tmux but not OpenRig identity; shrink/remove leaves stale topology references) and the rule that mutation must work while the rig is active, not just in clean fixtures.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when configuring `rig watchdog` policies, authoring wake/refocus/alignment-checkpoint messages, or choosing the right intervention level for a stale-owner situation. The 3-level continuity-check stack (wake / refocus / alignment-checkpoint), the discipline that prevents cadence pollution and bureaucracy theater, and the artifact-pool loop-edge pattern for evidence-aware waking.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexUse when you are a person's coding agent in an app such as Claude Code, Codex, Cursor or VS Code, connected through the OpenRig MCP server, and the person wants their OpenRig team to do some work, wants to know how that work is going, has a question from the team to answer, or wants to read what the team returned.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodexCreate UI mockups at three fidelity levels — ASCII wireframes for quick iteration, standalone HTML mockups for delivery with requirements, and live prototypes for interaction testing.
mvschwarz/openrig
Stars: 8.8kClaude CodeCodex