「risk」の検索結果

Decode a counteroffer after you resign — what the raise, promotion promise, or title bump really signals, the statistics-informed risks of staying, and a clear-eyed decision framework. Use when asked my company countered my resignation, should I accept a counteroffer, they offered me more to stay, or decode this retention offer. Produces a component-by-component decode with 🔴🟡🟢 severity, the questions that expose which promises are real, and the stay/go decision sheet.

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

Prepare and rehearse a coming-out conversation, tuned to the specific person and the real risk — what to say, how to open, how to handle the likely reactions, and a safety-first plan if it could go badly. Use when someone says 'I want to come out to my parents/boss/friend', 'help me tell them I'm [gay/trans/bi/etc.]', 'rehearse this conversation with me', or is planning any identity disclosure. Produces an opener, a rehearsal against realistic reactions, and a safety plan. Safety and the user's autonomy come first — it never pushes anyone to come out.

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

Write a Chinese workplace weekly or monthly report (周报 / 月报) for a manager: results with numbers, progress against goals, risks raised early, next week's plan and the support needed, in the structure Chinese managers expect. Use when asked 帮我写周报, 写月报, 整理本周工作, weekly report in Chinese, or turn my notes into a 周报. Produces the report in Chinese with 本周完成, 关键数据, 问题与风险, 下周计划 and 需要的支持, plus a one-line summary for chat apps.

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

Use when asked 做一份外贸报价单, FOB 和 CIF 怎么报价, 出口报价核算, 报价怎么算利润, 退税怎么算进报价, quotation sheet for an export order, or price an export quotation from China. Produces a cost build-up from the factory price through export tax rebate, domestic logistics, port charges, freight and insurance to each Incoterms 2020 term, a quotation sheet in English with a Chinese summary, quantity tiers, validity and exchange-rate assumptions, payment terms and the risk each term puts on the seller, with rates marked to confirm.

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

Produce a structured churn analysis that separates avoidable from unavoidable churn. Use when investigating why customers are leaving, identifying at-risk segments, calculating net revenue retention, or building a retention intervention plan. Produces a churn report with rate calculations, categorised reasons by avoidability, segment breakdown, timing analysis, early warning signals, and prioritised interventions ranked by estimated impact.

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

Plan a Chinese company's entry into an overseas market (出海): choose the market with evidence, then plan entity, payments, localisation, compliance, channels and team for the first twelve months. Use when asked 出海计划, 我们要进入东南亚 / 中东 / 欧洲 / 美国市场, how should a Chinese company expand overseas, or a go-global plan. Produces a market scorecard, a twelve-month entry plan by workstream, the compliance and data checklist for the chosen market, and the top risks with mitigations. Bilingual output on request.

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

Help a student and family plan university applications after the 高考 (gaokao): use the student's provincial rank rather than raw score, build a 冲 / 稳 / 保 (reach, match, safe) list from official historical admission data, check subject requirements under the new gaokao, and weigh major against university. Use when asked 帮我填高考志愿, 志愿怎么填, 冲稳保怎么排, 这个分数能上什么学校, or plan gaokao applications. Produces a structured application list with the reasoning for each choice, a risk check of the whole list, and the questions to settle as a family. Never guarantees admission.

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

Decode a care-home contract before a parent moves in — the fee-escalation clause with no cap, the needs-can-no-longer-be-met eviction trigger, the guarantor line that quietly makes you personally liable, and the after-death charges nobody mentions on the tour. Use when asked to review a care-home or nursing-home contract, what does this admission agreement mean, can they raise the fees, or can they make my parent leave. Produces a clause-by-clause decode ranked by financial and eviction risk, the questions to put in writing before signing, and the negotiate-or-verify list. Pairs with long-term-care-options for choosing the home; this is for the contract. Not legal advice.

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

