Results for “node”

Choose automatic layouts for diagrams made of connected nodes. Match algorithms and tools to the graph structure, then plan connector routes, overlap handling, and stable placement so readers can follow relationships and edits remain predictable.

• Reducing crossings in a dependency graph
• Routing ERD connectors around tables
• Choosing layouts for trees and networks

Node-RED visual automation flows for Home Assistant. Covers visual automation, flow JSON, trigger-state, api-call-service, function nodes, context storage, timer patterns, error handling, and node-red-contrib-home-assistant-websocket nodes. Use when user mentions "Node-RED", "flow", "visual automation", or "node-redflöde".

The English summary is being prepared. Showing the original description.

Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't use for pod-level application failures (use gke-workload-troubleshooting), autoscaler scale-up/scale-down decisions (use gke-cluster-autoscaler), or non-GKE compute.

The English summary is being prepared. Showing the original description.

在授权测试中核验 Node.js 权限模型（--permission / --experimental-permission，及旧 policy.json）能否被内部 API 绕过。当目标依赖 Node.js Permission Model 做沙箱隔离、需要判断给定 Node 版本下是否存在已知逃逸（inspector 断点、process.binding、fs.statfs/openAsBlob、process.mainModule.require、Module._load、path.resolve 覆盖、Uint8Array 路径、符号链接重命名）时使用。适用目标类型 Node.js 运行时 / 依赖权限模型的服务或 CLI。触发场景包括用户说"这个 Node 权限模型靠谱吗""--permission 能被绕过吗""测下 policy.json 沙箱逃逸""inspector/process.binding 能突破权限吗"。输出：给定 Node 版本下各绕过原语的命中矩阵 + 建议升级版本（含 killed 记录）。

The English summary is being prepared. Showing the original description.

Add clear runtime reporting to Python, PowerShell, or Node.js batch scripts. Design start messages, progress counts, item failures, and final summaries while preserving existing result output, error handling, and exit codes, then verify visibility during execution.

• Add progress reporting to long-running batch scripts
• Report individual failures and final outcome counts
• Keep progress logs separate from machine-readable results

Apply consistent coding practices across TypeScript, JavaScript, React, and Node.js projects. Get guidance on naming, types, error handling, API design, file organization, and tests to make code easier to read and maintain.

• Aligning coding conventions across a team
• Refactoring long functions and deeply nested code
• Reviewing React components and state updates

Guides background processing in Node.js and TypeScript with BullMQ and Redis. Covers job queues, which hold tasks for later execution, along with scheduling, priorities, rate limits, worker concurrency, and dependencies between processing steps.

• Design a queue for background tasks
• Schedule jobs for later or repeated execution
• Organize dependent steps into a job flow

Organize Node.js, Express, and TypeScript APIs into layers with clear responsibilities. This guide covers request handling, business logic, database access, input validation, error tracking, configuration, and testing to support consistent implementation and refactoring across services.

• Adding an API endpoint with clearly separated responsibilities
• Organizing database access through Prisma
• Adding input validation and error tracking

Write Python for n8n Code nodes to transform, filter, aggregate, and validate workflow data. Get guidance on reading input items, returning the required JSON structure, using standard library modules, and avoiding common errors within n8n's Python execution modes.

• Transforming and filtering data in n8n with Python
• Calculating totals and basic statistics
• Extracting and validating text with regular expressions

Build Node.js, Express, and TypeScript APIs with consistent structure. Separate request handling, business logic, and database access, while following guidance for input validation, error tracking, configuration, and tests when adding features or refactoring existing services.

• Adding an API endpoint
• Separating business logic from database access
• Standardizing input validation and error handling

Add URL handlers to a TypeScript server built with Node's native HTTP module. The skill follows an existing switch/case router, connects named asynchronous handlers, and covers JSON responses, error handling, and optional shared request body parsing.

• Adding an API endpoint to a native Node HTTP server
• Connecting a route file to an existing switch/case router
• Sharing JSON request body parsing across routes

Use Quicknode to connect applications to blockchains, retrieve wallet and asset data, and monitor activity. Covers event notifications, live data streams, historical backfills, and SQL queries, with guidance for choosing suitable services and access methods.

• Connecting an app to blockchain data
• Setting up transaction and event notifications
• Recovering missing historical stream data

Build token swap features that move assets between blockchains using the NEAR Intents 1Click API. The skill guides React and Node.js integrations through quotes, deposit transactions, and status checks, with instructions for six blockchain ecosystems.

• Building a token swap widget in React
• Implementing cross-chain swaps in Node.js
• Adding deposit handling for different blockchains

Run repository tests using commands suited to Python, Node, or Rust projects. Detect the project setup from its files, run the full suite or a selected target, and show passing results or failure details.

• Run the full test suite before pushing changes
• Test a specific file or folder
• Use test commands suited to each project

Prepare a branch for a pull request by running local tests, checking types for Node projects, pushing commits, and showing the CI pipeline link. Failed checks stop the workflow before the push.

• Running tests before opening a pull request
• Checking Node types before pushing commits
• Getting the CI link after a push

Remote command execution and file transfer on SageMaker HyperPod cluster nodes via AWS Systems Manager (SSM). This is the primary interface for accessing HyperPod nodes — direct SSH is not available. Use when any skill, workflow, or user request needs to execute commands on cluster nodes, upload files to nodes, read/download files from nodes, run diagnostics, install packages, or perform any operation requiring shell access to HyperPod instances. Other HyperPod skills depend on this skill for all node-level operations.

