with one click
credential-setup-with-computer-use
// 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.
// 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.
Designs and manages n8n Data Tables directly with the data-tables and parse-file tools. Use when the user asks to 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 planning workflows that create or write to Data Tables.
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.
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.
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.
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.
Quick reference for n8n patterns. Full docs /AGENTS.md
| name | credential-setup-with-computer-use |
| description | 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. |
| recommended_tools | ["research","ask-user","browser_connect","browser_tab_open","browser_navigate","browser_snapshot","browser_content","browser_click","browser_type","browser_capture_secret","browser_create_credential"] |
Use this skill only when Computer Use browser tools are available. Do not use
delegate or any non-Computer-Use browser bridge.
research(action="fetch-url") when a docs URL
is available. Use research(action="web-search") only when docs are missing
or clearly outdated. Do not navigate the browser to docs.browser_connect if no browser session is active, then open or navigate
to the external service console with browser_tab_open or
browser_navigate.browser_content for page text and browser_snapshot when you need refs
for browser_click, browser_type, or secret capture.ask-user when the user must choose a project, app name, account,
workspace, scope set, description, or resource. Do not invent these values.ask-user.browser_snapshot first. Use
interactive: false when the secret is static page text rather than an input.browser_capture_secret using either a snapshot ref
for an input or a redactedKey marker for visible text.credentialsKey for every captured field in one credential.browser_create_credential. Put literal,
non-secret values in data; put captured secret field names in
resolveData.browser_snapshot before clicking, typing, selecting, or
capturing. Refs from old snapshots are stale.browser_content for reading and browser_snapshot for interaction.
Use screenshots only when visual layout matters.After browser_create_credential succeeds, call the relevant n8n credential or
workflow setup tool again so the new credential can be selected or applied. If
the user must finish sign-in, 2FA, consent, or manual entry, tell them exactly
what to do in the browser or n8n setup card, without asking for secrets in chat.