“severity”的搜索结果

Combine laboratory animal welfare measurements into reference-relative RELSA severity scores. Analyze individual trajectories, explore forecasts for specified observation times, and derive candidate score zones, with explicit checks on normalization, reference selection, prediction intervals, and evaluation limits.

中文简介正在准备中。当前显示英语简介。

• Combine animal welfare measurements into daily scores
• Compare group severity using a shared reference
• Explore severity forecasts at specified observation times

Turn a Markdown code review into a single HTML file with code changes beside severity-labeled comments. Readers can jump to findings, inspect line numbers, and identify the named human reviewer.

中文简介正在准备中。当前显示英语简介。

• Turning a lengthy Markdown code review into HTML
• Reading code changes beside review comments
• Jumping directly to findings by severity

Investigate Sentry alerts using Datadog logs and recent GitHub changes, then post an initial diagnosis with a severity assessment. Notify the on-call team when severity reaches the configured threshold or the investigation remains inconclusive, without changing monitored systems.

中文简介正在准备中。当前显示英语简介。

• Investigate new and unresolved Sentry alerts
• Compare failures with logs and recent deployments
• Notify on-call staff for severe or inconclusive alerts

Prepare Bugcrowd submissions with accurate vulnerability categories, evidence-based severity requests, and explanations of program scope. Structure references between related reports, document QA testing conditions, and draft responses when a finding is downgraded or considered out of scope.

中文简介正在准备中。当前显示英语简介。

• Choose a suitable Bugcrowd vulnerability category
• Explain a severity request using demonstrated impact
• Respond to out-of-scope decisions

用于开发嵌入电子病历的临床决策支持，涵盖药物相互作用、剂量验证和临床评分，并按警报严重程度设计界面行为及检测漏报警的测试。

• 实现药物相互作用与过敏检查
• 根据患者信息验证剂量
• 实现NEWS2等临床评分

Organize parallel code reviews across security, performance, architecture, testing, and accessibility. It helps assign review areas, merge duplicate findings, apply consistent severity ratings, and produce one report with locations, impacts, suggested fixes, and prioritized actions.

中文简介正在准备中。当前显示英语简介。

• Assigning review areas for a code change
• Merging duplicate findings from multiple reviewers
• Aligning severity ratings across review reports

为QA测试发现的GitHub Issue和PR添加发布版本追踪标签，并按影响程度与变通方案为漏洞分类。支持批量添加标签，严重程度标签仅用于程序缺陷。

• 按发布版本整理QA发现的问题
• 划分程序缺陷的严重程度
• 批量为Issue和PR添加标签

获取恶意软件感染指标、攻击者控制服务器地址及已确认遭利用的漏洞信息，按类型、来源、严重程度和观测时间筛选，整理当前网络威胁记录。

• 查询近期恶意软件指标
• 检查严重且已遭利用的漏洞
• 核查攻击者控制服务器指标

以只读方式检查MCP连接与操作相关的威胁，按威胁整理发现并报告最高严重程度，可输出表格或JSON，帮助准备发布前的安全审查材料。

• 开展发布前的安全检查
• 准备提交给安全团队的报告
• 在定期审计中检查威胁变化

读取已声明的MCP服务器和工具配置，静态检查权限、策略及依赖问题，输出检查结果，并可按问题严重程度设置使CI检查失败的条件。

• 检查MCP服务器和工具权限
• 检查配置策略与依赖问题
• 按严重程度判定CI是否失败

Turn Strix vulnerability findings into focused code fixes, prioritized by severity. Address root causes, rerun security scans and original exploit examples, and report the changes and verification results for each issue.

中文简介正在准备中。当前显示英语简介。

• Fixing vulnerabilities reported by Strix
• Prioritizing remediation by severity
• Retesting original exploits after code changes

Build text and image checks in TypeScript with Azure AI Content Safety. The skill covers harmful content categories, severity scores, and custom text blocklists, with examples for authentication, error handling, and decisions about allowing content.

中文简介正在准备中。当前显示英语简介。

• Implement harmful text checks for user posts
• Analyze images and retrieve category severity scores
• Create and maintain custom prohibited term lists

