'broker' 검색 결과

Performs contract-driven compliance review of insurance certificates and endorsements against CRE/site-access and vendor agreement requirements. Produces pass/fail/conditional determinations, deficit lists, and broker-ready remediation instructions. Use when reviewing COI packets, ACORD 25 forms, or endorsements for additional insured, primary and non-contributory, waiver of subrogation, completed operations, umbrella alignment, limits adequacy, or insurer rating compliance. Trigger terms: COI, ACORD, additional insured, certificate holder, cancellation notice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reviews CRE insurance certificates (ACORD 25) and endorsements against Access Agreement insurance requirements, producing a pass/fail compliance determination with broker-ready deficiency instructions. Verifies coverage limits, Additional Insured status, primary/non-contributory language, waiver of subrogation, umbrella alignment, and carrier qualifications. Use when reviewing COIs, ACORD forms, vendor or contractor insurance, site access insurance, or Additional Insured endorsements in commercial real estate transactions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Store credentials once, then inject them into outbound agent requests at runtime so agents can call services without receiving raw secrets.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnoses Kafka consumer group lag using the Kafka AdminClient API and JMX metrics exposed via the Confluent Metrics API. Identifies slow consumers, topic partition hotspots, and broker rebalance storms that contribute to lag growth. Provides a step-by-step runbook to tune fetch.min.bytes, max.poll.records, and partition count.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when Codex must make a high-quality judgment on any complex problem, not only technical problems. Trigger when a question has high complexity, uncertainty, cost of being wrong, long-term impact, value tradeoffs, possible structural causes, or when the user asks for 全面思考, 深度理解, 系统性分析, 帮我想清楚, 从根上看, 这件事到底怎么看, 方法论, 复杂问题拆解, 系统方案, 架构判断, 策略判断, or 根因分析. Also trigger for project and engineering high-risk scenarios such as multi-module, multi-environment, multi-data-source, multi-state, financial truth, live trading, ledger, revenue, customer assets, order governance, broker interfaces, online availability, major solution selection, and system closure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