Pressure-test a business or side-hustle idea before you sink money and months into it — find the real demand, the risky assumptions, and the cheapest way to test them. Use when asked to validate my business idea, is this a good business idea, test my side hustle, or should I start this. Produces a read on the core assumptions the idea depends on, who the customer really is and whether the pain is real, the cheapest experiments to test demand before building, a rough viability check (market, competition, economics), and a go/refine/rethink call — honest, not a cheerleader.

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

Write a board pre-read that's sent before the meeting so the meeting is about decisions, not status. Use when asked to prepare a board pre-read, a board update/package, or pre-meeting materials for a board. Produces a board pre-read — a TL;DR, the metrics dashboard vs. plan, what's working / what's not, the decisions and asks for the board, and risks — designed to be read in advance.

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

Surface the hidden assumptions a plan or belief rests on, then test what happens when each one is wrong. Use when asked what am I assuming here, check my assumptions, what if I'm wrong about, or stress-test my thinking. Produces the unstated assumptions your conclusion depends on (ranked by how load-bearing they are), a flip of each to see which one breaking would change everything, and the cheapest way to check the riskiest ones — because the assumption you didn't know you were making is what sinks plans.

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

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

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

Review AI-authored code for its characteristic failure modes — plausible-but-wrong logic, hallucinated APIs, over-engineering, dead scaffolding, and silent security shortcuts. Use when reviewing an AI-generated or heavily AI-assisted PR, when AI-written code keeps shipping subtle bugs, or when setting review standards for a team using coding agents. Produces a focused review with AI-specific findings, verification steps per risk class, and a team checklist for AI-authored changes. For general PR review use code-review-checklist — this skill covers what that one assumes a human wouldn't do.

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

Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.

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

Help users de-risk new product bets by testing core assumptions, building low-fidelity prototypes, and gathering high-signal evidence before investing heavy engineering resources.

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

Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.

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

Use when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky, disputed, or technically questionable.

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

Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.

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

Architecture specialist for software/system design, module and service boundaries, tradeoff analysis, and stakeholder synthesis. Uses context-aware methods such as diagnostic routing, design-twice comparison, ATAM-style risk analysis, CBAM-style prioritization, and ADR-style decision records.

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

Break large features into independently verifiable, human-reviewable slices under a feature directory in specs/. Use for risky or multi-step feature work that needs upfront questioning, API seams, browser-playable checkpoints, HTML visualizations, screenshot gates, staged implementation plans, recursive fog-of-war reslicing, or proactive research into reference implementations/best practices before slicing. Pairs with your project's verification harness and screenshot gates (the browser checkpoints), [refactor-clean](../refactor-clean/SKILL.md) (review the materialized spec so the plan describes one-owner architecture, not the feature bolted on), [screenshot-critique](../../visual/screenshot-critique/SKILL.md) and [compare-screenshots](../../visual/compare-screenshots/SKILL.md) (the visual gates), and a code-review pass (audit each slice before it lands).

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

Use when the user asks what they are not seeing, what they forgot, what could go wrong, or what an expert would say about a plan, decision, document, code change, or setup they already have. Triggers: "what am I missing", "what don't I know", "poke holes in this", "what would an expert ask", "что я упускаю", "что я не вижу", or /clueless-blindspots. One-shot review; does not change the always-on level.

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

Review code for security problems; scan for vulnerabilities, secrets, dependency and prompt risks. Use when: asked whether code is safe to ship, even one small handler.

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

End-to-end Codex-native Amazon FBA research workflow using LaunchFast MCP. Use when the user wants a single report covering product research, IP risk, supplier sourcing, and PPC keyword intelligence. Requires `research_products`, `ip_check_manage`, `supplier_research`, and `amazon_keyword_research`.

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

Use when reading, editing, or generating a Bethesda Game Studio load-order file (plugins.txt / loadorder.txt) for Fallout 4, Skyrim SE/AE/VR, Fallout 76, Starfield, or when launching xEdit with a custom plugin list. Authoritative reference for the asterisk-prefix format, official masters detection, ESL handling, and the routing rules between plugins.txt editing and xEdit daemon commands.

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