「eal」の検索結果

GitHub 解封 — 账号封禁/限制/恢复的领域操作系统。覆盖：(a) GitHub 官方政策体系 (TOS / 可接受使用政策 / Trust & Safety 执行模式 / 公开申诉路径 / 受制裁地区解读)；(b) 封号原因诊断学 (spam / abuse / 制裁误标 / 2FA 丢失 / ToS 违规 / 账号劫持误判 / ban evasion 等子类型 + 症状→原因映射 + 自我分诊压测)；(c) 申诉实操 craft (写一封能让 T&S 快速判误伤的英文申诉信 + 升级阶梯 + 法务介入边界 + Don'ts)；(d) 制裁与合规硬边界 (OFAC SDN 名单 / 哪些国家或地区真不可达 / VPN 误判路径 / 中国大陆不是美国制裁地区的反复重申)；(e) 中国大陆开发者特别处境 (sanctioned region 误标 + SMS 验证不支持 +86/+852 + Gitee/GitLab/Codeberg/JihuLab 备用迁移 + 私有自托管 Gitea/Forgejo)；(f) 真实案例库 (~30+ 公开案例分类拆解：误伤 / 真违规 / 制裁误标三类各自赔率与申诉成功路径)。伦理锚绝不软化：不教 ban evasion / 不教撒谎式申诉 / 真违规承认改进 / 丢 2FA 无恢复因子则诚实告知 / 中国制裁误标靠申诉不靠换 VPN / 申诉 6 个月窗口必算清 / 约 3% (业内估) 真违规恢复 vs 约 79% (业内估) 误伤申诉成功率分层标。 (GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: false-positive / genuine violation / sanctions mis-flag, each with win-rate and appeal success path). Ethical anchors absolutely not softened: do NOT teach ban evasion (creating new accounts turns a temp ban into a permanent one — the single biggest mistake); do NOT teach social engineering or lying in appeals (misuse + actually confirms violation); genuine violations: admit + improve beats denial; lost 2FA + no recovery factor → do not pretend recovery is possible; China sanctioned-region mis-flag → fix via appeal, not repeated VPN switching; appeal form 6-month window must be counted carefully; historical 约 3% (业内估) genuine-violation recovery vs 约 79% (业内估) false-positive appeal success rate stratification must be honestly labeled. Anti-samples (explicitly describe harm, never endorse): developer permabanned for ban evasion / open-source team org-banned for personal attacks in public issues / cases where repeated VPN switching escalated risk-control severity.) Master OS — automated mastery of GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: fa

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

投行并购 (投行并购 / 交易撮合 (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

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

Expert SurrealDB 3 architect and developer skill (tracks v3.1.4+). SurrealQL mastery, multi-model data modeling (document, graph, vector, time-series, geospatial), schema design, security, deployment, performance tuning, SDK integration (JS, Python, Go, Rust, Java, .NET, C, PHP, Swift, Kotlin, Ruby), Surrealism WASM extensions, SurrealML scope coverage (preview), built-in MCP (v3.1+) and standalone SurrealMCP, LangChain Python integration, editor tooling (LSP v0.1.6, tree-sitter, CodeMirror v1.0.6, VS Code/JetBrains/Neovim/Zed), and ecosystem integrations (Surrealist v3.9, Surreal-Sync, SurrealFS, SurrealKit v0.7, n8n, Agent Skills, setup-surreal). Universal skill for 30+ AI agents.

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

Expert SurrealDB 3 architect and developer skill (tracks v3.1.4+). SurrealQL mastery, multi-model data modeling (document, graph, vector, time-series, geospatial), schema design, security, deployment, performance tuning, SDK integration (JS, Python, Go, Rust, Java, .NET, C, PHP, Swift, Kotlin, Ruby), Surrealism WASM extensions, SurrealML scope coverage (preview), built-in MCP (v3.1+) and standalone SurrealMCP, LangChain Python integration, editor tooling (LSP v0.1.6, tree-sitter, CodeMirror v1.0.6, VS Code/JetBrains/Neovim/Zed), and ecosystem integrations (Surrealist v3.9, Surreal-Sync, SurrealFS, SurrealKit v0.7, n8n, Agent Skills, setup-surreal). Universal skill for 30+ AI agents.

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

Expert SurrealDB 3 skill. Use when working with SurrealDB, SurrealQL queries, multi-model data modeling (document, graph, vector, time-series, geospatial), schema design, graph traversal, vector search, security and permissions, deployment and operations, performance tuning, SDK integration, Surrealism WASM extensions, SurrealMCP, Surrealist IDE, Surreal-Sync migrations, SurrealFS, SurrealKit, or ecosystem integrations such as n8n and CodeMirror.

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

Unreal Engineのエディターを操作し、物体の配置、照明や素材の調整、カメラ設定を進めます。シーンの状態と見た目を確認し、画像やレンダーを出力するスキル。

• 3Dレベルの構築と配置
• 雰囲気に合う照明に調整したいとき
• カメラの構図設定とレンダー出力

CodeScene MCPでコード構造の保守しやすさを評価するスキル。編集前後のスコアを比較し、コミットやPRの前にAIによる変更で品質が下がっていないか確認します。

• 見慣れないファイルを編集前に確認したいとき
• AIの変更で保守性が下がっていないか確認
• スコアを比較しながらコードを整理したいとき

Draws original spot illustrations of one hero object as SVG cards (480x360) in a teal-on-white style. Identifying traits are a single object in a fixed oblique 3/4 view showing top, front and right faces; white main faces with teal only on side faces and accents; thin dark-teal outlines on every edge; a hard, unblurred deep-teal drop shadow pushed down-right; and two to four small floating extras (coins, tilted UI cards, badges) with their own hard shadows, plus 4-point sparkles. No people. Covers design and coding concepts as objects: keyboards, databases, git graphs, inboxes, devices. Use when someone asks for a teal spot, teal icon illustration, isometric spot object, 3D line spot, empty-state art, onboarding step art, a 404 or error spot, a feature spot, a blog header object, a marketing card or a product icon scene in teal, mint or green-teal.

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

Deal desk: reviews, approves, and structures non-standard sales deals. Use when standing up a deal desk, building approval-threshold matrices, designing deal-review packets, routing deals, or auditing deals for compliance.

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

Governs employee health data processing for fitness-for-work assessments, occupational health surveillance, COVID testing legacy programmes, and absence management. Applies Art. 9(2)(b) employment obligations and Art. 9(2)(h) health professional exceptions. Covers data minimisation, occupational health provider relationships, and return-to-work procedures. Keywords: health data, Art. 9, occupational health, fitness-for-work, special category, employment, sickness absence.

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

SurrealDB MCP for AI agents: built-in server (SurrealDB 3.1+ `surreal mcp`) and standalone surrealmcp (surrealdb/surrealmcp v0.4.0). Part of the surreal-skills collection.

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

Build a customer health scorecard across usage, engagement, adoption, NPS, support load, and financial risk. Use when user says "health score", "customer health", "build a scorecard", "how healthy is this account", "customer scoring model", "green yellow red", "health dashboard", or "account health framework" - even if they don't say "scorecard" explicitly. Applies to CSMs building account health models or CS leaders standardizing health tracking across the team.

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

Track multiple live deals with milestones, deadlines, action items, and status updates. Maintains a deal pipeline view and surfaces upcoming deadlines and overdue items. Use when managing a book of business, tracking process milestones, or preparing for weekly deal reviews. Triggers on "deal tracker", "deal status", "where are we on", "process update", "deal pipeline", or "weekly deal review".

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

Amazon deal planning and promotional strategy optimization. Lightning Deals, Best Deals, Coupons, Prime Exclusive Discounts analysis and ROI calculation. Deal eligibility assessment, timing optimization, and promotional campaign planning. Use when the user asks about Amazon deals, Lightning Deals, promotional planning, deal strategy, or Amazon promotions.

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

Addresses HIPAA compliance for mobile health (mHealth) applications, wearable devices, and remote patient monitoring. Covers OCR guidance on mobile device PHI, FDA-regulated mobile medical applications, FTC Health Breach Notification Rule for non-HIPAA apps, BYOD policies, and encryption requirements for ePHI on mobile platforms. Keywords: mHealth, mobile health, HIPAA mobile, wearable, remote monitoring, BYOD, mobile device management, app privacy.

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

SurrealDB MCP for AI agents: built-in server (SurrealDB 3.1+ `surreal mcp`) and standalone surrealmcp (surrealdb/surrealmcp v0.4.0). Part of the surreal-skills collection.

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

Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a customer referral program (who may accept the reward, how the introduction is made), designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for an early-stage startup where the founder is still doing the selling — running founder-led sales, setting up a design-partner program, judging whether you have product-market fit, deciding what not to do yet, deciding when to hire the first AE or first marketer, and moving upmarket to larger buyers. Also use it when your company has just acquired another (or is about to), to plan the marketing integration: what you may and may not do between signing and close, the first letter to the acquired customers, whether to keep, endorse, fold in or retire the acquired brand, merging the two marketing databases without mailing people who opted out, when to start cross-selling, and announcing a product sunset. Also use it to design a demand-generation campaign and the channel plan it runs on: one campaign with one job, the offer for buyers who are and are not in market, what each channel is for, the kill and scale rules set before launch, the follow-up sales agrees to, the yearly calendar of always-on programs and tentpole campaigns, and which channels to keep, test or stop. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: founder-led sales, founder-led GTM, design partners, design partner agreement, first customers, first 10 customers, do we have product-market fit, PMF, Sean Ellis test, very disappointed survey, pre-seed, seed stage, when to hire our first AE, first sales hire, first marketing hire, moving upmarket, going upmarket, enterprise readiness, first enterprise deal, what do enterprise buyers need before they sign, positioning, product launch, beta program, early access program, design partners, private preview, public preview, general availability, GA launch, when can we call it GA, can sales sell a beta feature, selling the roadmap, launch tier, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, ideal customer profile, ICP, what is our real ICP, who actually buys from us, refresh our ICP from closed-won deals, ICP refresh before planning, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget. Also triggers on public-sector marketing: sell to government, government marketing, public sector go-to-market, federal marketing, state and local government, SLED, FedRAMP, FedRAMP marketing claims, can we say FedRAMP ready, GovRAMP, StateRAMP, VPAT, accessibility confor

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

Produces structured U.S. appellate document summaries mapping procedural posture, issues on appeal, standards of review, and competing arguments into memo-ready format. Use when summarizing appellate briefs, notices of appeal, records on appeal, or preparing for oral argument. Triggers: appeal, appellate, notice of appeal, standard of review, cross-appeal, appellate brief intake, record on appeal synthesis.

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

Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).

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

Implement several variations of a design directly inside the running app, on the real page/route, with a live switcher to toggle between them in the browser, then recommend one and fold the winner into the real code. Variants are real implementations judged against real data, layout, and density (not an isolated mockup). Use this skill whenever the user wants to try design options live in the app, prototype changes directly on a real page, add a variant switcher, compare layouts in-context, asks to "build a few versions of this page", "try variants on the real screen", "switch between designs in the app", "implement this with a toggle", or says "real-prototype this". For a safe standalone .html copy that never touches the app, use the prototype skill instead.

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

医療アプリの患者・職員の機密情報を分類し、施設単位のアクセス制御や監査記録を設計するとともに、ログ・URL・ブラウザー保存からの情報漏えいを点検するスキル。

• 患者記録を扱うコードの点検
• 医療施設間のアクセス制御の設計
• 機密情報の閲覧・変更の監査記録

Stage-by-stage pipeline health check - coverage, aging, conversion, and at-risk deals - from CRM opportunity data. Use when the user asks "review my pipeline", "pipeline health", "where's my pipeline stuck", "weekly pipeline review", "which deals should I focus on this week", "any stale or stuck deals", "which deals have past close dates", "which deals are single-threaded", or "check my pipeline coverage against my number".

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

Use when reviewing a specific inbound deal before close — when sales has asked for a discount that exceeds AE authority, when the customer has redlined the MSA, when per-deal economics (margin after discount, multi-year payment shape, indemnity exposure) need to be quantified, or when discount approval needs to be routed to a named human approver (Sales Director, VP Sales, CFO, CRO, General Counsel). Covers deal review, discount approval routing, per-deal margin scoring, deal exception handling, MSA redline triage, contract landmine detection (uncapped indemnity, MFN, perpetual license-back, missing DPA), and named-approver chain assembly. NEVER auto-approves — every output is a numeric scorecard plus a routing recommendation to a named human.

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

Use when designing or revising a company's commercial policy — the rules of engagement governing discounts off list price, approver thresholds, exception flows, and the deal framework that Deal Desk and AEs operate under. Covers discount matrix design (ARR band x term length x payment terms x strategic value), commercial policy design, exception policy, discount governance, approval thresholds, deal framework structure, and policy linting (contradictions, gaps, cliff edges, gaming surfaces). For Head of Commercial, Head of Deal Desk, VP Sales, or RevOps at the policy-design moment — NOT per-deal application (that is deal-desk) and NOT pricing model selection (that is pricing-strategist).

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