108건 · 관련도순
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`）。 外側が tmux のときに今の tmux を分割してワーカー（と dispatcher）を並べる `split-window` コマンドも出す。 特定のペインの画面を直接見たい・入りたい・並べて見たい、attach コマンドを知りたいという依頼で発動。 自分で attach / split はせず・ペインも一切変更しない（コマンド文字列とペイン一覧表を表示するのみ）。 作業委譲（org-delegate）・ダッシュボードで状況一覧（org-dashboard）・watcher 停止（org-attention-stop） には発動しない。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
개인 정보를 공개하는 사이트를 조사하고, 당사자의 동의를 받아 삭제 신청과 결과 확인을 진행합니다. 진행 기록과 재게시 정기 점검도 관리합니다.
Set up Pact tests that record what a frontend expects from an API and verify those expectations against the backend. Review these contract tests to catch incompatible changes and help services be tested and deployed independently.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build chat, image generation, and speech transcription features on 0G Compute Network, a distributed GPU marketplace. This skill guides SDK integration, model fine-tuning, response processing for billing, and account funding through code patterns and CLI commands.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Screen incoming investment opportunities against a fund’s criteria using company sale memoranda, short deal summaries, or broker materials. Extract financials and risks, assess fit, and produce a one-page memo with a recommendation and first-call questions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn broker trade exports into a report on holding periods, trading frequency, win rate, and realized profit or loss. Diagnose patterns such as holding losers longer, overtrading, chasing rising prices, and fixation on particular price levels, with numerical evidence.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Research stock and cryptocurrency strategies through historical testing, factor analysis, and options pricing. Analyze trading journals, extract rules from profitable trades, and generate reports comparing simulated results with actual trading outcomes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use shared organization credentials to call search services, paid APIs, or Git remotes through a broker, an intermediary that adds authentication without revealing the secret. Requests stay within the configured hosts, paths, and permitted operations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Help a spawned worker check which date-range helpers and external integrations are available and how to call them. The catalog explains environment settings, local broker access, and availability checks so the worker can choose tools for its task.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.