Expert-level computer networks covering OSI model, TCP/IP stack, routing protocols, transport layer, application protocols, network security, and software-defined networking.
日本語の概要は準備中です。原文の説明を表示しています。
1,216 件 ・ 関連度順
概要と使いどころ
Expert-level computer networks covering OSI model, TCP/IP stack, routing protocols, transport layer, application protocols, network security, and software-defined networking.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level hydraulics covering open channel flow, pipe systems, hydraulic structures, pumps and turbines, flood routing, and stormwater management.
日本語の概要は準備中です。原文の説明を表示しています。
Establish or audit a structural quality contract for any agent-operated engineering repository: app, library, CLI/tool, plugin, harness, or meta repo. Use when a repo needs charter clarity, docs/decision ownership, type-native validation gates, evidence paths, safe action policy, cold-start legibility, maturity proof, repair-loop routing, consumer/producer owner-boundary routing, command surface evolution, evolutionary simplicity (see references/evolutionary-simplicity.md), or a repo ecology pass to decide what should be compressed, merged, removed, updated, created, retired, or moved to checks.
日本語の概要は準備中です。原文の説明を表示しています。
新しいプロジェクトまたは既存リポジトリに Claude 用の kickoff 文脈を導入するスキル。 テンプレートとリポジトリ証跡、ユーザー入力をもとに `CLAUDE.md`、`docs/PROJECT_BRIEF.md`、 `docs/SKILL_ROUTING.md`、`docs/QUALITY_GATES.md`、`docs/TEST_STRATEGY.md`、 `docs/DECISION_LOG.md`、`docs/HIDDEN_CONTRACT_REGISTER.md`、 `docs/CROSS_MODULE_CONSISTENCY_MATRIX.md`、`.claude/rules/*`、 `.claude/commands/project-kickoff.md` を必要に応じて作成・更新する。 Use when starting a new project, retrofitting AI project context into an existing repository, bootstrapping Claude memory, or standardizing kickoff documents, rules, and slash-command scaffolding. Distinct from project-manager / project-plan-creator (which plan work), and from completion-quality-gate-designer / hidden-contract-investigator / safe-by-default-architect / cross-module-consistency-auditor / production-parity-test-designer (which deeply refine individual artifacts after bootstrap).
Wählt vor komplexer Multi-Agent-Arbeit gemeinsam mit dem Nutzer eine passende, begrenzte Orchestrierung und erzeugt einen kompakten Session-Vertrag. Nutze den Skill bei /choose-your-orchestrator, bei unsicherer Kombination aus Orchestrator, Schwarm, Modellrouting oder Nutzerpräferenzmodell sowie vor Agentenprogrammen, die Modellslots, Parallelität, Spawn-Tiefe, Schreibgrenzen, Abnahme und Eskalation ausdrücklich festlegen müssen.
日本語の概要は準備中です。原文の説明を表示しています。
Route planning from A to B via OSRM (Open Source Routing Machine). Supports car, bicycle and pedestrian. No API key required.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts the instructions field of a declarative agent that orchestrates a set of custom skills, under a character cap (default 8,000), from the skills' names and descriptions: role and scope, one routing rule per skill, workflow order, gates written as workflow holds, global rules, output format and what the agent never does. Returns the text in a fenced block with its character count labelled counted or estimated, plus a skill inventory, routing table, gate table, rules trace and open questions for the owner. Use when the user asks to "write the instructions for my agent", "draft a system prompt that ties these skills together", "tighten these agent instructions to fit the cap", "how should the agent route between these skills" or "revise my agent's orchestration text". Do not use to review a single SKILL.md, use skill-file-reviewer instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Azure Iot Hub — azure IoT Hub management including device registry, device twins, message routing, endpoints, jobs, and IoT Edge deployments. Covers device connectivity status, message throughput, routing health, quota utilization, and Edge module monitoring.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Ambassador — ambassador (Emissary-Ingress) API gateway management covering mappings, hosts, TLS contexts, authentication filters, rate limiting, and Envoy proxy configuration. Use when managing Ambassador/Emissary-Ingress routing, configuring API gateway mappings, debugging routing issues, setting up TLS termination, or analyzing gateway performance.
日本語の概要は準備中です。原文の説明を表示しています。
Expert en API gateway v2 (Kong, Traefik, rate limiting, auth, routing, observabilité)
日本語の概要は準備中です。原文の説明を表示しています。
Busabase-backed App-in-Skill dashboard for a shared LLM gateway's cost and model governance — daily spend trend, cost breakdown by service/model, a canary-rollout status board, and a deterministic cost/error anomaly list. Use when the user invokes $kelly-llm-gateway or /kelly-llm-gateway, or wants to review LLM gateway spend, model routing, canary rollouts, rollback readiness, or cost/error anomalies for services routed through one shared gateway to multiple LLM providers/models. Human actions (promote/rollback/hold a rollout, acknowledge an anomaly) write directly onto the route's own Busabase record — this skill never changes a real routing config.
日本語の概要は準備中です。原文の説明を表示しています。
Generates standard operating procedures for B2B SaaS marketing operations: campaign naming conventions, UTM governance, tool administration, workflow QA, data hygiene, lead routing, and incident response playbooks. Use when setting up or auditing marketing ops processes, onboarding a new marketing ops hire, standardizing campaign tracking, fixing broken lead routing, cleaning up HubSpot or CRM data, building QA checklists for campaign launches, or creating incident response procedures for marketing system failures. Also use when asked to "fix our UTM mess," "standardize campaign naming," "build a QA checklist," "audit our marketing ops," or "create an ops runbook." Designed for B2B SaaS marketing teams running HubSpot with multi-geo, multi-segment operations.
日本語の概要は準備中です。原文の説明を表示しています。
Train Mixture of Experts (MoE) models using DeepSpeed or HuggingFace. Use when training large-scale models with limited compute (5× cost reduction vs dense models), implementing sparse architectures like Mixtral 8x7B or DeepSeek-V3, or scaling model capacity without proportional compute increase. Covers MoE architectures, routing mechanisms, load balancing, expert parallelism, and inference optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Cross-chain interoperability for Stellar. Entry point with a rail-selection decision table and shared pitfalls, routing to two companion files — cctp.md (Circle CCTP V2, native USDC burn-and-mint between Stellar and EVM/Solana chains, domain 27, the CctpForwarder requirement for Stellar recipients) and axelar.md (Axelar GMP for Soroban contracts calling contracts on other chains, and the Interchain Token Service for multichain tokens). Also covers NEAR Intents (intent-based cross-chain swaps into XLM or Stellar USDC) at the routing level. Use when bridging USDC to or from Stellar, sending messages between a Stellar contract and another blockchain, making a token exist on multiple chains, or adding cross-chain swaps to an app.
日本語の概要は準備中です。原文の説明を表示しています。
TanStack Router (型安全 React ルーター、@tanstack/react-router) の API リファレンス。 React Router (react-router) とは別ライブラリ。 createRouter, createFileRoute, createRootRoute, createLazyFileRoute, Link, Outlet, useNavigate, useParams, useSearch, useLoaderData, useBlocker, loader, beforeLoad, validateSearch, redirect, notFound, Await, file-based routing, routeTree.gen.ts, router-plugin, tsr CLI, code splitting, SSR, TanStack Query 統合, eslint-plugin-router。
Hono (軽量・マルチランタイム対応 Web フレームワーク) リファレンス。 Hono App, Context (c.req / c.json / c.text / c.html), HonoRequest, Routing, HTTPException、 Built-in Middleware (JWT, CORS, CSRF, Cache, Logger, Compress, Basic / Bearer Auth)、 Helpers (Cookie, Streaming, WebSocket, Factory, RPC)、 Cloudflare Workers / Deno / Bun / Node.js / AWS Lambda 対応。
React Router v8 (Framework Mode、旧 Remix) の RR8 リファレンス。 loader, action, middleware, routes.ts、hooks (useLoaderData, useActionData, useFetcher, useNavigate, useNavigation, useParams, useSearchParams)、 コンポーネント (Form, Link, NavLink, Outlet, Route, Routes, Await)、SSR / SPA / Static、 ErrorBoundary, redirect, defer, session, matchPath, matchRoutes, type-safe routing。 TanStack Router (@tanstack/react-router) とは別ライブラリ。
Echo (LabStack) — Go Web framework リファレンス。routing(Group)、echo.Context、 Bind、Validator、HTTPError、HTTPErrorHandler、middleware(JWT, CORS, CSRF, BasicAuth, Gzip, Recover, Logger, RateLimiter)、Renderer、WebSocket、SSE、 AutoTLS 実装例。
Claude API (platform.claude.com) のプロンプトエンジニアリング・評価リファレンス。 prompt engineering, XML タグ, few-shot, system prompts, モデル別プロンプティング(Fable 5 / Opus 5 / Sonnet 5)。 evals, grading(LLM-graded 等), jailbreak・prompt leak 対策, hallucination 低減, classification, ticket routing 等ユースケース実装。
Token-slim mode — cut this session's token usage by routing every file read, code search, directory listing, and JSON dump through the token-slim MCP server (or its binary directly). Works in any repository or folder; the server itself is LLM-agnostic (any MCP client). Use when the user types /slim, or asks to save/reduce tokens, "トークン節約", "トークン削減", "コンテキスト節約", "token slim".
新規条項の誕生ゲート(5 宛先の routing 判定 → 常駐集合の予算処理 → 台帳記録)。規範文書に条項を追加・移動・削除するときに実行する
Plan which model tier handles which work BEFORE execution begins — a high-cognition model deeply understands the problem, lays the foundations, then emits a modular plan assigning each module the cheapest tier that can safely execute it, with escalation tripwires and one-way-door protection. Advisory only: it announces "next module → tier X / model Y" at each boundary and the HUMAN switches models — harnesses like Cursor cannot switch mid-run. Load when the user asks which model to use, wants a model plan, model tiers, model-tier routing, assign models to tasks or modules, says "cheap model got stuck", "which model for this task", "cost-efficient model choice", or when implementation-plan / problem-to-plan need a model: tier column. NOT dynamic-routing (plan-path selection after failure) — this skill assigns cognition tiers to work.
日本語の概要は準備中です。原文の説明を表示しています。
Lists all inference providers offered during NemoClaw onboarding. Use when explaining which providers are available, what the onboard wizard presents, or how inference routing works. Trigger keywords - nemoclaw inference options, nemoclaw onboarding providers, nemoclaw inference routing, switch nemoclaw inference model, change inference runtime, nemoclaw local inference, ollama nemoclaw, vllm nemoclaw, local model server, openai compatible endpoint.
日本語の概要は準備中です。原文の説明を表示しています。
Pick the right writing voice for a task — which voice playbook applies, nk-writer invocation, brand-writer invocation, /mxm-voice-route. Lookup wrapper over the operator's voice selection authority.
日本語の概要は準備中です。原文の説明を表示しています。