「broker」の検索結果

Use this skill when the user asks the difference between a freight broker, freight forwarder, and motor carrier (49 CFR 371 + 373) — required authority for each, bond requirements (BMC-84 broker bond, BMC-85 freight forwarder bond), broker-carrier agreements, factoring + commissions, double brokering, and how to identify each role on a Bill of Lading. Cite 49 CFR 371 + 373.

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

CRE Brokerage Investment Sales v1 - 8 specialist skills for U.S. seller-side commercial investment sales brokers, covering assignment intake, broker opinion of value, listing proposal, OM and teaser drafting, buyer process management, bid leveling, negotiation support, and PSA-to-close coordination.

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

Drafts SEC/FINRA-compliant Broker-Dealer Customer Agreements covering account opening, trading, margin, fees, risk disclosures, privacy, arbitration, and execution. Use when drafting or updating customer account agreements, brokerage agreements, or customer documentation for registered broker-dealers.

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

組織の生きているペイン（secretary / dispatcher / worker）へ tmux で**直接入る** ための **コマンドを出力するだけ** の read-only スキル。`mcp__org-broker__list_panes`（論理ペイン） と `/usr/bin/tmux -L claude-org-broker list-panes -a`（pane_id ↔ session マッピング）を pane_id（%N）で突き合わせ、各ペインに role + name(task_id) ラベル付きの attach コマンドを 生成する（読取専用 `-r` / 書込は `-r` 無し / デタッチは `Ctrl-b d`）。 「ワーカーのペインを見たい」「ワーカーのペインに入りたい」「dispatcher の様子を直接見たい」 「ペインに入りたい」「あのペインを直接覗きたい」「attach コマンド教えて」 「tmux でつなぎたい」「worker の画面に入る」等で発動。 自分で attach はせず・ペインも一切変更しない（コマンド文字列とペイン一覧表を表示するのみ）。 作業委譲（org-delegate）・ダッシュボードで状況一覧（org-dashboard）・watcher 停止（org-attention-stop） には発動しない。

PR の CI / マージ監視 (tools/pr-watch.sh) を broker tmux セッション内の専用ペイン pr-watch-<PR> で回す。窓口が PR 作成直後に `/pr-watch-pane <PR>` で起動すると、 ja-root cwd・sandbox 外で監視が走り、/clear や窓口セッション寿命と無関係に継続する。 pane name で冪等起動 (二重監視しない)、role=watcher で identity 登録、監視終了 (CI green / PR merged / timeout) で broker の tmux backend ならペイン自動 close (herdr / wezterm / renga のペインは tmux ペインでないため自動 close されず、窓口が 監視終端でイベント駆動 close する)。Bash tool の background は session 寿命依存で長時間 watcher には不適なので本 skill が推奨経路。 「CI 監視をペインで」「pr-watch をペインで回して」「PR <N> の CI を見張って」等で発動。

Brokered short-lived provider credentials client in matrx-frontend (`lib/api/broker/`). Use when browser code needs a provider realtime session, a direct provider call, an ephemeral token, or a provider API key in the browser or `NEXT_PUBLIC_*`. NOT for adding a new audience server-side (use aidream's token-broker).

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

Audit whether an enforced-coordination MCP has actually shrunk its ~19 legacy etiquette verbs into the 5 enforced tools — work/act/ask/recall/status — each carrying one denial shape and one transcript event, migrated through a real retirement path (intake-metadata, alias, or doc-history — never a parallel runtime), with zero legacy-verb calls once a body reaches compliance mode C4+. Use when reviewing a broker-collapse migration plan, gating a body's move from advisory (C0-C3) to enforced (C4+) coordination, or verifying IT-018 Broker Collapse compliance. NOT for the inbound trigger→spawn boundary that decides whether an event may spawn an agent at all (use fleet-event-spawn-trust), the capability-token cryptographic mechanism behind a denial (use agentic-zero-trust-security), designing how a swarm of agents invokes and shards work (use swarm-invocation-designer), or auditing an individual PR's mergeability (use agent-pr-authoring).

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

Search and chat with AI agents across the Universal Agentic Registry via the Hashgraph Online Registry Broker API. Use when discovering agents, starting conversations, finding incoming messages, or registering new agents.

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

Internal — for Boundless team members only. Cross-reference Boundless indexer API data, broker telemetry, and service logs to investigate production and staging operational issues. Use when the user wants to understand why slashings happened on prod/staging, diagnose prover or service failures in deployed environments, correlate market events with broker behavior, investigate fulfillment rate drops, look at prover/service logs, or perform any analysis that requires combining on-chain indexer data with off-chain broker telemetry and CloudWatch logs. Also use when the user asks to "investigate", "diagnose", or "find root cause" for prover, service, or market issues on live networks. Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.

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

Use when the user asks about initial access brokers (IABs), the access-listing market, ransomware-feeding-IAB pipelines, specific broker handles, or how access is priced and packaged. Self-updating knowledge cell.

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

Use when a task needs the judgment of a brokerage clerk — resolving a trade-break/reconciliation exception before settlement, recomputing a weighted-average execution price across partial fills, processing a corporate action's effect on share count and cost basis, or responding to a DK (don't-know) notice from a contra broker.

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

