'advisory' 검색 결과

Drive ONE already selected open pull request in microsoft/apm to mergeable. Classifies copilot-pull-request-reviewer[bot] inline review, runs autopilot-pr-review-worker, folds (by default) every recommendation inside the PR's stated scope, pushes to the head branch or a superseding PR that preserves authorship via commit trailers, watches CI to green (`agent-merge` when that skill or `<agent_merge_state>` is present; otherwise `gh pr checks --watch`), and iterates under fixed caps until ready-to-merge, advisory-with-deferred, superseded, or blocked. Plan before any fold, push, or reviewer request. Never spawned by autopilot-pr-review-scheduler. That scheduler is advisory only. Invoke this skill by name when the caller asked to drive a PR to merge.

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

[omh] Security event on the code already shipped -- a CVE in a dependency, a secret committed to the repo, a license question, an advisory: triage reachability and severity, contain in order, and never close a leaked secret before its rotation is observed. Use when the user says: security-event-response, security event response, cve, triage this cve, cve in our dependency, cve in a dependency, security advisory, dependabot alert.

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

Recommend a data-portal architecture (storage, compute, catalog, access, hosting, metadata) from stated needs, then hand off to the build skills. The advisory entry point. Use when starting a new data-portal project and the underlying architecture has not yet been decided.

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

End-to-end methodology for reproducing AND patching publicly disclosed, already-fixed vulnerabilities: sourcing the advisory and the fix commit, reading the patch diff, rebuilding a pinned offline lab, building a vulnerable-vs-patched contrast harness with proper controls, minimizing the trigger, designing and validating the fix, and writing it up as a blog post or whitepaper. Use this skill whenever the user wants to reproduce, demonstrate, understand, teach, or write about a known vulnerability or security incident: "reproduce this CVE", "build a repro for", "how did EchoLeak / Log4Shell / the postmark-mcp package actually work", "show me how this exploit worked", "write a blog post about this vulnerability", "set up a lab for CVE-XXXX", "pull the NVD/CVE/OSV details", or "make a PoC I can publish". Use it just as eagerly for the patching half: "how should this be fixed", "is this patch correct", "what would have caught this", "review this security fix", "write a regression test for this CVE", "how do I backport this", or "what's the right fix for this bug class" - even when the user never says the word "reproduce". Reach for it on vague asks like "help me understand this security advisory", "I want to write about this incident", or "can we test whether we were vulnerable" when a disclosed vulnerability is in play. This skill only handles ALREADY-PATCHED, publicly disclosed issues and refuses zero-day discovery, live targets, and weaponization.

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

Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026). Use this skill whenever a user asks about SWIFT CSP, CSCF controls, SWIFT security attestation, KYC-SA portal, SWIFT architecture types (A1/A2/A3/A4/B), mandatory vs advisory controls, independent assessment, SWIFT secure zone, secure flow zone, MFA for operators, SWIFT messaging security, payment fraud prevention on SWIFT, gap analysis for CSCF, or compliance with SWIFT's 32 controls (26 mandatory, 6 advisory in v2026) across the three objectives: Secure Your Environment, Know and Limit Access, Detect and Respond. Control 2.4 (Back-Office Data Flow Security) is now mandatory in v2026. v2026 attestation window is July 1– December 31, 2026. Trigger for any SWIFT CSP or CSCF compliance question.

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

Structured C-suite onboarding via a founder interview that captures company context into a persistent file used by all advisory skills. Use when setting up advisory context, refreshing stale context, or onboarding a new executive.

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

Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026). Use this skill whenever a user asks about SWIFT CSP, CSCF controls, SWIFT security attestation, KYC-SA portal, SWIFT architecture types (A1/A2/A3/A4/B), mandatory vs advisory controls, independent assessment, SWIFT secure zone, secure flow zone, MFA for operators, SWIFT messaging security, payment fraud prevention on SWIFT, gap analysis for CSCF, or compliance with SWIFT's 32 controls (25 mandatory, 7 advisory in v2026) across the three objectives: Secure Your Environment, Know and Limit Access, Detect and Respond. Control 2.4 (Back-Office Data Flow Security) is now mandatory in v2026. v2026 attestation window is July 1– December 31, 2026. Trigger for any SWIFT CSP or CSCF compliance question.

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

