Discover and install skills, docs, and rules to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
Azure/azure-sdk-for-net Query and modify CODEOWNERS ownership, service labels, and package associations in Azure SDK repositories. **UTILITY SKILL**. FOR SINGLE OPERATIONS: view, add, or remove owners and labels. WHEN: "code owners", "view codeowners", "add package owner", "remove package owner", "add label", "remove label", "codeowners blocked PR", "who owns this package", "create service label", "update codeowners cache", "unblock release". INVOKES: azsdk_engsys_codeowner_view, azsdk_engsys_codeowner_add_package_owner, azsdk_engsys_codeowner_add_label_owner, azsdk_check_service_label, azsdk_create_service_label, azsdk_engsys_codeowner_update_cache, azsdk_engsys_codeowner_check_package. | Skills | — |
ag-ui-protocol/ag-ui Keep the AG-UI .NET SDK at feature and wire-format PARITY with the canonical reference SDKs (TypeScript is the source of truth; Python is types/encoder only). USE FOR: porting a feature/event/behavior that landed in the TS (or Python) SDK into .NET, verifying the .NET wire format (JSON, SSE, protobuf) matches the reference, locating where the reference implementation and compatibility fixtures live, mapping a TS concept to the .NET event/client/encoder model, resolving an upstream protocol fix (e.g. a Microsoft.Extensions.AI / Microsoft Agent Framework issue) that needs a .NET counterpart, deciding which .NET package owns a change. DO NOT USE FOR: the mechanics of writing a specific test (use agui-dotnet-unit-tests for serialization round-trips, agui-dotnet-integration-tests for cross-language / E2E harness mechanics, agui-dotnet-wire-types for JSON/proto type rules, agui-dotnet-transport for SSE/HTTP transport details). This skill is about the PARITY PROCESS and where the reference lives, not test authoring. | Skills | — |
Rewrite text to sound collaborative, human, and on-brand for Metis Strategy Contains: metis-humanizer Rewrite text to sound collaborative and human, not pushy or authoritative, free of AI-generated writing patterns, and lightly in Metis Strategy's brand voice. Builds on the humanizer skill's detection catalog (inflated symbolism, promotional language, -ing tails, vague attribution, em dashes, rule of three, AI vocabulary, filler) and adds a Metis brand tint, an opt-in advisory register, document-type modes (email, proposal, exec summary, memo, slide copy), a consulting cliche ban, and a cinematic staging ban. Defaults to plain, peer-to-peer, non-authoritative tone. Use for Metis client-facing or internal prose. Trigger on "metis humanizer", "humanify", "make it human", "metis voice", "metis tone", "consultant tone", "make this sound like Metis", or "humanize for a client". | Skills | — |
n8n-io/n8n Configure MCP servers for n8n development in OpenCode. Use when the user says /setup-mcps or asks to set up MCP servers for n8n. | Skills | — |
n8n-io/n8n Configure MCP servers for n8n development. Use when the user says /setup-mcps or asks to set up MCP servers for n8n. | Skills | — |
n8n-io/n8n Guides adding, changing, and reviewing telemetry through the `@n8n/telemetry` event registry. Use when working on telemetry, analytics, tracking, product events, `track()` calls, or RudderStack/PostHog product events, in frontend or backend code — and whenever you need to find which registered telemetry events exist, what an event means, or what properties it carries. | Skills | — |
n8n-io/n8n Keeps implementation and specs in sync. Use when working on a feature that has a spec in .agents/specs/, when the user says /spec, or when starting implementation of a documented feature. Also use when the user asks to verify implementation against a spec or update a spec after changes. | Skills | — |
n8n-io/n8n Reproduce a bug from a Linear ticket with a failing test. Expects the full ticket context (title, description, comments) to be provided as input. | Skills | — |
n8n-io/n8n Product content designer for UI copy. Use when writing, reviewing, or auditing user-facing text: button labels, error messages, tooltips, empty states, modal copy, placeholder text, confirmation dialogs, onboarding flows, or i18n strings. Also use when the user says /copy, /content, or /ux-copy. | Skills | — |
n8n-io/n8n Quick reference for n8n patterns. Full docs /AGENTS.md | Skills | — |
n8n-io/n8n Guides work on `packages/frontend/editor-ui` experiments. Use when creating, extending, wiring, testing, reviewing, or retiring editor-ui experiments, PostHog feature flags, experiment key indexes, variants, stores/composables, persisted experiment state, or experiment telemetry. | Skills | — |
n8n-io/n8n Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs, security edge cases, and missing tests. Use when given a PR URL to review, or when the user says /human-like-code-review. | Skills | — |
n8n-io/n8n Adds or updates n8n Public API v1 endpoints, OpenAPI specs, and handler wiring. Use when creating public API handlers, registering paths in openapi.yml, or adding OpenAPI tags. Always use @PublicApiController for new endpoints (API-37+). | Skills | — |
n8n-io/n8n Applies n8n's RBAC scope decorators to REST endpoints. Use when creating a new @RestController, adding any @Get/@Post/@Put/@Patch/@Delete route to an existing controller, or reviewing endpoint authorization. Every authenticated endpoint must be gated by @ProjectScope or @GlobalScope. | Skills | — |
n8n-io/n8n Add OAuth2 credential support to an existing n8n node — creates the credential file, updates the node, adds tests, and keeps the CLI constant in sync. Use when the user says /node-add-oauth. | Skills | — |
n8n-io/n8n Deploy a temporary n8n test instance (or generate a local docker run command) via the internal "Nathan" bot, from the repo instead of Slack. Use after opening a PR to offer the user a live test instance, or whenever someone asks to spin up / deploy a test instance for a branch. | Skills | — |
n8n-io/n8n Fetch and display the full transcript from a Loom video URL. Use when the user wants to get or read a Loom transcript. | Skills | — |
n8n-io/n8n Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue. | Skills | — |
n8n-io/n8n Guidelines on using Design System styles and components. Use when working on .vue files in packages/frontend. Triggers for tasks that include component architecture, styling, UI changes, or feature work. | Skills | — |
n8n-io/n8n Authors n8n database migrations. Use when creating or modifying files under packages/@n8n/db/src/migrations/, when the user asks to add a column, table, index, foreign key, or backfill, or when the user mentions DB migrations or TypeORM migrations. | Skills | — |
Can't find what you're looking for? Evaluate a missing skill.