Draft malware incident communications for internal teams, executives, IT responders, customers, and regulators. Provides structured templates and severity-based notification workflows to organize impact details, response actions, decisions needed, and the timing of updates.

中文简介正在准备中。当前显示英语简介。

• Prepare an initial internal notification about a malware incident
• Summarize business impact and decisions for executives
• Draft technical response instructions for IT teams

Manage service incidents from initial assessment through recovery review. The skill organizes severity, impact, roles, status updates, and timelines, then drafts a blameless postmortem with root cause analysis and action items assigned to owners.

中文简介正在准备中。当前显示英语简介。

• Assess the severity and impact of a new incident
• Draft internal and customer status updates
• Record mitigation steps and an incident timeline

Organize responses to service outages and degraded performance, from initial assessment through recovery review. Classify severity, reconstruct event timelines, draft stakeholder updates, and create response guides and follow-up actions based on incident findings.

中文简介正在准备中。当前显示英语简介。

• Classify outage severity and plan initial response
• Reconstruct an incident timeline from scattered events
• Draft incident updates for customers and internal teams

Review an authorized security issue in its private workflow. Check the affected code, assess whether the report is valid, explain severity and attack prerequisites, and propose a remediation plan with focused tests.

中文简介正在准备中。当前显示英语简介。

• Checking whether a vulnerability report is valid
• Assessing impact and severity
• Planning fixes and focused tests

Investigate a possible incident in Superset’s hosted services by checking deployments, error spikes, and service health. Produce a proposed severity and status page update for human review, without changing services or publishing messages.

中文简介正在准备中。当前显示英语简介。

• Investigating a reported Superset outage
• Checking the scope of a sudden increase in errors
• Drafting an incident severity and status page update

Review dependency files to find outdated packages and security vulnerabilities. Sort updates by severity and version change, identify cases needing human review, and record a prioritized update list with testing requirements.

中文简介正在准备中。当前显示英语简介。

• Prioritizing outdated dependencies
• Separating security fixes by severity
• Identifying major updates needing human review

Trace a security finding from an attacker’s entry point to its impact using repository evidence. Examine access, permissions, existing defenses, and counterevidence to assess severity and decide whether the finding warrants reporting.

中文简介正在准备中。当前显示英语简介。

• Trace how an attacker could exploit a finding
• Reassess severity against existing defenses
• Check counterevidence before reporting

Run an audit, separate findings that can be fixed automatically from those needing manual work, and apply eligible fixes with tests and separate commits. Use severity filters, a finding limit, or a classification-only dry run.

中文简介正在准备中。当前显示英语简介。

• Fixing audit findings with test verification
• Prioritizing findings by severity
• Limiting how many findings are fixed

Manage service incidents from initial assessment through recovery review. The skill organizes severity, impact, roles, status updates, and timelines, then drafts a blameless postmortem with root cause analysis and action items assigned to owners.

中文简介正在准备中。当前显示英语简介。

• Assess the severity and impact of a new incident
• Draft internal and customer status updates
• Record mitigation steps and an incident timeline

Trace a security finding from an attacker’s entry point to its impact using repository evidence. Examine access, permissions, existing defenses, and counterevidence to assess severity and decide whether the finding warrants reporting.

中文简介正在准备中。当前显示英语简介。

• Trace how an attacker could exploit a finding
• Reassess severity against existing defenses
• Check counterevidence before reporting

Turn validated security findings into clear bug bounty reports for HackerOne, Bugcrowd, Intigriti, or Immunefi. Provides templates, reproducible evidence structure, severity scoring guidance, and submission checks focused on demonstrated impact.

中文简介正在准备中。当前显示英语简介。

• Draft a report for a specific bounty platform
• Document reproducible requests and evidence
• Explain severity using demonstrated impact

Evaluate security findings before writing a bug bounty report. Check reproducibility, scope, practical impact, duplicates, and behavior across user sessions, then use submission checklists and CVSS 3.1 guidance to prepare evidence and assess severity.

中文简介正在准备中。当前显示英语简介。

• Deciding whether a finding is ready to report
• Rechecking access across different user sessions
• Reviewing duplicate or intended behavior