Skill-uri pentru agenți pe care le poți verifica înainte să le instalezi
Skill-uri SKILL.md publice din depozite GitHub cu peste 50 de stele și de la producători, scanate și evaluate. Instalează oricare dintre ele cu o singură comandă în Claude Code, Cursor, Codex, GitHub Copilot sau Gemini CLI.
44.930 de skill-uri din 2.133 de depozite · actualizat acum 2 minute
44.930 de skill-uri
- office-hoursmvschwarz/openrigYC-style product validation using six forcing questions. Pressure-tests a feature idea before it becomes a requirement — ensuring real demand, a clear wedge, and evidence behind assumptions.TestareFără avertismente★ 8,1 K↓ —Apare și în 1 alt depozit
- 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).PlanificareFără avertismente★ 8,1 K↓ —
- session-compaction-and-restoremvschwarz/openrigUse 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).ProductivitateFără avertismente★ 8,1 K↓ —
- 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).PlanificareFără avertismente★ 8,1 K↓ —
- context-buildermvschwarz/openrigGather and distill context from meetings, competitors, regulatory sources, and internal discussions. Produces background.md for a feature and updates shared context docs when new knowledge is discovered.ProductivitateFără avertismente★ 8,1 K↓ —Apare și în 1 alt depozit
- agent-operated-softwaremvschwarz/openrigUse 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.PlanificareFără avertismente★ 8,1 K↓ —
- agent-operated-workflowsmvschwarz/openrigUse 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.InginerieFără avertismente★ 8,1 K↓ —
- 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.AlteleFără avertismente★ 8,1 K↓ —
- 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.AlteleFără avertismente★ 8,1 K↓ —
- human-in-the-loopmvschwarz/openrigUse 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.AlteleFără avertismente★ 8,1 K↓ —Apare și în 1 alt depozit
- queue-handoffmvschwarz/openrigUse 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.AlteleFără avertismente★ 8,1 K↓ —
- 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.ProductivitateFără avertismente★ 8,1 K↓ —
- openrig-usermvschwarz/openrigUse when a specific `rig` command, subcommand, or flag is already known and you need its exact syntax, JSON shape, defaults, or error meaning. NOT for natural capability discovery, open-ended how-do-I questions, or choosing which OpenRig move applies.PlanificareFără avertismente★ 8,1 K↓ —
- mission-slice-sopmvschwarz/openrigUse when starting, building, handing off, restoring, or closing a mission or slice under the default lightweight SDLC.AlteleFără avertismente★ 8,1 K↓ —
- vault-usermvschwarz/openrigUse when checking the health of this rig's HashiCorp Vault or writing, reading, listing, deleting or explaining its secrets.RedactareFără avertismente★ 8,1 K↓ —
- oversight-teammvschwarz/openrigUse when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention ladder (orchestrator-ping -> refocus -> human escalation), and the cheap+deep model economics. NOT for orchestrating your OWN rig (orchestration-team) and NOT the intervention primitive mechanics (watchdog).ProductivitateFără avertismente★ 8,1 K↓ —Apare și în 1 alt depozit
- development-teammvschwarz/openrigUse when a development pod begins or hands off implementation, QA, or design work.TestareFără avertismente★ 8,1 K↓ —Apare și în 1 alt depozit
- agent-browsermvschwarz/openrigBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.BrowserFără avertismente★ 8,1 K↓ —Apare și în 1 alt depozit
- software-for-agentsmvschwarz/openrigUse when older OpenRig instructions name software-for-agents or describe agent-in-the-middle or studio software under the former skill name.AlteleFără avertismente★ 8,1 K↓ —
- 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.MediaFără avertismente★ 8,1 K↓ —Apare și în 1 alt depozit
- backlog-capturemvschwarz/openrigQuickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.AlteleFără avertismente★ 8,1 K↓ —Apare și în 1 alt depozit
- 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.PlanificareFără avertismente★ 8,1 K↓ —Apare și în 2 alte depozite
- systemic-issue-triageGentleman-Programming/gentle-aiTrigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.AlteleFără avertismente★ 8 K↓ —Apare și în 1 alt depozit
- dogfoodmvschwarz/openrigSystematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.TestareFără avertismente★ 8,1 K↓ —Apare și în 1 alt depozit
csharp-developer
Jeffallan/claude-skills
DateActualizat acum 4 zile
De la autor
Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Builds REST APIs using minimal or controller-based routing, configures database access with Entity Framework Core, implements async patterns and cancellation, structures applications with CQRS via MediatR, and scaffolds Blazor components with state management. Invoke for C#, .NET, ASP.NET Core, Blazor, Entity Framework, EF Core, Minimal API, MAUI, SignalR.
Instalare
npx skills add Jeffallan/claude-skills --skill csharp-developer -a claude-code
Se instalează în .claude/skills/csharp-developer/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Descarcă .zip
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
La ce are acces
Doar instrucțiuniNu am văzut acces la rețeaLicență: MIT
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 92
Securitate100
Proveniență89
Întreținere100
Licență100
Adopție64
Fișiere (6)
- SKILL.md
- references/aspnet-core.md
- references/blazor.md
- references/entity-framework.md
- references/modern-csharp.md
- references/performance.md