JUnit 5, Mockito, AssertJ, and Testcontainers patterns for any JVM project. Covers test structure, parameterised tests, mocking discipline, fluent assertions, and integration testing with real containers. Stack-agnostic — referenced by every Java plugin in the marketplace. Use this skill to: - Write clear, maintainable unit tests with JUnit 5. - Mock dependencies with Mockito without overusing mocks. - Write expressive assertions with AssertJ. - Spin up real infrastructure (DBs, message brokers) with Testcontainers for integration tests. Do NOT use this skill for: - Spring-specific test slices (@SpringBootTest, @WebMvcTest, @DataJpaTest — those are in spring-boot-plugin skills). - Framework-specific mocking utilities (MockMvc, WebTestClient).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Interact with your Public.com brokerage account using the Public.com API. Able to view portfolio, get stock quotes, place trades, and get account updates. To create a Public.com account head to public.com/signup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Conduct a structured cross-project code review between two Claude Code instances via the cross-review-mcp broker. Each agent reads its own codebase, reviews the peer's code, and engages in evidence-backed dialogue — with QSG scaling laws enforcing review quality through minimum bandwidth constraints and phase-gated progression.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Built by DynG AI for PlatformPilot.ai-style Go agent runtimes. Use when the user wants to scaffold HandoffKit runtime primitives into a Go project: channel-backed mailboxes, select, router, broker, join/quorum barriers, trace, budget, corpus/compactor, supervisor/nursery, dead letters, and sketch interfaces. Trigger words include PlatformPilot scaffold, scaffold handoffkit, add the HandoffKit runtime, set up message-passing agents, or drop in CSP agent primitives.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deploy cloud access security brokers — shadow IT discovery, SaaS governance, and cloud data protection.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Client reporting, quality assurance, and financial operations management. Handles KPI frameworks, compliance audits, budget tracking, and launch checklists. Use when: managing client dashboards, ensuring brand compliance, conducting QA reviews, tracking marketing spend, ensuring GDPR/CAN-SPAM compliance, handling a request to delete someone's data across the marketing stack, deciding whether an AI voice or AI presenter has to be disclosed, proofreading deliverables. Also triggers on: client reporting, QA, quality assurance, brand compliance, marketing budget, financial tracking, legal compliance, GDPR, CAN-SPAM, proofreading, launch checklist, right to erasure, right to be forgotten, data deletion request, DSAR, someone asked us to delete their data, do we delete or suppress, suppression list, they unsubscribed and we emailed them again, we deleted them and they came back, restored a backup and re-emailed people, custom audience still has deleted contacts, California Delete Act, DROP, data broker deletion, enrichment records disappearing

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when running background tasks with Celery - worker and broker configuration (Redis, RabbitMQ), task routing by name vs queue, chains/groups/chords, retry patterns (autoretry_for, retry_backoff), acks_late semantics, failure detection, and monitoring with Flower

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when configuring Financial Services Cloud (FSC) financial accounts — including account types, FinancialHolding positions, FinancialGoal records, FinancialAccountRole assignments (Primary Owner, Joint Owner, Beneficiary), and household balance rollup behavior. Triggers: configure financial accounts in FSC, set up financial account roles Financial Services Cloud, FSC household balance rollup not working, add holdings to financial account, FinancialAccountType picklist setup, FSC brokerage or retirement account configuration. NOT for household group setup and rollup scheduling — use admin/household-model-configuration. NOT for the FinServ object graph and SOQL — use data/fsc-data-model.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AI โบรกเกอร์สินเชื่อบ้าน — เปรียบเทียบธนาคาร, ต่อรองดอกเบี้ย, ยื่นกู้, รีไฟแนนซ์, วิเคราะห์ต้นทุนแท้จริง

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Professional finance research toolkit — backtesting (11 engines + benchmark comparison panel), factor analysis, Alpha Zoo (478 pre-built alphas across qlib158/alpha101/gtja191/academic/fundamental), options pricing, 90 finance skills, 30 multi-agent swarm teams, Trade Journal analyzer, and Shadow Account (extract → backtest → render) across 29 market-data sources (tushare, yfinance, okx, binance, akshare, baostock, tencent, mootdx, ccxt, futu, mt5, tickerall, local, eastmoney, sina, stooq, yahoo, pykrx, india_broker, qveris, longbridge, nobitex, wallex, plus optional-key finnhub/alphavantage/tiingo/fmp/gildata).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when building data pipelines, ETL jobs, event processors, message-broker producers/consumers, application caching layers, database migrations, BigQuery queries, or event-sourcing handlers in TypeScript. Triggers on edits to indexer/ETL/migration code, Prisma or Drizzle schemas, BigQuery integration code, RabbitMQ/Kafka/SQS/BullMQ producer or consumer code, Redis cache wrappers, or mentions of "data engineering", "ETL", "pipeline", "indexer", "event sourcing", "data warehouse", "data migration", "message queue", "RabbitMQ", "Kafka", "SQS", "BullMQ", "Redis cache", or "caching".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Professional network graph analyst identifying Gladwellian superconnectors, mavens, and influence brokers using betweenness centrality, structural holes theory, and multi-source network reconstruction. Activate on 'superconnectors', 'network analysis', 'who knows who', 'professional network', 'influence mapping', 'betweenness centrality'. NOT for surveillance, discrimination, stalking, privacy violation, or speculation without data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design Kafka consumer groups that survive rebalances, hit the right delivery guarantee (at-most/at-least/exactly-once), and handle poison messages without stalling the topic. Use when picking a partition assignment strategy (Range vs Sticky vs Cooperative-Sticky vs the new KIP-848 protocol), tuning heartbeat / session / max.poll.interval timeouts, choosing manual vs auto offset commits, designing dead-letter or retry topics, or migrating from Classic to the next-gen Consumer protocol. NOT for Kafka cluster ops (broker tuning, partition reassignment), schema design (Avro/Protobuf/Schema Registry), or stream processing topology (use a kafka-streams skill).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

CQRS pattern, event stores, projections, eventual consistency. Activate on: CQRS, event sourcing, event store, read model, projection, aggregate, domain event, command handler. NOT for: message broker setup (use event-driven-architecture-expert), database optimization (use data-warehouse-optimizer).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cross-session Claude Code instance messaging via claude-peers-mcp broker

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detects early-stage ransomware indicators in network traffic before encryption begins, including initial access broker activity, command-and-control beaconing, credential harvesting, reconnaissance scanning, and staging behavior. Uses network detection tools (Zeek, Suricata, Arkime), SIEM correlation rules, and threat intelligence feeds to identify ransomware precursor patterns such as Cobalt Strike beacons, Mimikatz network signatures, and RDP brute-force attempts. Activates for requests involving pre-ransomware detection, network-based ransomware indicators, or early warning ransomware monitoring.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with Apache Pinot — apache Pinot management — monitor cluster health, tables, segments, ingestion jobs, query performance, and controller/broker/server status. Use when debugging ingestion issues, inspecting segment distribution, optimizing query latency, or auditing cluster capacity.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when working with Activemq — activeMQ broker health, destination management, advisory topic monitoring, network connector status, and message flow analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build and operate a Busabase-backed mainland China A-share strategy experiment desk with a bundled local Hono App-in-Skill, evidence-backed strategy research, strategy-level L1/L2/L3 manual maturity approvals, one CNY virtual ledger per strategy, and dated strategy backtest reports. Use when the user invokes $kelly-invest-stock or /kelly-invest-stock, wants to define or compare A-share strategies, inspect a strategy and its virtual book, record research evidence, manually approve strategy maturity, or review dated backtests, drawdown, and contribution to the total book. It never connects to a brokerage, places orders, moves money, or presents generated analysis as personalized investment advice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.