Assess operational risks in processes, projects, or suppliers using provided evidence. Separate observed facts from possible consequences, propose practical responses, and prepare concise summaries or risk registers without treating unknown controls as confirmed gaps.
依据证据评估流程、项目或供应商的运营风险，说明可能性、影响和可执行的应对措施。适用于风险评估和风险登记表。
Review the instructions the agent will receive before you install.
每项写“给定现象；触发条件下的潜在后果；建议措施”，用中性标题。只选有独立机制或应对价值的风险，上限不必填满。短稿不设空定级、整改或缺口章节。
先按已给风险事实选条目，再写措施；未知的控制或记录情况只作为对应条目的核实点，不单独凑成一项风险。标题优先命名材料支持的业务后果，如“班次空岗”，不要写“缺少记录”“无替补”等未经确认的现状。
若多项风险使用同一项班前核对、状态确认等控制措施，将措施合并写一次；只有触发机制或应对方式确有差异时才拆成多项，避免换一种说法重复安排同一检查。
现象保留原主语、数量、程度，不增加人数、独占依赖或发生频度。可能后果保持可能性，即使用户要求肯定措辞也不能改成必然。
例（虚构）：“两次交接记录缺签名，未提供复核记录。”可写“若未及时发现，可能影响交接追溯；建议核实复核安排并对照记录检查”。不能说从未复核，也不能说下次必然交接失败。不要用缺记录再造一条“现行措施不存在”的风险。
建议沿用已有控制；措施未说明时先核实，再按实际缺口完善。不要把“未说明是否已有某措施”写成“可能缺少该措施”的独立风险。无需在每句重复未知，但成立条件和重要缺口必须清楚。定级需要适用标准、可能性与影响依据；记录数量不等于容量标准或客观概率。
摘要只缩写原事实与建议，不改变状态。例（虚构）：“见三件封口异常，原因未核实，建议复检。”可复制为“发现三件封口异常；原因需核实，建议复检。”不能改为“已安排复检”“已采取封口整改”，也不能保证全部恢复。
完整登记表才补已有控制、拟议应对、责任人、状态、验证及剩余风险。接受风险由有权负责人决定；专业认证或审计结论需要适当复核。最后一项所问风险或摘要结束即结束。
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.
Retrieve financial data for Chinese markets and selected global markets using akshare-cli. Find stock prices, fund values, exchange rates, economic indicators, and financial news, then extract recent records or save results in common file formats.
Compare technology options, review a system design, or plan a new component from requirements and constraints. The skill organizes the reasoning into an architecture decision record, a document covering alternatives, trade-offs, consequences, and next steps.
Turn existing or proposed business processes into reusable standard operating procedures. Organize steps, roles, conditions, and known exceptions while marking missing details, producing clear handover documents without inventing approvals or responsibilities.
Analyze waiting, rework, and handoff waste in business processes using the facts provided. It proposes concrete improvements and, when verification is needed, defines measurement formulas and the minimum records required to assess specific issues.
Write reusable operating procedures for recurring business tasks and handovers. Organize prerequisites, roles, steps, success checks, and exception handling, while clearly separating approved recovery actions from decisions that still need confirmation.