agents-store
- 740 skills
- 0 followers
- yesterday last updated
- ▌ Theme Configuration 2 · agents-store bundleTheme shadcn/ui and shadcn studio projects — OKLCH CSS variables with @theme inline, light and dark variants, next-themes setup, next/font fonts, brand colors, style presets applied with shadcn apply, and installing shadcn studio themes. Use when changing colors, fonts or dark mode of a shadcn project.
- ▌ Generate Report · agents-storeGenerate a professional report (DOCX/PDF) Arguments: <title> [--format <docx|pdf>] [--type <annual|quarterly|project>].
- ▌ Keyword Research 2 · agents-storeRun keyword research for a topic or domain using DataForSEO Arguments: <keyword or domain>.
- ▌ Convert Document · agents-storeConvert between document formats (MD/DOCX/PDF/HTML/PPTX) Arguments: <input-file> --to <format>.
- ▌ Generate Invoice · agents-storeGenerate a professional invoice (PDF) Arguments: <invoice-number> [--company <name>] [--client <name>].
- ▌ Generate Contract · agents-storeGenerate a contract or agreement (DOCX/PDF) Arguments: <title> [--format <docx|pdf>] [--type <service|nda|employment>].
- ▌ Generate Estimate · agents-storeGenerate a professional cost estimate / quotation (PDF) Arguments: <estimate-number> [--company <name>] [--client <name>].
- ▌ Generate Proposal · agents-storeGenerate a professional business proposal (DOCX/PDF) Arguments: <title> [--format <docx|pdf>] [--company <name>].
- ▌ Competitor Analysis 3 · agents-storeCompare a domain against its competitors using DataForSEO Arguments: <domain>.
- ▌ Generate Presentation · agents-storeGenerate a professional presentation (PPTX) Arguments: <title> [--slides <number>] [--theme <corporate|minimal|bold>].
- ▌ Component Search 2 · agents-store bundleSearch and install components from the 400+ registries in the official shadcn directory — community registries such as magicui or aceternity, registries.json with its health status, adding registries to components.json, private GitHub registries. Use when looking for a component beyond the standard shadcn/ui and shadcn studio registries.
- ▌ Setup Registries · agents-storeSet up community shadcn registries, the shadcn MCP server, and CLAUDE.md section for a project Arguments: --mcp | --claudemd | --skill.
- ▌ Competitor Analysis 2 · agents-store bundleUse for competitor SEO research with DataForSEO Labs data - who competes for the same organic keywords, who ranks in the top 10 for a query, how domains compare on organic traffic, keywords and trend, a competitor's top pages, and keyword or domain gaps. Not for keyword ideation (keyword-research), backlink audits (backlink-audit) or page audits (site-audit).
- ▌ Search Components · agents-storeSearch across the shadcn registry directory (400+ registries) for UI components, blocks, and templates Arguments: <what-you-need>.
- ▌ Generate Act · agents-storeGenerate an Act of Completed Works (PDF) Arguments: <title> [--format <pdf|docx>].
- ▌ Generate Nda · agents-storeGenerate a Non-Disclosure Agreement (NDA) — PDF Arguments: [--type <mutual|unilateral>] [--party1 <name>] [--party2 <name>].
- ▌
- ▌ Performance Optimization 2 · agents-store bundleNext.js 16 performance — next/image and next/font setup, dynamic imports, bundle analysis, the React Compiler (stable in 16, experimental Rust compiler in 16.3), prefetching and Partial Prefetching, third-party scripts and Core Web Vitals (LCP, INP, CLS). Use when a page is slow or heavy. Caching strategy belongs to data-fetching.
- ▌ Server Client Components 2 · agents-store bundleServer and Client Components in the Next.js App Router — where to put 'use client', which props can cross the boundary, passing server components as children, context providers, wrapping third-party components, and keeping server-only code out of the client bundle with the server-only and client-only packages. Use when deciding or fixing component boundaries.
- ▌ Component Registry 2 · agents-store bundleInstall and use shadcn/ui and shadcn studio components with the shadcn CLI v4 — add, view, --dry-run and --diff, the @shadcn-studio and @ss-* registries, compositions that are not registry items such as form and date picker, and Base UI specifics like the render prop instead of asChild. Use when adding or composing components. Searching community registries is component-search.
- ▌ Project Scaffolding 2 · agents-store bundleScaffold and organise Next.js projects that use shadcn/ui — init with templates and the base choice (Base UI or Radix), shadcn studio templates, folder structure for ui, blocks and features, components.json aliases, the cn helper in lib/utils, and Turborepo monorepos with a shared ui package. Use when starting a project or deciding where components live.
- ▌ Create Collection · agents-storeCreate a new Directus collection with optional fields Arguments: <name> [--fields <field1:type,field2:type>] [--icon <icon>].
- ▌ Reconcile 2 · agents-storeSync the code and every document in one declared direction — the code is master and the documents get corrected, or the documents are master and the gaps become tasks Arguments: --master=code | --master=docs [--dry] [--only <documents>].
- ▌ Analyze Workflow · agents-storeAnalyze a workflow JSON or template before importing Arguments: <template-id-or-url>.
- ▌ Search Community · agents-storeSearch GitHub repos and community platforms for n8n workflows Arguments: <query> [--source <github|community|all>].
- ▌ Search Templates · agents-storeSearch the official n8n template library for ready-made workflows Arguments: <query> [--category <name>] [--nodes <nodeTypes>] [--mode <keyword|by_nodes|by_task|by_metadata>].
- ▌ App Router Patterns 2 · agents-store bundleNext.js 16 App Router routing conventions — layouts and templates, route groups, dynamic routes with async params and generateStaticParams, parallel routes (every slot needs default.tsx), intercepting routes for modals, proxy.ts replacing middleware.ts, and the Metadata API. Use when creating, restructuring or migrating routes. Error and loading files belong to error-handling, Route Handlers to api-design.
- ▌ Add Registries · agents-storeFetch the shadcn registries from the official endpoint (skipping unavailable and hidden ones) and add them to components.json Arguments: --filter <keyword>.
- ▌ Provision Instance · agents-storeRun a full instance provisioning session with multiple workflows Arguments: [--preset <startup|devops|marketing|custom>] [--dry-run].
- ▌ Template Discovery 2 · agents-store bundleSearch the official n8n template library (12,900+ templates). Use when asked to "search n8n templates", "find n8n workflow", "browse n8n template library", "n8n workflow catalog", "discover n8n automation", or need to find a template by keyword, node type, task, category, or architectural pattern.
- ▌ Troubleshoot 37 · agents-storeDiagnose a Chatwoot API / CLI / webhook problem — run read-only connectivity, auth, and scope checks against the configured instance and report the fix. Arguments: [object Object].
- ▌
- ▌ Dify Docker Architecture 2 · agents-store bundleDify Docker Compose deployment architecture — services, container naming, directory layout, .env.example and envs/ structure, and Docker project name conventions. Use when working with Dify Docker setup, understanding container services, debugging container issues, or needing to know the Dify directory structure. Triggers on "dify docker", "dify containers", "dify services", "dify architecture", "dify compose".
- ▌ Table Management 3 · agents-store bundleCreate, rename, duplicate and delete NocoDB tables, set the display field and description, including creating a table with its initial fields over MCP or REST (Meta API v3). Use when a NocoDB schema needs a new or changed table. Adding or changing columns is field-management.
- ▌ Crawl Site · agents-storeCrawl an entire website or map its structure Arguments: <url> [--depth <number>] [--limit <max-pages>] [--map-only].
- ▌ Item Operations 2 · agents-store bundleRead, query and write records (items) in a Directus collection with the items MCP tool - filters and sorting, deep queries across relations, many-to-any field selection, aggregation with groupBy, pagination, batch create, and update or delete by keys or by query. Use it for how-to questions about the data in a collection, in any language. For SDK code use sdk-patterns, for setting up relations and field types field-relations, for data model design schema-design.
- ▌ Snapshot Schema · agents-storeGet a schema snapshot — shows complete data model for one or more collections Arguments: collection1 collection2 ....
- ▌ Setup 28 · agents-storeSet up document generator preferences — style, language, company profile, and logo.
- ▌ Security Patterns 2 · agents-store bundleNext.js 16 security for production apps — security headers, nonce-based Content Security Policy in proxy.ts, CSRF and allowed origins for Server Actions, CORS for Route Handlers, rate limiting, server-only data access layers, environment variable safety, and keeping next patched against current security advisories. Use when hardening an app. Login and sessions belong to auth-patterns.
- ▌ Record Management 2 · agents-store bundleCreate, read, update and delete records in NocoDB tables — single and bulk creates, finding a record and changing it, counting records that match a condition, deduplicating and restoring deleted records. Use when working with the data inside a NocoDB table. Filter syntax is search-filter, CSV import and export is import-export, reports are views-and-reports.
- ▌
- ▌ Feedback 4 · agents-storeReport a problem with macstack-dev, the macstack.json schema, or the registry — and fix it at the source Arguments: <what went wrong>.
- ▌ Deploy Template · agents-storeDeploy an official n8n template to your instance Arguments: <template-id> [--name <custom-name>] [--no-auto-fix] [--keep-versions].
- ▌ Troubleshoot 36 · agents-store bundleDiagnose shadcn/ui and shadcn studio problems — components.json errors, Tailwind v3 or v4 mismatches, a missing cn helper after CLI 4.21, unstyled components or unset CSS variables, studio registry 401 or 403, dependency conflicts with React 19, hydration issues with next-themes. Use when an install, init or render fails.
- ▌ Instance Upgrade 2 · agents-store bundleUse when an OpenClaw instance or fleet is being upgraded, or when the question is which OpenClaw version to move to — version drift between instances, the current stable release, a release channel or registry dist-tag, an image tag or digest pin, a soak or hold-back window, a gateway that will not start after an update, schedules firing several times per tick, a session that expired after an update, or what a given OpenClaw release added.
- ▌ Research · agents-storeConduct comprehensive deep research on a topic using 7-step algorithm Arguments: <topic> [--type <competitive|market|technical|person|topic|news>] [--depth <quick|standard|deep>].
- ▌ Create Project · agents-storeCreate a new Dokploy project Arguments: <name> [--description <text>].
- ▌ MCP Tools 4 · agents-store bundleSet up and use the official shadcn MCP server (npx shadcn@latest mcp) — mcp init per client for Claude Code, Cursor, VS Code, Codex and opencode, its seven tools, how items are addressed as @registry/item, and why the community shadcn-ui-mcp-server is no longer shipped. Use when configuring or using MCP for shadcn component work.
- ▌ View Management 3 · agents-store bundleCreate, configure, and delete NocoDB views — Grid, Form, Gallery, Kanban, Calendar, Map, Gantt, Timeline, List. Use when: - "create a kanban view" - "add a calendar / gantt / timeline view" - "build a form for intake" - "make a gallery of products" - "set up filters on a view" - "delete a view" - "show / hide columns on a view"
- ▌ Codemap Explain 2 · agents-store bundleUse when the user wants existing code explained as a learner - what a file, function or module does, how a request or data flows through the project, why it was built that way, or a tour of a codebase. Gives a structured step-by-step explanation (context, data flow, details, pitfalls) pitched at the user's level, preferred to an ad-hoc answer when the user is learning the code. Not for code review (codemap-review) or diagrams (codemap-diagram).
- ▌ MCP Patterns 11 · agents-store bundleUse for how to call the DataForSEO MCP server - its tools (api_request, docs_search, docs_index, docs_list_sections), the docs-first cycle, request bodies and the .ai response mode - and to build the right call for an endpoint family without a task skill, such as SERP, Merchant, App Data or Business Data. Not for site audits, content analysis, page parsing, technologies or WHOIS (site-audit).
- ▌
- ▌ Explore Schema · agents-storeExplore the Directus schema — list all collections or get detailed field info for a specific collection Arguments: collection-name.
- ▌ Intake 2 · agents-storeTake in anything the client sends — a document, a returned review package, or a correction typed straight into this chat — and merge it through delta → ruling → apply Arguments: [file in inbox/ | what to change, in your own words | (empty = whatever is unprocessed)].
- ▌ Troubleshoot 35 · agents-store bundleUse when a Mattermost REST API call fails or behaves unexpectedly — 401 or 403 mid-session, an expired personal access token, 404 from names used instead of ids, 429 rate limits, missing rows from pagination, 400 on a write, no token after login, or behaviour that changed silently after a server upgrade such as v12 dropping webhook and bot identity props from posts. Maps symptoms to causes and fixes.
- ▌ Field Management 2 · agents-store bundleCreate, update and delete NocoDB fields across all 35 types, including select options, formulas, links with lookups and rollups, attachments, barcode and button fields, plus safe type changes and deletes. Use when a NocoDB table needs a new or changed column. Creating the table itself is table-management, hiding or ordering columns in a view is view-management.
- ▌ Test Frontend · agents-storeTest a running app's frontend — navigate pages, check UI, find errors, generate report Arguments: [url] — e.g. localhost:3000, http://localhost:8080/admin.
- ▌ Site Audit 2 · agents-store bundleUse for page and site inspection with DataForSEO OnPage, Content Analysis and Domain Analytics - Lighthouse and page speed, on-page SEO checks (title, meta, headings, alt text), site crawls, parsing a page's content, content and sentiment analysis for a keyword, the technologies a domain runs, and WHOIS data. Not for backlinks (backlink-audit), competitor comparison (competitor-analysis) or keyword research.
- ▌ Compare · agents-storeCompare multiple products, companies, or technologies Arguments: <item1> vs <item2> [vs <item3>...] [--criteria <criteria>].
- ▌ Search Items · agents-storeSearch items across a Directus collection using full-text search Arguments: <collection> <query>.
- ▌ Trigger Flow · agents-storeTrigger a Directus automation flow Arguments: <flow-name-or-id> <collection> [--keys <id1,id2>] [--data <json>].
- ▌ Troubleshoot 32 · agents-store bundleDiagnose Directus problems such as 401, 403, 404, 409, 422 and 500 responses on items, fields, relations or assets, MCP connection and tool-call errors, permission and policy issues, schema conflicts, slow queries, and flows that never fire or whose conditions never match. Use it for any Directus question about something failing or behaving unexpectedly. For Docker setup use docker-local-dev; for building flows use flow-automation.
- ▌ Filter Queries 2 · agents-store bundleThe grammY filter query syntax of bot.on. Covers the update tree (message, edited_message, channel_post, callback_query), colon paths such as message:text or message:entities:url, wildcard and shortcut forms (msg, edit, :text, :file), combining queries as OR arrays or AND chains, and how ctx is type-narrowed. Use when choosing which updates a handler receives. For command handlers use commands-and-keyboards, for handler order and next() use middleware.
- ▌ Troubleshoot 33 · agents-store bundleDiagnoses failures of the macstack-dev toolchain. Covers lint errors, prototypes that do not resolve or clone, Infisical profile and missing or wiped env keys, scaffold runs that overwrite files, contradict the architecture or leave env references unresolved, macstack/ folder faults (duplicate macstack.json, stripped anchors, homoglyph ids, unreadable client files) and plugin discovery failures. To run the validation use lint; for new client material use intake.
- ▌ Search Records · agents-storeSearch records in a NocoDB table by keyword Arguments: <table-name> <query>.
- ▌ Troubleshoot 34 · agents-store bundleUse when a Jira or Confluence Cloud REST call fails or behaves unexpectedly - 401 or 403 with a token that looks right (expired, or scoped and sent to the site URL), 404 from a wrong base path or a missing /wiki prefix, 400 from plain-text ADF or an unbounded JQL (only ORDER BY), 409 version conflicts on page updates, 429 rate limits, Agile or v1-only endpoints missing in v2. Not for first-time credentials (setup) or ordinary calls that work (jira-operations, confluence-operations).
- ▌ Read Url · agents-storeRead and extract content from a URL with fallback Arguments: <url> [--format <markdown|json|screenshot>].
- ▌ Troubleshoot 30 · agents-store bundleSymptom-to-cause lookup for an app, domain, database or proxy on Dokploy - a domain that does not open or resolve, an SSL certificate error on a new domain, 502 or 404 from Traefik while the container runs (Traefik dashboard), connection refused between containers (internal hostname), a known deploy or compose error such as a registry pull or port conflict, Dokploy MCP or API errors such as missing tools or 401. Not for a full failed-deploy walkthrough (debug-deploy) or reading logs (read-logs).
- ▌ N8n Troubleshoot 2 · agents-store bundleDiagnose n8n problems in workflow development — MCP connection failures for n8n-mcp-external and n8n-native-mcp, API errors by status code, publish failures such as PUBLISH_FORBIDDEN, execution failures, SQLITE_BUSY, a missing encryption key. Use when something in n8n fails. Validation and expression syntax are covered by n8n-validation-expert and n8n-expression-syntax.
- ▌ Data Fetching 2 · agents-store bundleNext.js 16 data fetching and caching in the App Router — Server Component fetching, parallel requests and Suspense streaming, Server Action mutations, revalidation with revalidatePath, revalidateTag, updateTag and refresh, ISR, and the use cache directive with cacheLife and cacheTag under cacheComponents. Use when loading, caching or invalidating data. Forms and validation are form-handling.
- ▌ Form Handling 2 · agents-store bundleNext.js forms with Server Actions — useActionState, useFormStatus, useOptimistic, zod validation with field errors, progressive enhancement, file uploads and the Form component. Use when building or fixing a form in the App Router. Choosing a Route Handler for an endpoint is api-design, refreshing data after a mutation is data-fetching.
- ▌ API Reference 19 · agents-store bundleNocoDB REST API reference for schema-development work — curl on Meta API v3. Loaded only on explicit cite. Use when: - "NocoDB REST API" - "API endpoints for tables/fields/views" - "create a table via API" - "what's in the OpenAPI spec" - "Meta API endpoints" - "field type schemas" - "Hook v3 payload" - "dashboard / widget API"
- ▌ CLI Reference 5 · agents-store bundleCommand-line access to NocoDB for schema work — curl recipes on Meta API v3 by resource, mapped to the commands of the official nocodb.sh script (installed with npx skills add nocodb/agent-skills). Loaded only on explicit cite. Use when: - "NocoDB CLI" - "NocoDB command line schema commands" - "how do I create a table with curl" - "nocodb.sh commands" - "NocoDB agent-skills CLI"
- ▌ CLI Reference 6 · agents-store bundleCommand-line access to NocoDB data -- curl recipes on the Data API v3 (records, links, attachments) and Meta API v3, mapped to the commands of the official nocodb.sh script (installed with npx skills add nocodb/agent-skills). Loaded only on explicit cite. Use when: - "NocoDB CLI commands" - "NocoDB curl recipes" - "NocoDB agent-skills" - "what CLI commands are available" - "nocodb.sh commands"
- ▌ Create Record · agents-storeCreate a new record in a NocoDB table Arguments: <table-name> <field=value pairs>.
- ▌ Search Filter 2 · agents-store bundleNocoDB filter syntax for searching, filtering and sorting records — the where clause and structured filter, text, numeric, date and multi-select operators, relative date ranges, AND/OR groups, null and empty checks, and sort objects. Use when writing or debugging a NocoDB query condition. Creating or changing records is record-management.
- ▌ Troubleshoot 31 · agents-store bundleUse when a Chatwoot API call, CLI command or webhook fails or misbehaves - 401 or 403 with a valid token, 404 or an HTML page instead of JSON, 422 request errors, 429 rate limits, a webhook signature that never matches, or a CLI that works locally but not in CI. It maps the symptom to the cause and the fix. For building bots and webhooks use webhooks-automation, for CLI usage cli-recipes.
- ▌ Create Field · agents-storeAdd a field of any of the 35 supported types to a NocoDB table Arguments: [table-name-or-id] [field-title] [field-type].
- ▌ Create Table · agents-storeCreate a new NocoDB table with optional initial fields Arguments: [base-name-or-id] [table-title].
- ▌ MCP Patterns 9 · agents-store bundleNocoDB MCP for schema-development work — what the server lists directly, which schema tools hide behind listTools/callTool, and the Community vs Cloud/licensed contract. Use when: - "what MCP tools can I use for schema?" - "can MCP create tables / fields / views?" - "listTools / callTool" - "how do I discover NocoDB structure?" - "MCP for nocodb-dev"
- ▌ Build Report · agents-storeBuild an aggregation report from NocoDB table data Arguments: <table-name> [aggregation-type] [field].
- ▌ List Records · agents-storeList records from a NocoDB table with optional filtering Arguments: <table-name> [where-filter].
- ▌ MCP Patterns 10 · agents-store bundleNocoDB MCP tools reference for data work -- which tools the server lists, which sit behind listTools/callTool, the Community vs Cloud/licensed contract, and the exact parameter shapes (100-record batches, sort objects, filter vs where, date sub-operators). Use when: - "what NocoDB tools are available?" - "how do I query records?" - "show me NocoDB MCP parameters" - "which tool do I use for..." - "NocoDB tool reference" - "listTools / callTool"
- ▌ Search · agents-storeSearch the web using optimal provider with automatic fallback Arguments: <query> [--type <web|code|academic>].
- ▌ Update Workflow 2 · agents-store bundleGit and backup workflow for updating self-hosted Dify — pick the target tag, pre-flight the bundled Weaviate migration path, back up volumes with the stack down, merge into dev, handle conflicts, pull images, verify, roll back. Use when updating Dify, merging upstream changes, handling merge conflicts in Dify, backing up before an update, or switching to a specific Dify version/tag. Triggers on "update dify", "pull dify changes", "merge main into dev", "upgrade dify", "dify version", "dify backup", "weaviate upgrade".
- ▌ Create Item · agents-storeCreate a new item in a Directus collection Arguments: <collection> <field=value> [field=value...].
- ▌ Compose Logs · agents-storeRead the logs of EVERY container in a Dokploy Docker Compose stack and highlight errors Arguments: <compose-name-or-id> [--tail <N>] [--since <1h>] [--search <term>] [--errors-only].
- ▌ Debug Deploy 2 · agents-store bundleEnd-to-end recovery of a failed or misbehaving Dokploy deployment, covering failed or errored builds, deployments stuck in running or queued, a redeploy marked done while the old version is still served, crash-looping containers, 502 and 504 after a deploy, safe rollback, and verifying the fix. Use it for any Dokploy deploy that is not working, in any language. For one known symptom use troubleshoot; for reading logs only use read-logs.
- ▌ Add Webhook · agents-storeConfigure a NocoDB webhook (HookV3) on a table Arguments: [table-name-or-id] [event] [destination].
- ▌ Create View · agents-storeCreate a Grid / Form / Gallery / Kanban / Calendar / Map / Gantt / Timeline / List view Arguments: [table-name-or-id] [view-type] [view-title].
- ▌ List Fields · agents-storeList all fields on a NocoDB table with their types Arguments: table-name-or-id.
- ▌ Create View 2 · agents-storeCreate a new view for a NocoDB table Arguments: <table-name> <view-type> [title].
- ▌ List Files · agents-storeList files in Directus with optional folder or type filter Arguments: [--folder <name>] [--type <mime-prefix>].
- ▌
- ▌ List Items · agents-storeList items from a Directus collection with optional filters Arguments: <collection> [--filter <field=value>] [--sort <field>] [--limit <n>].
- ▌ Sdk Patterns 6 · agents-store bundlegrammY (Telegram bot framework) code patterns - creating a Bot, reading the Context (ctx.from, ctx.chat), handlers with bot.command, bot.hears and bot.on, ctx.reply versus ctx.api or bot.api for other chats and scheduled posts, editing and deleting messages, bot.init, and typing a custom Context with plugin flavors (session). Use for how-do-I-write-this questions in grammY code. For filter queries use filter-queries, for keyboards commands-and-keyboards, for session storage sessions.
- ▌ N8n CLI Recipes 2 · agents-store bundleThe n8n server CLI for self-hosted instances (execute, export and import of workflows and credentials, publish and unpublish, entities backup, user reset, security audit, community nodes) in npm, Docker or Docker Compose installs. Use when the task is an n8n command run on the host or in the container rather than a REST API or MCP tool call.
- ▌ N8n Code Python 2 · agents-store bundleWrite Python in n8n Code nodes (native Python, `language` pythonNative, n8n 2.x). Use when the user explicitly wants Python in a Code node, when migrating old Pyodide/"Python (Beta)" code that used _input/_json/_node/_now, or when a Python Code node fails with NameError, "Security violations detected", "Import of standard library module … is disallowed", "__build_class__ not found", "A 'json' property isn't a dictionary", or "Python runner unavailable". Covers the only two variables (_items/_item), dict-only access, imports blocked by default, the sandbox's denied builtins, accepted return shapes, and how errors interact with onError. JavaScript is the default for Code nodes — native Python has no n8n helpers and, by default, no imports. EXCEPTION — for Python in the AI-agent-callable Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode), use the n8n-code-tool skill instead (input is _query, return must be a string).
- ▌ Troubleshoot 29 · agents-store bundleDiagnose Next.js 16 errors — hydration mismatches, 'use client' and server-only errors, build failures such as dynamic server usage, Cache Components errors like blocking-prerender and next-request-in-use-cache, next/image host errors, slow dev or build, and deployment problems. Use when something fails or behaves unexpectedly in a Next.js app.
- ▌ Add Relation · agents-storeSet up a Link between two NocoDB tables, optionally with a Lookup Arguments: [from-table] [to-table] [cardinality].