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.
32,113 skills from 1,400 repositories · updated 8 minutes ago
31,651 skills
- rdd-defect-workflowGentleman-Programming/gentle-aiTrigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.ProductivityNo warnings★ 8K↓ —Also in 1 other repo
- work-unit-commitsGentleman-Programming/gentle-aiPlan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.TestingNo warnings★ 8K↓ —
- release-skillsJimLiu/baoyu-skillsUniversal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, GitHub Releases, annotated tags, historical release backfill, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送", "release notes", "GitHub Release", or "回填 Release".EngineeringNo warnings★ 26.9K↓ —Also in 1 other repo
- issue-root-resolutionGentleman-Programming/gentle-aiTrigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.OtherNo warnings★ 8K↓ —
- gentle-ai-chained-prGentleman-Programming/gentle-aiTrigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.EngineeringNo warnings★ 8K↓ —
- gentle-ai-benchGentleman-Programming/gentle-aiTrigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.TestingNo warnings★ 8K↓ —Also in 1 other repo
- 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↓ —
- 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↓ —
- 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
- delegating-workmvschwarz/openrigUse 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.ProductivityNo 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↓ —
- development-teammvschwarz/openrigUse when a development pod begins or hands off implementation, QA, or design work.TestingNo warnings★ 8.1K↓ —Also in 1 other repo
- openrig-skillsmvschwarz/openrigUse when an agent running inside OpenRig needs the right skill or context for fleet recovery, seat handover, new-seat orientation, a watchdog wake, cross-host reach to an agent on another machine, rig packaging, an OpenRig upgrade, systematic debugging, queue triage, or implementation planning; also when the agent doesn't know what applies or nothing is projected on cold boot. Installing, starting or updating OpenRig, getting back to a team or bringing a stopped one back from a person's own session is the rigs skill.PlanningNo warnings★ 8.1K↓ —Also in 2 other repos
- rig-lifecyclemvschwarz/openrigUse 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).OtherNo warnings★ 8.1K↓ —Also in 1 other repo
- openrig-cmuxmvschwarz/openrigUse when opening OpenRig fleet terminals into cmux — turning a rig, pod, mission, slice, or saved view into live agent tiles via `rig terminal --provider cmux`, or driving cmux on an agent's request. Same OpenRig view semantics as openrig-herdr (the verbs, honest-partial/degrade, read-only cross-rig, scroll/copy, same-size-only duplicates); cmux is the **best-effort** provider (herdr is the default and the proof-gated one). Prefer openrig-herdr unless cmux is specifically wanted.PlanningNo warnings★ 8.1K↓ —Also in 1 other repo
- backlog-capturemvschwarz/openrigQuickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.OtherNo warnings★ 8.1K↓ —Also in 1 other repo
- review-teammvschwarz/openrigUse when assigned a review or when an authored review boundary is reached.EngineeringNo warnings★ 8.1K↓ —Also in 1 other repo
- 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↓ —
- dispatching-parallel-agentsjnMetaCode/superpowers-zh当面对 2 个以上可以独立进行、无共享状态或顺序依赖的任务时使用OtherNo warnings★ 8.4K↓ —
- agent-startersmvschwarz/openrigUse when creating, refreshing, packaging, inspecting, promoting, or deprecating a named per-seat starting point — Agent Starter manifest authoring, the 6-state lifecycle (captured → named → inspectable → used → promoted → deprecated), provenance honesty, and refusal rules. NOT a VM image; a managed starting point composed from agent role + startup context + optional native session source + provenance.MediaNo warnings★ 8.1K↓ —Also in 1 other repo
- using-superpowersjnMetaCode/superpowers-zh在开始任何对话时使用——确立如何查找和使用技能，要求在任何响应（包括澄清性问题）之前调用 Skill 工具OtherNo warnings★ 8.4K↓ —
- chinese-code-reviewjnMetaCode/superpowers-zh中文 review 沟通参考——话术模板、分级标注（必须修复/建议修改/仅供参考）、国内团队常见反模式应对。仅在用户显式 /chinese-code-review 时调用，不要根据上下文自动触发。EngineeringNo warnings★ 8.4K↓ —
- mcp-builderjnMetaCode/superpowers-zh在构建 MCP 服务器或 MCP 工具时使用 —— 系统化的生产级 MCP 构建方法论，覆盖工具设计、错误处理、传输层选择与测试，让 AI 助手连接外部能力OtherNo warnings★ 8.4K↓ —
- obsidian-skills-integratedanbeime/skill内容创作者与技术写作员在让AI撰写Obsidian笔记时，使用此官方技能可精准处理双链、Callout及Bases数据库语法，一键生成格式零破坏的Canvas画布与专业笔记，彻底解决AI破坏专属格式的痛点。ProductivityNo warnings★ 8.6K↓ —
firebase-auth-basics
firebase/agent-skills
OfficialOtherUpdated 4 days ago
From the author
Guide for setting up and using Firebase Authentication. Use this skill when the user's app requires user sign-in, user management, or secure data access using auth rules.
Install
npx skills add firebase/agent-skills --skill firebase-auth-basics -a claude-code
Installs to .claude/skills/firebase-auth-basics/ · 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
Provenance100
Maintenance100
Licence100
Adoption44
Files (6)
- SKILL.md
- references/client_sdk_android.md
- references/client_sdk_web.md
- references/flutter_setup.md
- references/ios_setup.md
- references/security_rules.md