LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says…
GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.
Discord ops via the message tool (channel=discord).
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human…
Interact with Slack workspaces using browser automation.
>
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated…
OMC agent catalog, available tools, team pipeline routing, commit protocol, and skills registry.
Orchestrates lively group discussions between installed BMAD agents or custom personas, and helps author custom parties.
Reviews GitHub pull requests for the Medusa repository.
Operate notifications as one ECC-native workflow across GitHub, Linear, desktop alerts, hooks, and connected communication surfaces.
Checks if a community pull request is ready for human review. Verifies CLA signature, PR title format, description completeness, test coverage, and cubic-dev-ai issues, then triages to the right…
Review Clojure and ClojureScript code changes for compliance with Metabase coding standards, style violations, and code quality issues.
Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file.
Checks if a community pull request is ready for human review. Verifies CLA signature, PR title format, description completeness, test coverage, and cubic-dev-ai issues. Use when given a PR number…
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use.
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state…
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage.
Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints…
Communication & Collaboration agent skills on mcprush decide what leaves the building: what a message must show a person before it is sent, and what a status update is allowed to claim on somebody else’s behalf. The kinds are workflow, expertise, output format, voice & style and guardrail, and the one a skill belongs to is the fastest way to guess what it will do to your prompt.
What to look at before installing one is what it costs in context and what it takes away: a guardrail that refuses an action and a voice that rewrites a sentence are both skills, and only one of them will stop the agent doing something. Every skill here says which kind it is, what it costs in context, what it needs beside it to work and the licence it is published under, next to the publisher it came from and whether that publisher has been verified. The filters on the left narrow it further and the sort at the top decides what comes first.
A skill is not connected to anything: there is no endpoint to authorise and nothing routed through the gateway. Installing one drops a folder of instructions into the client’s own skill folder, and uninstalling it is deleting that folder. The exact line for each client is on the skill’s own page, because it differs by client rather than by skill.