Guides compliance with Singapore's Personal Data Protection Act 2012 (PDPA). Covers PDPC advisory guidelines, Do Not Call Registry, data intermediary obligations, deemed consent, notification requirements, and the 2020-2021 amendments. Keywords: Singapore PDPA, PDPC, Do Not Call Registry, deemed consent, data intermediary, advisory guidelines.

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

End-to-end substantive-integrity forensic sweep of a research paper (especially autoresearch / AI-Scientist-style output). Orchestrates the whole pipeline: ingest (arxiv-id | pdf | dir → working dir + pdftotext for L0) → /evidence-ledger (artifact manifest + observability level L0/L1/L2 + span-anchored claims.json) → fan out the integrity auditor skills (consistency, citation, baseline, experiment, presentation, proof-derivation, eval-design — each reads the ledger, emits span-anchored findings) + the zero-verdict-weight AIS writing-style track → advisory memos (/adversarial-case-builder + /novelty-duplication-advisory, no verdict weight) → deterministic tools/adjudicate_findings.py (--ledger REQUIRED) → reviewer-ready Integrity Forensics Report. Cross-model (fresh codex per dimension) and reviewer≠adjudicator: the model proposes findings, the deterministic adjudicator decides the verdict. Observability-aware, detect-only, never an opaque AI-text classifier (a separate zero-weight AIS section lists AI writing-style impressions, never moving the verdict). Triggers: "anti-autoresearch", "integrity audit this paper", "forensic review", "audit a submission", "审一篇投稿的诚信".

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

