「boundary」の検索結果

Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.

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

Perform STRIDE threat modeling for each component and trust boundary and produce a threat register. Use when reviewing a feature for security.

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

This skill integrates **Boxxy sandbox boundary testing** with the complete Trail of Bits firmware extraction methodology. Use this for extracting and analyzing firmware in heavily obfuscated, containerized, or restricted environments.

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

Runs structured Python cleanup and modernization — static analysis via prek/ruff, smell investigation to root cause, typed-boundary hardening by inventorying Any usage, and modernization within the project's requires-python lane. Use when refactoring Python code, removing dead code, hardening type boundaries, or running a modernization pass on a file or scope.

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

Reviews Python code across type safety, error handling, security, performance, modern patterns, design clarity, typed-boundary compliance, test quality, and documentation. Use when performing code review, PR review, pre-merge quality checks, or assessing Python for security vulnerabilities, bare except clauses, Any usage outside boundaries, or missing input validation at system boundaries.

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

Runs deterministic Python quality checks against a path or scope — formatting, linting, type checking, and typing-boundary policy. Use when checking or fixing code quality via prek, ruff, ty, pytest, or the check-typing-boundaries policy script. Reports results grouped by category; fixes only when explicitly requested.

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

Shared Python 3.11+ development rules — type safety and the boundary policy for `Any` (ty, native generics, Protocol, TypeIs, Pydantic), layered architecture and SOLID, error handling, security, performance, identifier naming, PEP 723 script dependencies, Rich/Typer output, tooling defaults (uv, ruff, ty, hatchling, pytest), and testing requirements (behavioral coverage, TDD). Activates when any Python skill or agent needs the shared rules for implementation, code review, refactoring, or test authoring.

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

Verify that changed components are actually connected into the intended end-to-end system flow. Use when checking imports/exports, registrations, data/control flow, configuration consumption, call paths, and boundary compatibility after implementation.

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

Design validation and maintained regression protection before test authoring. Use for TDD increments, acceptance or regression evidence, test boundary/oracle decisions, and multi-factor interaction coverage.

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

Review test effectiveness against authoritative contracts, relevant fault detection, refactor tolerance, boundary fidelity, isolation, and diagnostic value. Use when auditing test quality, reviewing coverage gaps, improving regression protection, or assessing tests after a change.

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

Agent invocation syntax and boundary rules

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

Generate adversarial inputs, edge cases, and boundary test payloads for stress-testing LLM robustness

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

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.

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

当用户在投资（或重大决策）场景中，对某个标的/方向产生兴趣但说不清"我到底懂不懂它"，或列举了一堆正面理由却无法回答"未来5-10年它会怎样"时，激活此 skill。关键触发信号：用户用行业经验替代商业判断、用研究时长衡量理解深度、或以"看起来便宜"作为买入理由。不适用于：纯信息查询、已有明确投资框架的用户寻求优化、日常小额消费决策。核心区别：能力圈≠熟悉的行业，而是"能判断未来现金流折现的范围"；安全边际=理解度而非价格折扣。

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

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for prompt-injection, retrieval poisoning, memory contamination, planner drift, MCP or tool-boundary abuse, and agent exfiltration challenges. Use when the user asks to analyze prompt injection, retrieval poisoning, memory contamination, planner drift, tool-argument corruption, or secret exposure caused by an agent chain. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

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

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for kernel attack surface, namespace and cgroup boundaries, container isolation assumptions, syscall paths, and escape primitive verification. Use when the user asks to analyze container-to-host escape paths, kernel exploit prerequisites, namespace crossover, capability misuse, or prove whether an exploit primitive crosses the sandbox boundary. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

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

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for crypto, encoding, steganography, APK, IPA, and mobile trust-boundary challenges. Use when the user asks to decode a blob, recover a transform chain or key, inspect hidden media payloads, hook an APK or IPA signer, inspect app storage, or replay mobile request-signing logic. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

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

Design the Soundcraft Ui24R adapter boundary for AI-Controlled Party: dry-run, Bitfocus Companion, direct Node bridge, connection health, config, failure handling, and live-validation gates. Use whenever a task mentions Soundcraft, Ui24R, snapshots, cues, Companion, soundcraft-ui-connection, mixer bridge, or revising the adapter design.

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

Quality-assure integrated tdmcp features: run the four PR gates + recipe/bridge tests, cross-boundary coherence checks (tool schema↔CLI↔docs↔registry, operator↔createable, bridge↔client), and live TouchDesigner validation (preview + post-cook error check) when the bridge is reachable. Use when validating/QA-ing/testing tdmcp tools, checking a feature actually cooks in TD, verifying CLI matches a tool, or gating a release.

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

Windows local privilege escalation from a low-privilege shell to Administrator or SYSTEM. Covers quiet vs loud enumeration, SeImpersonate/Potato family including LocalPotato, token privileges (SeBackup/SeRestore/SeManageVolume/SeLoadDriver/SeDebug), service/DLL/COM/scheduled-task abuse, AlwaysInstallElevated and UAC boundary, KrbRelayUp-style domain-joined local admin, and version-gated kernel LPE. Use when the operator already has a Windows foothold and needs local SYSTEM. Endpoint blocks hand off to /edr-bypass then return here.

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

Cloud control-plane reconnaissance for AWS, Azure/Entra, GCP, and Alibaba Cloud: identity, IAM/RAM, trust, resources, metadata, and managed-Kubernetes cloud-side boundary. Recon only — no policy changes, no privilege escalation. Operator may select /cloud-attack or /k8s.

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

Discover, message, and coordinate AI coding agents (Claude Code, Codex CLI) running on the same machine via a shared Unix socket broker backed by SQLite. The broker wakes recipients natively (Claude inbox socket, codex queue) and turn-boundary hooks catch missed wakes. Supports cross-session task delegation, peer summaries, and session lifecycle management. Triggers on 'peer agents', 'cross-session communication', 'message Codex', 'inter-agent messaging', 'coordinate agents'.

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

Validate RuField CSI or ultrasonic recording replay and its fusion boundary. Use for captured CSI JSONL, BatVu ultrasonic replay, replay adapter integration, or replay regression diagnosis.

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

Validate and scientifically interpret completed research runs, including negative, null, boundary, confounded, failed, and inconclusive outcomes. Use after execution to assess evidence and claim impact; not to edit methods or schedule experiments.

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