「capability」の検索結果

Catalog and selection guide for Exasol tools, extensions, connectors, integrations, and architecture patterns. Use when the primary intent is comparison, discovery, support-status research, or architecture selection rather than executing a workflow; hand operational work to the selected dedicated skill. Covers deploy, load, explore, enrich, surface, and scale capability families, including named products with no dedicated skill of their own such as Lakehouse Turbo, the Exasol MCP Server, Governed SQL / Text-to-SQL MCP Server, Agent Control Plane, Extension Manager, Terraform and Ansible tooling, and BI, ETL, and warehouse integrations such as Databricks, SAP, Kafka, Power BI, and Tableau.

日本語の概要は準備中です。原文の説明を表示しています。

Reconstruct an evidenced indoor space from local Realsee scan exports, point clouds, CAD, and panoramas as a separately editable native Blender scene. Use for scan-to-Blender space modeling, source-based geometry/material/light refinement, and requested walkthrough or physics exports. Argus panorama-to-depth inference is a separate capability.

日本語の概要は準備中です。原文の説明を表示しています。

Create, extend, or fix Eloquent business models and their state transitions. Use when moving business rules out of controllers or Actions, or explicitly migrating a model into a DDD capability.

日本語の概要は準備中です。原文の説明を表示しています。

使用状态绑定的最小 Tool Surface、exact Action Gateway、来源可追踪的 MissionSpec 与 Verification Manifest、宿主无关 Flight Progression Engine、可选且无权威的 App Server continuation、顺序持久 Wave、一层原生 Agent、困难后强制战术指导、证据型 Capability Profile、显式 Manual Verification、不可变宿主 Evidence、恢复检查点和仅本地 Git，治理复杂 Codex 开发。用户要求飞控接管、继续、自主开发、修复或完成多步骤软件项目，需要有界并行子代理，或实现前必须建立文档工程时使用。

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing, evaluating, documenting, modernizing, reviewing, refactoring, or implementing software architecture and code-level structure, including requirements, context, architecture style selection, microservices patterns, WebAssembly/WASI/Component Model, UMA portable capabilities, runtime contracts, capability graphs, governed MCP/agent orchestration, clean code, code smells, Rust crate/library API architecture, Cargo feature/MSRV/SemVer policy, unsafe/FFI/no_std/library testing, modularity, views, NFR tactics, IAM/auth, security patterns, cost estimation, architecture-as-code fitness functions, ADR/RFC work, and engineering execution plans.

日本語の概要は準備中です。原文の説明を表示しています。

Work through which package to add for a capability, and what each option costs — maintenance, licence, bundle weight, transitive risk, and whether the platform already does it. Use when someone needs a library for a job and has not picked one yet, when weighing two candidates, or when a package looks convenient but unmaintained.

日本語の概要は準備中です。原文の説明を表示しています。