投行并购 (投行并购 / 交易撮合 (Investment Banking M&A / Dealmaking) — 面向并购顾问、企业融资、卖方/买方交易执行的职业认知操作系统，从业者(分析师 Analyst / 经理 Associate / 副总裁 VP / 董事 Director / 董事总经理 MD / 内部公司发展 Corp Dev / PE 投资人)、想入行者、以及服务这行(法律/会计/估值/咨询)的视角。覆盖: (a) 第一性张力 — 投行 M&A 的核心世界观分歧: **价格 vs 价值 (price 是市场愿意付的, value 是内在的, deal 在两者缝隙里成交) ⇄ 确定性 vs 最高价 (certainty of close 对卖方常胜过纸面最高报价) ⇄ 顾问/中介 vs 委托代理 (banker 是 agent, 客户利益 vs 成交费的激励冲突真实存在, 「banker 总想成交」是行业原罪批判)**; 更深层 — 「过程/竞价纪律 (controlled auction 制造竞争张力、信息不对称管理) ⇄ 关系/信任 (relationship banking、长期 coverage、reputational capital)」, 「叙事/包装 (the story, equity story, positioning) ⇄ 数字/尽调 (the numbers, diligence, quality of earnings)」, 「估值的科学外衣 (DCF/comps 的伪精确) ⇄ 谈判的真实定价 (价格由 leverage、竞争、时机决定)」; (b) 估值与分析正典 (最标准化、最易蒸出高质量+CLI 化) — DCF (折现现金流: FCF 预测/WACC 折现率/terminal value 终值/Gordon growth vs exit multiple), Comparable Companies (可比公司/trading comps: EV/EBITDA, EV/Revenue, P/E), Precedent Transactions (先例交易/deal comps: control premium 控制权溢价), LBO (杠杆收购模型: IRR/MOIC/debt schedule/sources & uses), Accretion/Dilution (增厚/摊薄分析: EPS 影响、pro forma), Sum-of-the-Parts (分部估值/SOTP), Football Field (估值区间图), Merger Model (合并模型: synergies 协同/purchase accounting/goodwill), Sensitivity/scenario; (c) 交易流程与产出物 — 卖方流程 (sell-side: teaser 简介 → NDA → CIM/IM 信息备忘录 → management presentation → IOI 意向函 → data room 数据室 → LOI/term sheet → confirmatory diligence → SPA 买卖协议 → signing → closing), 买方流程 (buy-side: thesis/sourcing → outreach → valuation → bid → exclusivity → diligence → financing → close), auction 类型 (broad/targeted/negotiated/preemptive bid); 产出物: pitchbook 推介材料、CIM、fairness opinion 公平意见、board presentation、fee letter、engagement letter; (d) 交易结构与条款 — consideration (cash/stock/mix/earnout 对赌)、deal protections (breakup fee 分手费/go-shop/no-shop/MAC 重大不利变化条款)、representations & warranties 陈述与保证、escrow 托管、working capital adjustment 营运资金调整、reverse termination fee、collar 价格区间、tender offer vs merger、hostile vs friendly、defensive tactics (poison pill 毒丸/white knight 白衣骑士/staggered board); (e) 行业结构与角色 — bulge bracket (高盛/摩根士丹利/JPM/BofA/花旗) vs elite boutique (Centerview/Evercore/Moelis/Lazard/PJT/Perella) vs middle market (Houlihan Lokey/William Blair/Harris Williams) vs regional/independent; analyst→associate→VP→director→MD 晋升金字塔; coverage (行业组) vs product (M&A/ECM/DCM/leveraged finance/restructuring); sponsors group (服务 PE); 买方包括 PE/strategic acquirer/corp dev; (f) 量化指标与节奏 — deal fee (success fee 业内通常约 1-2% 视规模递减/retainer/Lehman formula)、league table 排行榜、pitch→mandate 转化、deal velocity、hours culture (analyst 80-100h/week 文化批判)、bonus/comp 结构、deal sheet (简历上的成交清单); (g) 争议/批判 — fairness opinion 是否橡皮图章 (利益冲突: 出意见的 banker 也收成交费)、estimate 的伪精确 (DCF garbage in garbage out、假设驱动结论)、banker 永远建议成交 (deal 偏见、empire building 助推 CEO 自利并购)、协同效应系统性高估 (大量并购毁灭价值、winner's curse 赢家诅咒)、analyst 血汗工厂文化 (2021 高盛 13 人 deck 事件、过劳死争议)、advisory 价值 vs 中介寻租之争、bulge vs boutique 的利益独立性叙事 (boutique 标榜「无承销利益冲突」)、SPAC 泡沫与 de-SPAC 教训; (h) 流派/思想谱系 — 估值学派 (Aswath Damodaran 估值教父/纽大、Tim Koller McKinsey《Valuation》、McKinsey valuation 体系) vs 公司金融教科书派 (Rosenbaum & Pearl《Investment Banking》行业圣经、Brealey Myers Allen、CFI/WSP/BIWS 培训体系) vs 交易实战派 (Bruce Wasserstein《Big Deal》、Joseph Perella/Felix Rohatyn 老派 dealmaker、现代 boutique 创始人) vs 行为/批判派 (并购毁灭价值的学术证据、Damodaran 对协同/控制权溢价的批判、Matt Levine《Money Stuff》解构华尔街逻辑) vs PE/buy-side 视角 (LBO 数学、value creation 杠杆/运营/multiple expansion)。不含: 二级市场股票交易/卖方研究 (equity research)、零售财富管理/private banking、纯 ECM/IPO 承销执行 (虽相关但聚焦 M&A advisory)、纯 PE 投后运营、量化交易/对冲基金策略、纯公司财务报表会计。) Master OS — automated mastery of 投行并购 / 交易撮合 (Investment Banking M&A / Dealmaking) — 面向并购顾问、企业融资、卖方/买方交易执行的职业认知操作系统，从业者(分析师 Analyst / 经理 Associate / 副总裁 VP / 董事 Director / 董事总经理 MD / 内部公司发展 Corp Dev / PE 投资人)、想入行者、以及服务这行(法律/会计/估值/咨询)的视角。覆盖: (a) 第一性张力 — 投行 M&A 的核心世界观分歧: **价格 vs 价值 (price 是市场愿意付的, value 是内在的, deal 在两者缝隙里成交) ⇄ 确定性 vs 最高价 (certainty of close 对卖方常胜过纸面最高报价) ⇄ 顾问/中介 vs 委托代理 (banker 是 agent, 客户利益 vs 成交费的激励冲突真实存在, 「banker 总想成交」是行业原罪批判)**; 更深层 — 「过程/竞价纪律 (controlled auction 制造竞争张力、信息不对称管理) ⇄ 关系/信任 (rela

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

Advisory wrap for tool results from untrusted external surfaces. Appends `[QUARANTINE-NOTICE]` to next-turn context after `mcp__*`, `WebFetch`, and `Read` of `**/uploads/**` so prior tool output is treated as data — not directives. Use when the session ingests MCP user-content (Zendesk, Intercom, support tickets), fetched HTML, or operator-uploaded files. Hook fires AFTER ingestion — advisory, not structural.

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

Structures IAC/LPAC design with composition, authority scope, conflict review protocols, and valuation oversight. Use when designing advisory committees, defining LPAC authority, or structuring conflict resolution processes.

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

Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use when building a new collection with a defined scope and budget, assessing an existing collection for gaps or outdated materials, when shelves are overcrowded and systematic weeding is needed, or when establishing a formal collection development policy.

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

Run bounded, read-only semantic advisory sidecar passes for candidate mapping, issue triage, upstream diffs, evidence verification triage, and meta audit hints. Enforces monthly spend limits with explicit fallback to worker-luna.

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

Run the Advisory Council — a multi-perspective market analysis that spawns 5 AI advisors (The Skeptic, The Macro Bull, The Risk Manager, The Technical Analyst, The Contrarian) powered by MiniMax M2...

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

Cycle-end retrospective converting recurring judgment failures into durable enforcement. Reviews the cycle's friction — repeated user corrections, guard trips, RCA themes, integrate failures — and turns each recurring one into a landmines.md entry, then proposes graduation candidates up the enforcement funnel (landmine → advisory hook → hard gate). Pairs with standup: standup says what shipped and what's next; retrospective says what kept going wrong and how to stop it structurally. Writes only memory entries and a report — graduation proposals are advisory and require the normal seed.md amendment path to become enforcement. Invoke at the end of a release cycle, an epic, or any stretch of work with repeated friction.

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

Answer whether a specific advisory reaches anything in THIS repository — which manifest declares the package, at what version, whether the version is in range, and whether the vulnerable code is reachable. Use when someone asks "does CVE-… affect us", when triaging an advisory against a real codebase, or before spending effort on a fix.

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

Client advisory communication with fiduciary tone, compliance-friendly language, and plain-language financial education

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

Kelly Financial Services Intel: App-in-Skill daily industry intelligence cockpit for financial services, investment advisory, and family offices (Busabase App-in-Skill). Use when the user asks about financial services, investment advisory, market explainers, client memos, family office,投顾,金融服务, or family-office scenes. Prepares news/source signals, buyer-intent interpretation, approved sales actions, and channel drafts for review before any external handoff.

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

Kelly Insurance Intel: App-in-Skill daily industry intelligence cockpit for insurance and wealth advisory (Busabase App-in-Skill). Use when the user asks about insurance, wealth advisory, client risk reminders, market news, policyholder follow-up,保险, or financial-advisor sales scenes. Prepares news/source signals, buyer-intent interpretation, approved sales actions, and channel drafts for review before any external handoff.

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

Provide advisory guidance for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEMaaCS cloud workflows only, with public-doc citations and cloud-specific MCP verification plans. Use for conceptual questions such as `statfileslevel`, filter rules, URL decomposition, cache invalidation behavior, rewrite behavior, and security headers.

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

Provide advisory guidance for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEMaaCS cloud workflows only, with public-doc citations and cloud-specific MCP verification plans. Use for conceptual questions such as `statfileslevel`, filter rules, URL decomposition, cache invalidation behavior, rewrite behavior, and security headers.

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

AI에 보낼 요청의 목표와 부족한 정보를 정리하고 작업에 맞는 ECC 명령과 스킬을 제안합니다. 진단과 수정 이유를 덧붙여 바로 붙여 넣을 요청문으로 다듬습니다.

• 모호한 개발 요청 구체화
• 완료 조건과 검증 절차 추가
• 작업에 맞는 ECC 구성 선택

개발 목표에 맞는 ECC 명령 그룹을 골라 실행 순서와 중단 조건을 안내합니다. 현재 파일을 읽어 용도별 목록을 정리하며 명령은 실행하지 않습니다.

• 버그 수정에 필요한 명령 순서 확인
• MVP 개발용 명령 선택
• ECC 작업 절차를 용도별로 조회