All categories
AI & Agents
LLMs, agent workflows, RAG, MCP, prompting, and AI app patterns
- 299,177
- 12,466
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse ai & agents skills
Showing 217–240 of 299,177 skills
- PrototypeThrowaway code that answers a design question before real implementation — slots between /orc:plan and /orc:start. Use when feeling out whether logic, a state machine, or a data shape holds up, or when comparing radically different UI variants on one route before committing to a design.Votes: 0GitHub stars: 6
- Prd WritingAuthor Product Requirements Documents (PRDs) from scratch — interview-driven, templated, published to docs/prds/NNNN-*.md. Use for "write a PRD for X", an unsettled new feature, or /orc:prd.Votes: 0GitHub stars: 6
- Postmortem WritingAuthor blameless incident postmortems — timeline, root cause(s), contributing factors, action items. Use after a production incident (outage, data loss, security event, regression) or a near-miss.Votes: 0GitHub stars: 6
- Postgresql Table DesignDesign or review a PostgreSQL-specific schema: data types, indexing, constraints, partitioning, RLS, performance patterns, and advanced features. Use when modeling or auditing PG tables.Votes: 0GitHub stars: 6
- Postgresql OptimizationWrite or review PostgreSQL-specific SQL: JSONB, arrays, custom/range/geometric types, indexing, full-text search, window functions, extensions, and RLS. Use for PG-unique features and code review.Votes: 0GitHub stars: 6
- Next Best PracticesNext.js best practices. Use when writing, reviewing, or refactoring Next.js code — App Router routing, RSC/server-client boundaries, data fetching, route handlers, metadata, image/font optimization.Votes: 0GitHub stars: 6
- Nestjs Best PracticesNestJS best practices and architecture patterns for production apps. Use when writing, reviewing, or refactoring NestJS code — modules, dependency injection, security, and performance.Votes: 0GitHub stars: 6
- Mobile Ios DesigniOS Human Interface Guidelines and SwiftUI patterns for native apps. Use when designing iOS interfaces, building SwiftUI views, or aligning apps with Apple's design principles.Votes: 0GitHub stars: 6
- Jira HierarchyThe Jira backlog contract — Epic-as-micro-PRD, Stories, concurrency-sliced Tasks, and the mandatory child-ticket template. Use when creating or restructuring Jira epics, stories, or task breakdowns, or when enforcing ticket structure — /orc:jira-breakdown and orc-jira-architect are built on it.Votes: 0GitHub stars: 6
- Jira CliAtlassian CLI (acli) reference for Jira work items — create, sub-task, link, view, JQL search, transition. Use to file/move/link a Jira ticket from the terminal or when /orc:jira is invoked.Votes: 0GitHub stars: 6
- Inline ReviewPost a real GitHub PR review with line-anchored inline comments; invoked by /orc:code-review after findings. For commenting on your OWN diff, prefer the bundled /code-review --comment.Votes: 0GitHub stars: 6
- Improve Codebase ArchitectureFind architecture-deepening opportunities in a codebase. Use when the user wants to improve architecture, find refactors, consolidate coupled modules, or make a codebase more testable and AI-navigable.Votes: 0GitHub stars: 6
- HandoffCompact the current conversation into a redacted handoff document, saved to the OS temp dir, that a fresh agent in another session or tool can pick up — /orc:resume is the counterpart for resuming in-repo orc state.Votes: 0GitHub stars: 6
- GrillingRound-based interview engine under orc's grill entry points (orc:grill-me, /orc:plan --grill, /orc:rfc --grill, /orc:flow medium+ scope). Use when stress-testing a plan or design decision-by-decision, or when a session must end with nothing left silently assumed.Votes: 0GitHub stars: 6
- Grill With DocsGrill a plan or design while writing the docs as you go — the interview plus a live glossary (CONTEXT.md) and ADRs captured the moment decisions land.Votes: 0GitHub stars: 6
- Grill MeA relentless decision-by-decision interview to sharpen a plan or design until reaching shared understanding.Votes: 0GitHub stars: 6
- Git CommitExecute git commit with conventional-commit analysis, intelligent staging, and message generation from the diff. Use when the user asks to commit changes, create a git commit, or mentions /commit.Votes: 0GitHub stars: 6
- Git Advanced WorkflowsAdvanced Git workflows - rebase, cherry-pick, bisect, worktrees, reflog - for clean history and recovery. Use when managing complex histories, collaborating on branches, or troubleshooting a repo.Votes: 0GitHub stars: 6
- GatesThe canonical AskUserQuestion conventions for every orc gate — class-tagged header chips, Recommended-first options, side-by-side `preview` for preview-then-confirm, multiSelect chunking, notes as the rewrite channel, and the --auto ladder. Use when about to render an orc gate.Votes: 0GitHub stars: 6
- Flow PhasesPer-phase playbooks for /orc:flow Phases 2–9, loaded one at a time as the flow reaches each phase. Use only from /orc:flow — Read the single references/PHASE-N-*.md for the phase being entered, never all of them.Votes: 0GitHub stars: 6
- Finishing A Development BranchGuide the completion of a development branch by presenting structured options for merge, PR, or cleanup. Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.Votes: 0GitHub stars: 6
- ExplainerBuild the narrated what-was-made walkthrough for a QA packet: script from plan + acceptance, demo pass, segments.json, animate graphics, kokoro narration, orc-explain assemble. Use from /orc:explain and the flow explainer gate. Not for QA itself.Votes: 0GitHub stars: 6
- Executing PlansExecute a written implementation plan batch-by-batch — load it, review critically, implement task by task, and stop for review between batches. Use when you have a written implementation plan to execute in a separate session with review checkpoints.Votes: 0GitHub stars: 6
- Evidence PublishDeliver a QA/evidence packet to a tracker or keep it local, behind an always-ask preview gate. Protocol for /orc:qa Phase 6, /orc:evidence, and any evidence-delivery step.Votes: 0GitHub stars: 6