Agent skills you can check before you install
Public SKILL.md skills from GitHub repositories with 50+ stars and from the vendors themselves, scanned and scored. Install any of them with one command in Claude Code, Cursor, Codex, GitHub Copilot or Gemini CLI.
35,001 skills from 1,572 repositories · updated 12 minutes ago
34,502 skills
- gentle-ai-collab-perfectGentleman-Programming/gentle-aiTrigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the contribution flow is in scope: opening an issue, drafting or editing a PR body, splitting a change into chained/stacked PRs, or auditing a PR before requesting review.WritingNo warnings★ 8K↓ —
- rigsmvschwarz/openrigUse when a person in their own Claude Code or Codex session mentions OpenRig, rigs or the rig command, or wants a team of coding agents (Claude Code, Codex) on their project. That includes installing, setting up, starting or updating OpenRig, seeing, getting back to or re-attaching to their OpenRig agents (including bringing a stopped team back), TUI or operator, starting or sharing a team, and joining this session to one. Operating a running rig from inside it (fleet recovery, seat handover, watchdog wakes, in-rig upgrades) is the openrig-skills skill.EngineeringNo warnings★ 8.1K↓ —Also in 1 other repo
- forming-an-openrig-mental-modelmvschwarz/openrigUse when the system around you does not make sense yet: you just booted into a seat and do not know how the pieces fit; someone said rig, pod, seat, fleet, topology, or slice and you are not certain what they mean here; you are unsure what kind of rig you are in or what it is for; you do not know how skills reach you or where context comes from; or you are about to act on a guess about how OpenRig works. Gives the runtime mental model fast, so you stop guessing.ProductivityNo warnings★ 8.1K↓ —
- retiring-and-inheriting-a-seatmvschwarz/openrigUse 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).PlanningNo warnings★ 8.1K↓ —
- orienting-to-an-inherited-seatmvschwarz/openrigUse when you have just been primed into an EXISTING seat through a planned handover — a different agent retired and handed you the seat plus its earned context — and you need a world model of what just happened to you. Covers how a handover differs from compaction and from a fresh launch, the inherit-the-seat-not-the-identity rule, treating the handover packet as testimony you verify (and refusing stale ghost prompts, and verifying your OWN identity surfaces), why a seat is a COMPOUNDING LINEAGE (inherit the state, acquire the predecessor's epistemology, then improve and re-deposit so the next generation is better), how to query your predecessor, your duty to stream feedback and re-deposit your earned wisdom, and how to route to role-specific onboarding. NOT the driver-side handover mechanic (retiring-and-inheriting-a-seat) and NOT unplanned compaction/crash recovery (claude-compaction-restore / session-compaction-and-restore).PlanningNo warnings★ 8.1K↓ —
- seat-continuity-and-handovermvschwarz/openrigUse when replacing a seat's occupant (rebuild/handover/swap), reasoning about stable-seat-identity vs fluid-occupant-identity, choosing an old-occupant disposition (retire/advise/shadow), or recording provenance for an occupant change. Two independent outcomes (continuityOutcome + seatBindingOutcome) and the 5 failure modes that prevent silent dishonesty.OtherNo warnings★ 8.1K↓ —
- applying-a-permission-policymvschwarz/openrigUse before launching a team during agent-guided setup, or when a user asks to configure OpenRig command permissions, reduce repeated native approval prompts, or apply a selected rig/seat permission policy.OtherNo warnings★ 8.1K↓ —
- test-driven-developmentmvschwarz/openrigUse when implementing any feature or bugfix, before writing implementation codeTestingNo warnings★ 8.1K↓ —Also in 1 other repo
- openrig-software-factorymvschwarz/openrigUse when a user wants a continuing software team for a real repository, or has a first OpenRig team and needs a repeatable path for reviewed work and later tasks.ProductivityNo warnings★ 8.1K↓ —Also in 1 other repo
- cross-host-rig-commandsmvschwarz/openrigUse when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.OtherNo warnings★ 8.1K↓ —Also in 1 other repo
- context-engineeringmvschwarz/openrigUse when designing, reviewing, or debugging how an agent's context window gets filled, pruned, or shared — choosing what loads at boot versus on demand, sizing an install or an always-loaded file, fixing an agent that drifts, repeats itself, or forgets constraints mid-task, planning compaction or summarization, deciding single-agent versus subagents, engineering handoffs between agents, or picking a tool loadout. NOT for rewording a prompt's tone, choosing which model to pin, or debugging business logic — those are adjacent moments this skill does not serve. Historical 2024–2025 snapshot; not normative for present-day frontier models — see the Status section.ProductivityNo warnings★ 8.1K↓ —Also in 1 other repo
- session-source-forkmvschwarz/openrigUse when authoring a rig spec member or `rig expand` payload that needs to start a new managed seat from a prior runtime conversation source — `session_source: { mode: fork, ref: { kind, value } }`. v1 supports `mode: fork` with `ref.kind: native_id` for Claude and Codex. The new seat persists a NEW post-fork token; the parent token is NEVER written onto the new seat. NOT for restoring an existing seat or for artifact-backed mental-model rebuild.WritingNo warnings★ 8.1K↓ —Also in 1 other repo
- messaging-the-humanmvschwarz/openrigUse when project policy calls for a human decision or update, a human delivery is pending or failed, or a reply must resume the right work.OtherNo warnings★ 8.1K↓ —Also in 2 other repos
- frontend-designmvschwarz/openrigCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.DesignNo warnings★ 8.1K↓ —Also in 1 other repo
- requirements-writermvschwarz/openrigUse when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.WritingNo warnings★ 8.1K↓ —Also in 1 other repo
- openrig-architectmvschwarz/openrigUse when designing multi-agent topologies that run ON OpenRig — authoring RigSpec and AgentSpec files for new rigs, creating agent startup content (guidance / skills / culture), or diagnosing why a launched rig's agents aren't behaving as intended. NOT for changing OpenRig itself (use developing-openrig); NOT for ordinary CLI operation of an existing rig (use openrig-user). Covers the full authoring lifecycle from user intent to validated, launchable rig.PlanningNo warnings★ 8.1K↓ —Also in 1 other repo
- subagent-driven-developmentjnMetaCode/superpowers-zh当在当前会话中执行包含独立任务的实现计划时使用OtherNo warnings★ 8.4K↓ —
- finishing-a-development-branchjnMetaCode/superpowers-zh当实现完成、所有测试通过、需要决定如何集成这份工作时使用OtherNo warnings★ 8.4K↓ —
- test-driven-developmentjnMetaCode/superpowers-zh在实现任何功能或修复 bug 时使用，在编写实现代码之前TestingNo warnings★ 8.4K↓ —
- requesting-code-reviewjnMetaCode/superpowers-zh完成任务、实现重要功能或合并前使用，用于验证工作成果是否符合要求EngineeringNo warnings★ 8.4K↓ —
- diagnosing-superpowersjnMetaCode/superpowers-zh当一次 superpowers 会话出了问题、你的人类伙伴想知道原因时使用——重复劳动、无视计划、磕磕绊绊、结果质量差、某个技能没触发、"太慢了"、"为什么这么贵"、"它到底在干什么"——或者想给 superpowers 维护者整理一份 bug 报告；适用于当前会话，或按 id / 路径指定的过往会话，任何工具均可OtherNo warnings★ 8.4K↓ —
- receiving-code-reviewjnMetaCode/superpowers-zh收到代码审查反馈后、实施建议之前使用，尤其当反馈不明确或技术上有疑问时——需要技术严谨性和验证，而非敷衍附和或盲目执行EngineeringNo warnings★ 8.4K↓ —
- chinese-documentationjnMetaCode/superpowers-zh中文文档排版参考——中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定。仅在用户显式 /chinese-documentation 时调用，不要根据上下文自动触发。OtherNo warnings★ 8.4K↓ —
- chinese-commit-conventionsjnMetaCode/superpowers-zh中文 commit 与 changelog 配置参考——Conventional Commits 中文适配、commitlint/husky/commitizen 中文模板、conventional-changelog 中文配置。仅在用户显式 /chinese-commit-conventions 时调用，不要根据上下文自动触发。EngineeringNo warnings★ 8.4K↓ —
queue-handoff
mvschwarz/openrig
OtherUpdated 13 hours ago
From the author
Use 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.
Install
npx skills add mvschwarz/openrig --skill queue-handoff -a claude-code
Installs to .claude/skills/queue-handoff/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Instructions onlyNo network use seenLicence: APACHE-2.0
Safety checks on SKILL.md
No warnings.
Why 92
Security100
Provenance87
Maintenance100
Licence100
Adoption61
Files (1)
- SKILL.md