The English summary is being prepared. Showing the original description.

Diagnose and remediate per-node issues on a HyperPod cluster (EKS or Slurm) — a specific node is unhealthy, unresponsive, stuck, or needs replacing. Covers on-node EFA, GPU / accelerator hardware (XID, ECC, NVLink, row-remap, DCGM), Slurm node down/drained, disk and memory pressure, per-node lifecycle-script failures, SSM agent, container runtime, kernel panics, pod networking. Read-only. Not for cluster-wide provisioning (→ hyperpod-cluster-debugger), NCCL (→ hyperpod-nccl), or MFU (→ hyperpod-mfu-debugger).

The English summary is being prepared. Showing the original description.

Diagnostic-only skill for Slurm scheduler and node-daemon issues on Amazon SageMaker HyperPod Slurm clusters. Scope mirrors the HyperPod troubleshooting guide. Invoke when the user reports a Slurm node stuck in down/drain, "Node unexpectedly rebooted" after auto-repair, slurmd not running, jobs stuck PENDING with REASON=Resources while sinfo shows idle nodes, jobs stuck COMPLETING after node replacement, GRES/GPU counts wrong, scontrol ping failing, slurmctld unresponsive, an Action:Reboot/Replace request that did not trigger HyperPod auto-recovery, or auto-resume not restarting a job. Also triggers on "drain before reboot", "diagnose a Slurm node", "investigate stuck jobs."

The English summary is being prepared. Showing the original description.

Integrate the Temps Node.js SDKs for server-side platform access, KV storage, and Blob storage. Use when the user wants to: (1) Call the Temps platform API from Node.js (deployments, projects, analytics, session replay, etc.), (2) Use Temps KV (key-value) storage, (3) Use Temps Blob storage for files, (4) Server-side integration with a Temps project, (5) Backend access to Temps resources. Triggers: "temps node sdk", "temps kv", "temps blob", "backend integration", "node.js temps", "@temps-sdk/node-sdk".

The English summary is being prepared. Showing the original description.

Build, inspect, audit, and refactor Blender Geometry Nodes systems for procedural models, instancing, modular effects, curves, scattering, flocks, data visualization, fields, simulation zones, and node-graph cleanup. Use whenever a Blender task specifically calls for Geometry Nodes, reusable procedural node graphs, node connections/layout, or a scalable procedural asset.

The English summary is being prepared. Showing the original description.

Builds full-stack web applications with AdonisJS — a batteries-included Node.js framework with ORM, auth, validation, and mailer built-in. Use when someone asks to "build a web app with Node.js", "Laravel for Node.js", "full-stack Node framework", "AdonisJS", "batteries-included backend", or "Node.js with built-in ORM and auth". Covers Lucid ORM, auth (sessions, tokens, social), VineJS validation, Edge templates, and deployment.

The English summary is being prepared. Showing the original description.

Designs Claude Code prompts and CC environments. Produces CLAUDE.md drafts, agent topologies, scope-authorization frameworks, halt triggers, Skills/hooks/MCP plans, chat-to-CC handoff specs, and EXECUTION_PLAN.md remediation plans. Five modes: DESIGN (new CC deployments), EVOLVE (updates from friction), RESEARCH (evaluate a CC tool/pattern), TEMPLATE (reusable artifacts), REMEDIATE (consume hygiene findings → produce + execute plan). Do NOT use REMEDIATE for direct cleanup (Cat 1–10 — use rootnode-repo-hygiene Phase 2). Do NOT use for hygiene scanning (rootnode-repo-hygiene), chat prompts (rootnode-prompt-validation), or chat Projects (rootnode-project-audit).

The English summary is being prepared. Showing the original description.

Firmware development for the 30-pin NodeMCU ESP8266 devkit — NodeMCU DevKit V1.0 / Amica (CP2102) and LoLin NodeMCU V3 (CH340G), built on the Ai-Thinker ESP-12E or ESP-12F module (ESP8266EX, 4 MB flash), with PlatformIO and the Arduino ESP8266 core (`board = nodemcuv2`). Use when working on a NodeMCU, ESP-12E, ESP-12F or ESP8266 devkit: project setup, platformio.ini, the D0-D10 vs GPIO numbering, which pins are safe and which break the boot, GPIO15/GPIO0/GPIO2 strapping, the A0 divider and 1 V ADC, software I2C and software PWM, analogWrite range, LittleFS and flash layouts, OTA, deep sleep and the missing GPIO16-to-RST link, Wi-Fi, heap exhaustion, watchdog and Soft WDT resets, exception decoding, flashing over CP2102/CH340, or debugging why the board does not boot, prints garbage, or reboots by itself.

The English summary is being prepared. Showing the original description.

Pencil CLI（`pencil`コマンド）だけを使って既存の.penファイル（Pencilで作成されたデザインファイル）をAIプロンプトで修正・更新するスキル。ユーザーが.penファイルの編集、ボタン追加、レイアウト変更、UIデザインの調整、Pencilデザインの更新などを依頼した場合に必ずこのスキルを使用する。エージェントモード（`pencil --in --out --prompt`）で同一パスを指定して既存ファイルを上書き編集し、編集後はインタラクティブモード（`pencil interactive`）でNodeツリーから「**編集したコンポーネントのNodeだけ**」を特定して`get_screenshot` / `export_nodes` でPNG出力し、`.pen`と同階層の`snapshots/`ディレクトリに保存する。Pencil MCPには依存せず、`pencil` コマンドのみで完結する。

The English summary is being prepared. Showing the original description.