IDS/IPS detection content for a CVE — Snort/Suricata-compatible rules, YARA signatures, ProjectDiscovery Nuclei templates, traffic-filter rules. Capability-aware: skips families when the binary is not installed (no Snort = no Snort output). Use when deploying defences for a CVE without a patch, augmenting SAST with active detection, or feeding the SOC engineering pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base from NASA-STD-7009B (Standard for Models and Simulations) with implementation depth from NASA-HDBK-7009B. Use for M&S criticality and programmatics, development evidence and capability assessment, verification/validation domains, uncertainty and sensitivity, use-phase results assessment, risk-informed decision reporting, and handbook life-cycle products. Covers STD-7009B (2024-03-05) + HDBK-7009B (2026-02-03) synthesized notes only; does not replace program-specific TA direction, NPR 7150.2 software requirements detail, or full PRA methodology.

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base from DoD Architecture Framework (DoDAF) 2.02 — Volume II: Architectural Data and Models. Use for DoDAF viewpoints, DM2 meta-model, capability modeling, operational architecture, systems architecture, services architecture, data/information modeling, standards compliance, project/portfolio integration, and fit-for-purpose model selection. Does not cover DoDAF Volume I (policy/governance) or Volume III (enterprise-level guidance); also does not substitute for the live DISR or DARS registries.

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base from the DoD Systems Engineering Guidebook (OUSD R&E, February 2022). Use for the DoD SE process model — the 16 SE processes (8 technical management + 8 technical) mapped to ISO/IEC/IEEE 15288, the event-driven technical reviews and audits across the Major Capability Acquisition life cycle (ASR, SRR, SFR, PDR, CDR, SVR/FCA, PRR, PCA), the Systems Engineering Plan (SEP), risk/issue/opportunity management, TPMs and leading indicators, system-of-systems and digital engineering, and the 24 design considerations (RAM, system safety, HSI, system security engineering, MOSA, supportability, etc.). Acquisition-program oriented: thin on detailed cost estimating, contracting law, and non-DoD or commercial life cycles.

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base from the FAA System Safety Handbook (Dec 30, 2000). Use for system safety as a specialty within systems engineering: the five-step safety risk management process (mandated by FAA Order 8040.4 and the AMS), the severity-by-likelihood risk matrix and acceptance bands, the Safety Order of Precedence, system-description models (5M, SHEL(L)), the hazard-analysis activities (PHL/PHA/RHA/SSHA/SHA/O&SHA/HHA), integrated system hazard analysis, the analysis techniques (FTA, FMEA/FMECA, Fault Hazard, Common Cause, Sneak Circuit, Energy Trace), closed-loop hazard tracking (Safety Action Record), and the specialty domains the handbook covers — acquisition-lifecycle safety and contracting (OSA/CSA/SSPP/ISSPP), software safety (control-capability ranking, SHCM, DO-178B), test & evaluation safety, facilities safety, commercial launch safety (AST licensing, expected casualty, MPL/DAMP), system safety training, and Operational Risk Management (ORM) with human/organizational factors. Scope limits: this is a year-2000 FAA how-to; it predates the modern FAA/ICAO Safety Management System (SMS) and Just Culture regulatory frameworks, and many cited orders, advisory circulars, and launch-licensing rules have since been restructured. It is FAA/NAS-centric, leans on MIL-STD-882C, and does not define the SE life-cycle processes themselves (use nasa-npr-7123 / dau-se-guidebook) or reproduce third-party standard text (MIL-STD-882, DO-178B, ISO/IEC/IEEE).

日本語の概要は準備中です。原文の説明を表示しています。

Reviews one SKILL.md against the format rules and returns a findings table: strict YAML front matter with exactly name and description, name equal to the folder, description as the trigger, the eight-heading skeleton, capability-neutral wording, safety boundaries. Each finding carries severity, rule identifier, location, quoted evidence and replacement text; the verdict READY, REVISE or BLOCKED is an apparent state and the owner decides. Use when the user asks to "review this SKILL.md", "check my skill file before upload", "lint this skill description", "validate the front matter of this skill" or "score this skill folder". Do not use to write an agent's instructions field, use agent-instructions-drafter instead; for injection or leakage exposures use agent-instructions-red-team; for launch tests use agent-evaluation-plan. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Discover and execute specialized skills from a curated marketplace catalog on GitHub, fetched on-demand and run ephemerally (no permanent installation). The catalog covers a broad and growing range — document generation (PDF/Word/Excel/PowerPoint), visual design, presentations, web app testing, animated GIFs, dev tooling (MCP scaffolding, frontend components), creative outputs (algorithmic art), technical documentation lookup (library/API/framework references), and more. Consult this skill whenever the user asks for a capability that could plausibly be covered by a community skill — the catalog is the source of truth, not this description.

日本語の概要は準備中です。原文の説明を表示しています。

Start, inspect, or continue a persistent SIPS self-improvement loop. Use when the user asks for /selfloop, wants the agent to iteratively improve itself, or wants a goal dedicated only to SIPS and agent capability.

日本語の概要は準備中です。原文の説明を表示しています。

Runtime release controls for deployless repositories. Use when a repo needs feature flags, kill switches, capability gates, targeted rollout, remote config, routing rules, or a provider-neutral release-control facade independent of language and provider.

日本語の概要は準備中です。原文の説明を表示しています。

