'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

Organize GitHub issues and pull requests found during quality assurance testing. Apply release tracking labels, classify bugs by four severity levels, and label multiple findings while keeping documentation issues and feature requests outside the severity scheme.

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

• Group QA findings by release
• Classify bugs by severity
• Apply labels to multiple issues and pull requests

Retrieve current cyber threat data, including malware indicators, addresses of attacker control servers, and vulnerabilities known to be exploited. Filter by threat type, source, severity, and date to identify relevant threats for review and reporting.

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

• Reviewing recently observed malware indicators
• Finding high-severity exploited vulnerabilities
• Checking attacker control server indicators

Scan declared MCP servers and tools for permission, policy, and dependency issues without executing them. Produce JSON or a Markdown table, and set a severity threshold that determines whether a CI check fails.

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

• Review declared MCP server and tool permissions
• Check policy and dependency issues in MCP configuration
• Fail CI when findings reach a chosen severity

Generate a read-only security report on threats involving MCP connections and operations. It groups findings by threat, reports the highest severity, and supports table or JSON output with a configurable severity threshold for failure.

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

• Prepare security findings before a release
• Share a categorized threat report with a security team
• Check changes in MCP-related threats during periodic audits

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

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

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