Agent Skills

extract-errors

✓★ 246,273

by facebook

Use when adding new error messages to React, or seeing "unknown error code" warnings.

🧰 Not standalone — use together with react/react

n8n:create-issue

★ 195,330

by n8n-io

Create Linear tickets or GitHub issues following n8n conventions. Use when the user asks to create a ticket, file a bug, open an issue, or says /create-issue.

🧰 Not standalone — use together with n8n-io/n8n

n8n:create-pr

★ 195,330

by n8n-io

Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.

🧰 Not standalone — use together with n8n-io/n8n

n8n-cli

★ 195,330

by n8n-io

Use the n8n CLI to manage workflows, credentials, executions, and more on an n8n instance. Use when the user asks to interact with n8n, automate workflows, manage credentials, or operate their instance from the command line.

🧰 Not standalone — use together with n8n-io/n8n

n8n:create-instance-ai-eval

★ 195,330

by n8n-io

Authors a new Instance AI workflow eval case in packages/@n8n/instance-ai/evaluations/data/workflows — build cases, behaviour/process cases, credential cases, and seeded (mid-conversation) cases — with intent-driven expectations calibrated against a real build. Use when adding or changing an Instance AI workflow eval, or debugging why one is flaky.

🧰 Not standalone — use together with n8n-io/n8n

credential-setup-with-computer-use

★ 195,330

by n8n-io

Guides n8n credential setup through Computer Use browser tools. Use when a user needs OAuth apps, API keys, client IDs, client secrets, or other credential values from an external service console.

🧰 Not standalone — use together with n8n-io/n8n

n8n:db-migrations

★ 195,330

by n8n-io

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.

🧰 Not standalone — use together with n8n-io/n8n

debugging-executions

★ 195,330

by n8n-io

Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.

🧰 Not standalone — use together with n8n-io/n8n

post-build-flow

★ 195,330

by n8n-io

Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.

🧰 Not standalone — use together with n8n-io/n8n

n8n:linear-issue

★ 195,330

by n8n-io

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.

🧰 Not standalone — use together with n8n-io/n8n

n8n:community-pr-readiness-check

★ 195,330

by n8n-io

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 Linear team or recommends a close. Use when given a PR number or branch name to review, or when the user says /community-pr-readiness-check, or asks to check if a PR is ready for review.

🧰 Not standalone — use together with n8n-io/n8n

data-table-manager

★ 195,330

by n8n-io

Designs and manages n8n Data Tables directly with the data-tables and parse-file tools. Use when the user asks to list, show, create, inspect, import, seed, query, update, clean up, rename columns in, or delete data tables and rows, especially from CSV/XLSX/JSON attachments, and before building or planning workflows that create or write to Data Tables.

🧰 Not standalone — use together with n8n-io/n8n

workflow-builder

★ 195,330

by n8n-io

Default path for all single-workflow work: new one-off workflows, existing- workflow edits, verification repairs, and workflow-local data tables. Write or edit a workspace source file, then call build-workflow with filePath. Do not load planning or create-tasks first. Load planning only when multiple coordinated workflows or shared cross-task data tables require a dependency-aware task graph.

🧰 Not standalone — use together with n8n-io/n8n

n8n:spec-driven-development

★ 195,330

by n8n-io

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.

🧰 Not standalone — use together with n8n-io/n8n

planned-task-runtime

★ 195,330

by n8n-io

Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, create-tasks silence rules, and detached delegate completion. Load whenever any of these tags appear or after spawning create-tasks or delegate.

🧰 Not standalone — use together with n8n-io/n8n

planning

★ 195,330

by n8n-io

ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first. Do NOT use for new one-off workflows, single-workflow edits, verification-only requests, or standalone data-table ops — use workflow-builder or data-table-manager instead.

🧰 Not standalone — use together with n8n-io/n8n

n8n:loom-transcript

★ 195,330

by n8n-io

Fetch and display the full transcript from a Loom video URL. Use when the user wants to get or read a Loom transcript.

🧰 Not standalone — use together with n8n-io/n8n

n8n:create-skill

★ 195,330

by n8n-io

Guides users through creating effective Agent Skills. Use when you want to create, write, or author a new skill, or asks about skill structure, best practices, or SKILL.md format.

🧰 Not standalone — use together with n8n-io/n8n

n8n:content-design

★ 195,330

by n8n-io

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.

🧰 Not standalone — use together with n8n-io/n8n

n8n:experiments

★ 195,330

by n8n-io

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.

🧰 Not standalone — use together with n8n-io/n8n

n8n:human-like-code-review

★ 195,330

by n8n-io

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.

🧰 Not standalone — use together with n8n-io/n8n

n8n-docs-assistant

★ 195,330

by n8n-io

Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs. Use when the user asks how to configure, set up, troubleshoot, or understand n8n behavior, especially credential setup questions opened from the credential modal.

🧰 Not standalone — use together with n8n-io/n8n

heap-snapshot-analysis

✓★ 187,144

by microsoft

Analyze V8 heap snapshots to investigate memory leaks and retention issues. Use when given .heapsnapshot files, asked to compare before/after snapshots, asked to find what retains objects, or investigating why objects survive GC. Provides snapshot parsing, comparison, retainer-path helpers, and scratchpad scripts.

🧰 Not standalone — use together with microsoft/vscode

memory-leak-audit

✓★ 187,144

by microsoft

Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.

🧰 Not standalone — use together with microsoft/vscode

author-contributions

✓★ 187,144

by microsoft

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

🧰 Not standalone — use together with microsoft/vscode

project-setup-info-context7

✓★ 187,144

by microsoft

Comprehensive setup steps to help the user create complete project structures in a VS Code workspace. This tool is designed for full project initialization and scaffolding, not for creating individual files. When to use this tool: when the user wants to create a new complete project from scratch; when setting up entire project frameworks (TypeScript projects, React apps, Node.js servers, etc.); when initializing Model Context Protocol (MCP) servers with full structure; when creating VS Code exte

🧰 Not standalone — use together with microsoft/vscode

accessibility

✓★ 187,144

by microsoft

Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.

🧰 Not standalone — use together with microsoft/vscode

cpu-profile-analysis

✓★ 187,144

by microsoft

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-*.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating user timing marks.

🧰 Not standalone — use together with microsoft/vscode

fix-ci-failures

✓★ 187,144

by microsoft

Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix. Requires the `gh` CLI.

🧰 Not standalone — use together with microsoft/vscode

find-release

✓★ 177,640

by flutter

A skill to find the lowest Dart and Flutter release containing a given commit. Use this skill whenever users ask about when a commit landed in Flutter or Dart releases, inquire about release versions for specific SHAs, or want to know if a commit is included in stable, beta, or dev channels for Flutter/Dart projects.

🧰 Not standalone — use together with flutter/flutter