搜索
搜索结果
80 results for "workers"
workers-best-practices
审查并编写符合生产最佳实践的 Cloudflare Workers 代码。在编写新的 Worker、审查 Worker 代码、配置 wrangler.jsonc 或检查常见的 Worker 反模式（流处理、未处理的 Promise、全局状态、密钥、绑定、可观测性）时加载。倾向于从 Cloudflare 文档检索，而非依赖预训练知识。
cloudflare
notion
Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls.
openclawcoding-agent
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
openclaw
notion
用于页面、Markdown 内容、数据源、文件、评论、搜索、Workers 和原始 API 调用的 Notion CLI/API。
steipetecoding-agent
将编码工作委托给 Codex、Claude Code 或 OpenCode 作为后台工作进程；不用于简单编辑或只读代码查询。
steipete
browser-extension-reverse
Use for authorized reverse engineering of browser extensions (Chrome/Firefox) including manifest analysis, background workers, and extension-based credential or traffic logic recovery.
zhaoxuya520
entra-agent-user
在 Microsoft Entra ID 中从代理标识创建代理用户，使 AI 代理能够作为数字工作者在 Microsoft 365 和 Azure 环境中使用用户身份功能。
github
supermemory
Supermemory is a state-of-the-art memory and context infrastructure for AI agents. Use this skill when building applications that need persistent memory, user personalization, long-term context retention, or semantic search across knowledge bases. It provides Memory API for learned user context, User Profiles for static/dynamic facts, and RAG for semantic search. Perfect for chatbots, assistants, and knowledge-intensive applications.
supermemoryai
iii-core-primitives
Use when registering iii functions, binding triggers, selecting sync/void/enqueue invocation, creating workers, inspecting the live worker registry, installing registry workers, authoring custom triggers, moving channel data, or adapting external HTTP functions across TypeScript, Python, and Rust.
iii-hqiii-error-handling
Handle iii engine and SDK errors across Node, Python, Rust, and browser workers. Use when interpreting error codes, retryability, RBAC denial, timeouts, handler failures, or SDK-specific exception surfaces.
iii-hqiii-engine-config
Configures the iii engine via iii-config.yaml — workers, adapters, queue configs, ports, and environment variables. Use when deploying, tuning, or customizing the engine.
iii-hq
vue-expert
使用组合式 API 模式构建 Vue 3 组件，配置 Nuxt 3 SSR/SSG 项目，设置 Pinia 存储，搭建 Quasar/Capacitor 移动应用，实现 PWA 功能，并优化 Vite 构建。适用于创建 Vue 3 组合式 API 应用、编写可复用的组合函数、使用 Pinia 管理状态、使用 Quasar 或 Capacitor 构建混合移动应用、配置 Service Worker，或调整 Vite 配置和 TypeScript 集成。
jeffallanrails-expert
Rails 7+ 专家，精通通过 includes/eager_load 优化 Active Record 查询、使用 Turbo Frames 和 Turbo Streams 实现页面局部刷新、配置 Action Cable 处理 WebSocket 实时连接、搭建 Sidekiq worker 处理后台异步任务，以及编写全方位的 RSpec 测试套件。适用于构建基于 Hotwire、包含实时功能或后台任务处理的 Rails 7+ Web 应用程序。涉及 Active Record 性能优化、Turbo Frames/Streams、Action Cable、Sidekiq、RSpec Rails 等场景时调用。
jeffallanjavascript-pro
使用现代 ES2023+ 特性、async/await 模式、ESM 模块系统和 Node.js API 编写、调试和重构 JavaScript 代码。适用于构建纯 JavaScript 应用程序、实现基于 Promise 的异步流程、优化浏览器或 Node.js 性能、使用 Web Workers 或 Fetch API，以及审查 .js/.mjs/.cjs 文件的正确性和最佳实践。
jeffallanlaravel-specialist
构建和配置 Laravel 10+ 应用程序，包括创建 Eloquent 模型和关系、实现 Sanctum 认证、配置 Horizon 队列、使用 API 资源设计 RESTful API，以及使用 Livewire 构建响应式界面。在创建 Laravel 模型、设置队列工作者、实现 Sanctum 认证流程、构建 Livewire 组件、优化 Eloquent 查询或为 Laravel 功能编写 Pest/PHPUnit 测试时使用。
jeffallanmigrate-to-vinext
将 Next.js 项目迁移到 vinext（基于 Vite 的 Next.js 重新实现）。当被要求从 Next.js 迁移、转换或切换到 vinext 时加载。处理兼容性扫描、包替换、Vite 配置生成、ESM 转换和部署设置（Cloudflare Workers 原生支持，其他平台通过 Nitro）。
cloudflare
semgrep
使用并行子代理对代码库运行 Semgrep 静态分析扫描。支持两种扫描模式——“全部运行”（完整规则集覆盖）和“仅重要项”（高置信度安全漏洞）。自动检测并在可用时使用 Semgrep Pro 进行跨文件污点分析。当被要求扫描代码漏洞、使用 Semgrep 进行安全审计、查找错误或执行静态分析时使用。为多语言代码库生成并行工作进程。
trailofbits
n8n-self-hosting
Deploy a production self-hosted n8n end-to-end to a fresh Linux VM over SSH, using Docker Compose behind a Caddy reverse proxy with automatic HTTPS. Use whenever the user wants to self-host, install, set up, provision, or deploy n8n on their own server/VPS/box (Hetzner, DigitalOcean, AWS EC2, bare metal, etc.) — in either single/regular mode or queue mode with workers — or to update, back up, restore, or harden such an instance. This is for SELF-HOSTED n8n (Docker), not n8n Cloud and not building workflows. The skill makes the agent ask single-vs-queue first, collect the domain/SSH/timezone inputs, generate fresh secrets on the box, and bring the stack up with TLS. Trigger on "deploy n8n", "self-host n8n", "install n8n on my server", "n8n docker compose", "n8n queue mode / workers / scaling", "n8n reverse proxy / SSL", "back up / update my n8n", or "we don't want to give every user the OAuth client secret" / "enable the Sign in with Google button" (credential overwrites).
czlonkowski
dynamo-troubleshoot
Diagnose failed or unhealthy Dynamo deployments. Use when pods, model-cache jobs, PVCs, workers, frontend/router health, endpoints, or benchmark jobs fail; use recipe-runner/router-starter before this for normal bring-up.
nvidiak2
Build and troubleshoot Cloudflare K2 or K2 Streams durable logs. Use for stream setup, producing from Workers or HTTP, configuring retention and inputs, and consuming through subscriptions.
cloudflarebasin
Build and troubleshoot Cloudflare Basin analytics workflows with Basin Pipelines, Basin Catalog, and Basin SQL. Use for streaming data into R2 Iceberg tables, managing catalogs, or querying those tables; also use for requests using the former Data Platform, Pipelines, R2 Data Catalog, or R2 SQL names.
cloudflaresandbox-stable
Use when building or changing Cloudflare Sandbox apps on the current stable @cloudflare/sandbox package (default npm tag)—commands, sessions, files, ports, tunnels, terminals, bridge, production, or deprecated-API cleanup while staying on stable. Not for @cloudflare/sandbox@next (use sandbox-next) or for porting to 1.0 (use sandbox-migrate-to-next).
cloudflaresandbox-next
Use when building or changing Cloudflare Sandbox apps on @cloudflare/sandbox@next (Sandbox SDK 1.0 preview)—code execution, AI runners, interpreters, CI-like jobs, terminals, files, mounts, tunnels, preview URLs, lifecycle, or errors. Not for the default stable package (use sandbox-stable) or for porting stable to @next (use sandbox-migrate-to-next).
cloudflaresandbox-migrate-to-next
Use when porting a Cloudflare Sandbox app from stable @cloudflare/sandbox to @cloudflare/sandbox@next (Sandbox SDK 1.0 preview), or when the user asks to migrate or upgrade to Sandbox 1.0 / @next. Not for day-to-day stable work (sandbox-stable) or new @next apps (sandbox-next).
cloudflare