'risk' 검색 결과

Assess code change risk, locate complex areas, and inspect file statistics with ruflo analysis commands. The skill also guides running and extending ruflo’s regression guards, automated checks that help catch previously fixed problems.

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

• Assessing risk before reviewing a code change
• Finding complex code that needs attention
• Running ruflo regression guards locally

Organize ISO evidence for medical devices and laboratories, including controlled documents, risk records, corrective actions, and supplier controls. Produce structured gap reports for authorized human review while keeping certification, accreditation, and regulatory processes distinct.

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

• Organize controlled documents and implementation records
• Check links in medical-device risk and design records
• Review corrective-action and supplier-control evidence

Check token security audit data before buying or swapping crypto. Review contract and trading risks, buy and sell taxes, and signs of scams such as tokens that can be bought but cannot be sold.

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

• Check token risks before a purchase or swap
• Look for tokens that can be bought but not sold
• Review dangerous contract functions and owner controls

Assess the security of LLM applications and AI agents by tracing inputs, retrieved content, tool calls, and outputs. Covers prompt injection, where content carries unwanted instructions, along with permission misuse, memory poisoning, and supply-chain risks.

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

• Testing chatbot resistance to prompt injection
• Auditing agent tool permissions and approval steps
• Checking retrieval access controls and memory poisoning

Review a product or major feature before development starts. Assess demand, revenue, repeat use, trust, and user reach, then identify the riskiest assumption, a small validation step, and work to delay.

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

• Check demand and revenue assumptions before building an MVP
• Review positioning before creating a landing page
• Assess adoption risk for a major feature

Review a pull request or code diff for bugs by reading callers, expected behavior, and nearby error handling. Receive findings tied to specific lines, ranked by severity, plus a summary of merge risks and needed tests.

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

• Checking a pull request for behavioral regressions
• Reviewing risks to stored data
• Investigating input validation and access checks

Review an AI agent codebase against ten OWASP ASI security risk areas. Examine tool permissions, input validation, identity checks, audit logs, and other controls, then summarize coverage, gaps, and recommended improvements in a report.

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

• Reviewing agent security before production deployment
• Mapping existing controls to ten security risk areas
• Preparing findings for a security review or audit

Compare yields from decentralized finance lending, liquidity provision, and staking. Assess returns alongside price-related losses, smart contract risks, and dependence on token rewards, then organize opportunities by risk and the sustainability of their income sources.

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

• Compare lending and staking yields with their risks
• Estimate liquidity pool returns after price-related losses
• Assess whether rewards depend on token issuance

Assess whether a Chinese A-share company may receive ST or *ST risk warnings next financial year. Review financial forecasts, dividends, audit opinions, and regulatory penalties, then report risk severity separately from confidence in the prediction.

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

• Reviewing a Chinese A-share company's future ST risk
• Assessing escalation risk for an existing ST or *ST stock
• Checking revenue, equity, and dividend warning signs

Review upcoming customer renewals, assess risk and potential contract increases, and identify next steps with supporting evidence. It also flags missing renewal opportunities and inconsistent records, and prepares a detailed renewal brief for an individual account.

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

• Reviewing upcoming renewals across your accounts
• Finding at-risk renewals that need action this week
• Preparing a renewal discussion for a specific account

Turn project or team updates into a structured report for leaders and stakeholders. The skill summarizes key metrics, accomplishments, ongoing work, risks, decisions needed, and next-period priorities, with an overall assessment of whether work is on track.

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

• Write weekly, monthly, or quarterly progress reports
• Summarize progress against key metrics and targets
• Highlight risks and decisions needing stakeholder attention

Explore code structure and history using an index of code relationships and meaning-based search. Trace calls, assess change impact, find likely bug locations, generate architecture reports, and review pull requests for risk and conflicts.

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

• Tracing function calls and change impact
• Investigating code locations related to a GitHub issue
• Generating architecture reports and class diagrams