Use this skill when the user asks the economic + operational tradeoffs of broker-mediated freight vs direct shipper relationships — margin difference, capital + operational cost, sales effort, payment terms, relationship investment, when to pursue direct, and the hybrid model. Reference industry research on freight broker margins.

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

Autonomously remove your info from data-broker sites.

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

0G Compute Network guide for decentralized AI inference, fine-tuning, and GPU services. Covers chatbots, image generation, speech-to-text, SDK integration (0g-serving-broker), processResponse API, broker.inference methods, CLI commands (0g-compute-cli), and account management. Use this skill for any 0G compute, 0G AI, or decentralized GPU question.

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

Hunt fintech-specific GraphQL vulnerabilities: money-movement mutations (transfers, redemptions, withdrawals, card top-ups), ledger/balance/portfolio query IDOR, decimal-precision and rounding abuse, idempotency-key bypass enabling double-spend, KYC/PII field-level authorization gaps, and admin-override mutations reachable via mass assignment. Distinct from hunt-graphql, which owns generic GraphQL discovery and IDOR/mutation methodology — this skill owns the delta introduced when a GraphQL layer sits in front of a ledger, wallet, payments, banking, brokerage, or lending backend, where a resolver bug moves real money instead of just leaking data. Use when hunting a fintech, banking, payments, wallet, neobank, brokerage, or lending target that exposes a GraphQL API, or when a schema/response includes balance, transfer, ledger, redeem, quote, KYC, or account-linking fields.

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

Use when asked 出口报关需要什么单证, 报关资料清单, 申报要素怎么填, 报关单和发票对不上, 出口退税需要的单证, 进口清关资料, or prepare customs documents for an export or import shipment in mainland China. Produces a document checklist for this shipment (报关单 data, 商业发票, 装箱单, 合同, 委托书, licences and certificates), a cross-document consistency check, the 申报要素 to prepare for the HS code, inspection and licence flags, the timeline with the customs broker, and the records to keep for the export rebate, all marked to confirm with the broker and customs.

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

Get option chain data from Interactive Brokers for equities, ETFs, and futures (FOP), including calls and puts with strikes, bids, asks, volume, implied volatility, and model Greeks. Use when user asks about options using IBKR data, futures options (NQ/ES/CL/GC...), or needs real-time option quotes from their broker. Requires TWS or IB Gateway running locally.

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

Texas Data Privacy and Security Act (TDPSA) compliance. No revenue threshold applies to all businesses. Covers data broker registration requirements, biometric identifier provisions under CUBI, consumer rights, AG enforcement, and 30-day cure period. Effective July 1, 2024.

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

Start and interact with the Boundless localnet (docker compose-based local development network). Covers dev mode (fake proofs, broker included) and full proving mode, submitting requests, and debugging order flow. Use when the user wants to start localnet, run the local network, test proof requests locally, or debug broker/order-stream issues.

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

Internal — for Boundless team members only. Query Boundless broker telemetry tables on Redshift for prod/staging operational data. Use when the user asks about broker health, request evaluations, request completions, proving times, skip rates, telemetry data, or wants to run SQL against the telemetry database on live networks. Also covers historical telemetry through 2026-04-24 stored as Parquet archives in S3 (queried via DuckDB). Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.

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

Implement consumer-driven contract testing with Pact-JS (v16). Covers consumer test writing, broker-driven provider verification, Pact Broker setup, can-i-deploy as a deployment gate, webhook-triggered verification, pending pacts, and schema-first vs consumer-first approaches (OpenAPI/Ajv, Schemathesis). Use when: "contract test," "Pact," "consumer-driven," "API contract," "provider verification," "can-i-deploy." Not for: stubbing or mocking a dependency to isolate a test — use service-virtualization; general REST/GraphQL endpoint assertions against your own API — use api-testing. Related: api-testing, service-virtualization, ci-cd-integration, test-environments.

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

保险经纪人 / 保险代理人 (中国保险经纪人/代理人 (从业者视角)) Master OS — automated mastery of 中国保险经纪人/代理人 (从业者视角): top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 中国保险经纪人/代理人 (从业者视角) problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「保险经纪人」「保险代理人」「保单方案设计」「保险经纪 master」「中国保险 broker」

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

Generate freight documents (Bill of Lading, Rate Confirmation) and check carrier/broker compliance via FMCSA. Track insurance expiries and authority status. Use when a broker needs to generate a BOL or Rate Con, wants to verify carrier compliance, needs to check upcoming document expiries, or when booking a load. Triggered by phrases like "generate BOL", "generate rate con", "compliance check MC#", "upcoming expiries", or "document for load".

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

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'.

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