Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 73591–73620 of 75677 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| zapierericrisco/rsc-harnessUse when operating Zapier from an agent through the official hosted Zapier MCP server — connecting with a bearer key, discovering an app's actions, enabling one, and invoking a read or write action or firing a Catch Hook trigger across thousands of apps by natural language. Note there is no public API for creating or updating your own Zaps on a normal account, so say so and route onward. NOT deciding what a flow should be or its error and dedup design (that is `automation-flows`), NOT workflow CRUD, which `n8n` and `make` do support. | Stars: 622 | Updated | Claude CodeCodex | Unverified | Install |
| claw-orchestratorEnderfga/claw-orchestratorManage persistent coding sessions across Claude Code, Codex, Antigravity (agy), Grok Build, OpenCode, any Agent Client Protocol agent (Kimi Code, dsh) and custom CLIs. Use when orchestrating multi-engine coding agents, starting/sending/stopping sessions, running durable, resumable workflows (solve / fanout / council / Codex goal) and having the runtime verify the result against an acceptance contract, fanning one task out to several engines, running multi-agent council collaborations, cross-session messaging, ultraplan deep planning, ultrareview parallel code review, autoloop autonomous workspace iteration, ultraapp building deployable web apps from a structured Q&A interview, switching models/tools at runtime, running Claude sessions under several Claude accounts with rotation at the usage limit, tracking per-turn cost and spend caps across engines, exposing the orchestrator's 79 tools as an MCP server to Hermes Agent / Claude Desktop / Cursor / Cline / Continue / Zed / Windsurf / Goose, or running as an Agent Client Protocol (ACP) agent that Zed / JetBrains / Neovim / Emacs / VS Code / dsh can drive directly. Triggers on "start a session", "send to session", "run council", "ultraplan", "ultrareview", "autoloop", "ultraapp", "Forge tab", "build a web app", "one-click app", "AppSpec", "autonomous iteration", "iterate until goal", "auto research", "switch model", "hand off a session", "session handoff", "switch engine", "continue on codex", "continue on claude", "move this session to another engine", "multi-agent coding", "coding session", "session inbox", "grok session", "grok build", "opencode", "mcp server", "clawo-mcp", "hermes mcp", "model context protocol", "ultracode", "dynamic workflow", "fanout", "fan-out", "best-of-N", "steer turn", "interrupt turn", "fork thread", "rollback turns", "acp", "agent client protocol", "clawo acp", "zed agent", "jetbrains agent", "external agent", "dsh subagent", "deepseek harness", "acp engine", "acp agent", "kimi code", "kimi | Stars: 614 | Updated | Claude CodeCodex | Unverified | Install |
| ultraapp-interviewEnderfga/claw-orchestratorUse when the user opens a Forge tab in the claw-orchestrator dashboard to start building a new ultraapp. Drives a structured Q&A interview that produces a complete AppSpec, then signals readiness to build. | Stars: 614 | Updated | Claude CodeCodex | Unverified | Install |
| analyzing-ci-flakinessopsmill/infrahubAnalyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal ledger so flakiness can be tracked over time. TRIGGER when: the user wants to find flaky tests, correlate recent CI failures, check which tests fail across PRs or recover on retry, or refresh the flakiness trend report. DO NOT TRIGGER when: babysitting a single PR's CI until green → monitoring-pull-requests; diagnosing or fixing one specific failing test → the bug-analysis skills. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| audit-docsopsmill/infrahubAudits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers, reports gaps, and optionally applies the fixes. TRIGGER when: the user wants to audit or check documentation coverage, find doc gaps after a feature branch, or verify docs are still current for a subject or specific files. DO NOT TRIGGER when: authoring new documentation from scratch → the writing-infrahub-docs skill from the OpsMill skills plugin; only linting/formatting Markdown → run `uv run invoke docs.lint`. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| commitopsmill/infrahubStages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| creating-changelog-entriesopsmill/infrahubUse when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or opening a PR, or whenever asked to add a changelog entry, towncrier fragment, or news fragment. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| creating-issuesopsmill/infrahubTurns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| creating-prdopsmill/infrahubSynthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| grilling-ideasopsmill/infrahubStress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| harvesting-reviewopsmill/infrahubMines a pull request's review threads for lessons that generalize beyond that PR, reconstructs each against the actual code before deciding, checks whether it is already codified, and routes the genuinely-new, durable ones into Infrahub's internal documentation — `dev/knowledge/`, `dev/guides/`, `dev/guidelines/`, the `AGENTS.md` files, and `.agents/rules/` — proposing edits first and applying only with the user's approval. TRIGGER when: the user wants to turn PR review feedback into durable conventions, guidelines, or rules; capture recurring reviewer comments as internal documentation; or check whether review lessons are reflected in the knowledge/guides/guidelines/AGENTS.md/rules layer. DO NOT TRIGGER when: sweeping a feature's changes for documentation coverage across all layers → use `audit-docs`; extracting knowledge from completed spec directories → `speckit-opsmill-extract`; only replying to or resolving review threads → normal git/gh flow. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| migrate-feature-pageopsmill/infrahubMigrate Infrahub docs feature pages from the legacy topic+guide pair into a cleaner structure (single merged page, hub+spokes, or tutorial extraction). Supports both single-feature migrations (one feature like Profiles or Webhooks) and section-wide migrations (a whole section like Branches & Change Control with multiple features migrated together) when the team has agreed on a section-wide restructure plan. Trigger when the user names a specific feature or section to migrate (e.g. "let's migrate profiles", "start the Resource Manager migration", "do the entire Branches & Change Control section"). Each migration is its own branch off `demo/groups-diataxis-example`, its own PR back to that branch. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| monitoring-pull-requestsopsmill/infrahubWatches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| neo4j-cypher-guideopsmill/infrahubComprehensive guide for writing modern Neo4j Cypher queries. Essential for text2cypher MCP tools and LLMs generating Cypher queries. Covers removed/deprecated syntax, modern replacements, CALL subqueries for reads, COLLECT patterns, sorting best practices, set-based writes, Quantified Path Patterns (QPP) for efficient graph traversal, and how to choose the entry point of a query so the plan starts with an index seek instead of a label scan. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| opsmill-dev-analyzing-bugsopsmill/infrahubPerforms root-cause analysis of a bug — from a GitHub issue, an issue URL, or a free-text description — before any reproduction or fix is written. TRIGGER when: triaging or diagnosing a bug, investigating why something misbehaves, an issue number/URL handed over for analysis, needing the root cause before touching code. DO NOT TRIGGER when: a failing reproduction test already exists and you are ready to fix → opsmill-dev-fixing-bugs; writing that reproduction test → opsmill-dev-test-driving-bugs; capturing a new bug as a ticket → opsmill-dev-creating-issues. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| opsmill-dev-fixing-bugsopsmill/infrahubImplements and validates the fix for a bug once a failing reproduction test exists. TRIGGER when: a bug has a failing reproduction test and you are ready to make it pass, implementing the root-cause fix, the final step of the bug-fixing pipeline. DO NOT TRIGGER when: no reproduction test exists yet → opsmill-dev-test-driving-bugs; still diagnosing, or asked to fix a bug with no analysis or reproduction test yet → opsmill-dev-analyzing-bugs. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| opsmill-dev-test-driving-bugsopsmill/infrahubWrites a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written. TRIGGER when: a bug has a completed root-cause analysis and you need the failing reproduction test, writing a test that proves a bug exists, the second step of the bug-fixing pipeline. DO NOT TRIGGER when: still triaging or diagnosing the bug → opsmill-dev-analyzing-bugs; implementing the fix once the test exists → opsmill-dev-fixing-bugs; general feature test-first work → superpowers test-driven-development. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| propsmill/infrahubOpens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| pre-ciopsmill/infrahubRun all locally-executable CI checks (format, lint, unit tests) for the areas you changed | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| rebaseopsmill/infrahubRebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| reviewing-pull-requestsopsmill/infrahubReviews a pull request in a separate subagent that has not seen this conversation, applying the rules in REVIEW.md. TRIGGER when: this session has just opened a pull request, for example with `gh pr create`; the user asks for a review of a pull request by URL or number; or a hook reports that large changes were pushed to a pull request. DO NOT TRIGGER when: answering existing review comments → addressing-review; watching CI → monitoring-pull-requests. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| speckit-agent-context-updateopsmill/infrahubRefresh the managed Spec Kit section in coding agent context file(s) | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| speckit-analyzeopsmill/infrahubPerform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| speckit-checklistopsmill/infrahubGenerate a custom checklist for the current feature based on user requirements. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| speckit-checkpoint-commitopsmill/infrahubCommit changes at meaningful checkpoints throughout the workflow | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| speckit-clarifyopsmill/infrahubIdentify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| speckit-constitutionopsmill/infrahubCreate or update the project constitution from interactive or provided principle inputs. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| speckit-convergeopsmill/infrahubAssess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| speckit-critique-runopsmill/infrahubPerform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation. | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |
| speckit-git-commitopsmill/infrahubAuto-commit changes after a Spec Kit command completes | Stars: 553 | Updated | Claude CodeCodex | Unverified | Install |