Review code for privacy risks, prepare data protection impact assessments, and track personal data requests and deadlines. The skill supports GDPR and German privacy compliance work, with final compliance decisions referred to a data protection officer or legal counsel.

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

• Checking a service's code for privacy risks
• Preparing a data protection impact assessment
• Tracking deadlines for access and erasure requests

Prepare internal audit materials for ISO/IEC 42001:2023, the AI management system standard. Identify gaps, link AI risks to controls, and build a 12-month audit plan with coverage priorities and auditor independence checks.

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

• Prioritizing gaps before certification
• Linking AI risks to Annex A controls
• Planning a year of internal audits

Manage complex software and SaaS projects by assessing schedules, budgets, quality, risks, and team capacity. Compare priorities across projects, identify resource constraints, and turn portfolio analysis into executive reports with recommendations for decisions and follow-up.

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

• Review progress and health across multiple projects
• Assess risks and prioritize response actions
• Rebalance staffing based on team capacity

Assess security risks in AI systems by scanning prompts for known attack patterns and scoring data exposure, poisoning, and tool abuse risks. Map findings to MITRE ATLAS, an AI threat framework, and identify protective controls.

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

• Scan application prompts for injection and jailbreak patterns
• Review malicious instructions in retrieved documents
• Assess training data exposure and poisoning risks

Examine feature ideas for existing products to uncover risky assumptions about customer value, usability, business support, and technical feasibility. Consider product, design, and engineering perspectives, then record potential failures, confidence levels, and suggested ways to test each assumption.

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

• Reviewing assumptions behind a feature idea
• Assessing risks from three professional perspectives
• Planning how to test uncertain assumptions

Review a product plan by imagining a failed launch and tracing possible causes. Separate real risks, overblown concerns, and unspoken worries, then define mitigation actions, owners, and deadlines for issues that must be resolved before launch.

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

• Checking launch plans for possible failure causes
• Separating real risks from overblown concerns
• Surfacing assumptions the team has not discussed

Identify untested assumptions behind a new product idea across eight areas, including customer value, usability, business viability, technology, ethics, market launch, strategy, and team. Rate confidence in each assumption and suggest a test, producing a Markdown analysis.

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

• Checking assumptions behind a new product concept
• Reviewing launch channels and messaging assumptions
• Examining technical and team risks together

Create an AI impact assessment in your team's format. Gather system details through conversation, analyze risks and applicable regulatory classifications, check consistency with internal policy, and document recommendations, safeguards, and conditions for deployment.

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

• Assessing an AI system before deployment
• Preparing an assessment after conditional triage
• Reviewing pilot or production AI risks

Build an AI system register for EU AI Act reviews. Track owners, deployment status, EU connections, and each system’s role and risk category through a guided discussion, preserving classification reasons and dates for future review.

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

• Register AI systems used or planned across an organization
• Review each system’s role and risk category
• Find systems approaching their next review date

Audit npm, PyPI, and Go dependencies for version-specific advisories, inactive upstream projects, concentrated npm publishing rights, and installation scripts. Produce a report backed by collected data, with assessment coverage, action priorities, and upgrade or replacement guidance.

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

• Reviewing dependency risks before an engagement
• Checking advisories across a lockfile dependency tree
• Finding abandoned or archived dependencies

Compare business growth options across existing and new products and markets. The skill connects each option to documented demand signals, rates its risk, and recommends an order of action with the assumption that could change it.

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

• Compare growth options for next year's business plan
• Check the evidence behind a diversification proposal
• Sequence growth initiatives by risk and funding needs

Assess a fixed code patch for behavior changes, regression risks, test coverage, and recovery options. Receive an evidence-based report and structured assessment indicating whether it is ready to merge and qualifies as an automatic merge candidate.

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

• Reviewing the risks of an AI-generated patch
• Checking affected behavior before merging a pull request
• Assessing whether tests protect changed behavior