Customize WP Rocket behavior from a third-party plugin / theme via filter hooks — exclude URIs / cookies / user agents / REST API namespaces from caching, configure CDN URL rewrites, extend lazy load handling, override capability requirements, hook into Action Scheduler integration. Critical guidance — rocket_cache_reject_uri takes URI patterns (regex-like), NOT full URLs; rocket_cache_reject_* filters all expect arrays. The rocket_buffer filter is the FULL HTML output filter — extremely powerful but dangerous; one fatal error in the callback breaks every cached page until WP Rocket is disabled. Use when extending WP Rocket's default rules, NOT for cache invalidation (see wp-rocket-cache-invalidation). Triggers on rocket_cache_reject_, rocket_cdn_, do_rocket_lazyload, rocket_buffer, rocket_capacity, "exclude from WP Rocket cache".

日本語の概要は準備中です。原文の説明を表示しています。

Scaffolds and reviews custom WordPress REST API endpoints registered via register_rest_route on rest_api_init — namespace and version slug, permission_callback authorization (NEVER __return_true on state-changing routes, which is the most common plugin-side vulnerability on wp.org), args schema with validate_callback / sanitize_callback / type / enum, object-level capability checks via current_user_can with object ID, responses with WP_REST_Response and WP_Error carrying an HTTP status, no raw DB rows / sensitive columns in responses, cookie auth via X-WP-Nonce, REST vs admin-ajax decision. Recommends the better-route library when the plugin grows past a few endpoints. Use when scaffolding or reviewing a REST endpoint, or migrating from admin-ajax. Triggers on register_rest_route, rest_api_init, permission_callback, WP_REST_Request, WP_REST_Response, WP_Error, X-WP-Nonce, rest_ensure_response, register_rest_field, or any file path containing /rest/ or /api/ in a WP plugin or theme.

日本語の概要は準備中です。原文の説明を表示しています。

Audits WordPress plugin or theme PHP code for the most common security mistakes — missing nonce checks, capability checks, input sanitization, output escaping, unslashing, SQL preparation, AJAX nopriv exposure, file/path traversal, and unsafe redirects. Use when reviewing pull requests, before releasing a plugin, when the user asks "is this secure", or when handling code that touches $_GET / $_POST / $_REQUEST / $_COOKIE / $_FILES / $_SERVER, admin-ajax / admin-post, REST endpoints, options, user meta, custom DB queries, or file uploads.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "pick which social channels to run", "should we be on X platform or 小红书", or "plan our organic social channel portfolio"; produces an audience/objective-first portfolio with capability/access matrix, cadence-budget reality check, declared ECHO operating profile, boundary routing, and proposed-state registry events. Not for recording canonical channel facts — use channel-registry. 社媒渠道选择/渠道组合规划/平台能力矩阵/自然社媒

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose and draft or explicitly apply paid-ad optimizations using evidence, financial constraints, experiments, and capability-gated adapters. Use for campaign optimization, budget reallocation, bid changes, pausing or archiving ads, requests to delete campaigns, search-term or negative-keyword actions, creative rotation, or improving CPA and ROAS.

日本語の概要は準備中です。原文の説明を表示しています。

Draft or explicitly apply a paid-ad campaign launch through Claude Ads capability-gated adapters. Use for campaign creation, launch plans, publishing ads, activating campaigns, uploading creative, or requests to push a campaign live.

日本語の概要は準備中です。原文の説明を表示しています。

Builds React Native and Expo apps in TypeScript — navigation with React Navigation or Expo Router, lists, forms, styling, gestures and animations with Reanimated, safe areas, accessibility and localization; networking with TanStack Query, response validation, persistence with MMKV, AsyncStorage, SQLite and secure storage; permissions, push notifications, deep links, background tasks, native modules and config plugins; performance with Hermes and the React profiler; and release with EAS Build, EAS Submit and EAS Update or bare Gradle and Xcode builds. Use when writing or changing React Native code, adding a native capability, configuring Expo, preparing a store build or an over-the-air update, or when the user asks how to do something in React Native, even if they do not name the library.

日本語の概要は準備中です。原文の説明を表示しています。

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on re...

日本語の概要は準備中です。原文の説明を表示しています。

Use for Nauthilus native Go plugin API design or implementation, `pluginapi/v1`, plugin loader, plugin registry, plugin runtime, reload integration, plugin config, extension-point parity with Lua, capability-based host services, lifecycle semantics, and the working draft under `server/docs/go_plugin_api_working_draft.md`.

日本語の概要は準備中です。原文の説明を表示しています。