'impact' 검색 결과

Conduct Fundamental Rights Impact Assessments (FRIA) for high-risk AI systems as required by EU AI Act Article 27. Use when (1) deployers of high-risk AI systems (Annex III) need to assess fundamental rights impacts before first use, (2) public bodies or private entities providing public services are deploying AI systems, (3) credit scoring or insurance risk assessment AI systems are being deployed (Annex III 5b, 5c), (4) evaluating impact on natural persons' fundamental rights (dignity, liberty, privacy, data protection, non-discrimination, children's rights, etc.), or (5) creating EU AI Act Article 27 compliance documentation with market surveillance notification.

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

Calculates dilutive impact of equity issuance on existing shareholders with EPS, ownership, and NAV per share analysis. Use when modeling dilution, communicating shareholder impact, or comparing capital raise alternatives.

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

This skill should be used when analyzing recent market-moving news events and their impact on equity markets and commodities. Use this skill when the user requests analysis of major financial news from the past 10 days, wants to understand market reactions to monetary policy decisions (FOMC, ECB, BOJ), needs assessment of geopolitical events' impact on commodities, or requires comprehensive review of earnings announcements from mega-cap stocks. The skill automatically collects news using WebSearch/WebFetch tools and produces impact-ranked analysis reports. All analysis thinking and output are conducted in English.

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

Analyzes the downstream impact (blast radius) when a BigQuery table or view is broken, stale, or modified. Identifies all downstream tables, dashboards, and processes that will be affected. Use when: - Performing a blast radius or impact analysis for a BigQuery table or view. - Assessing the consequences of modifying, deleting, or pausing updates to a BigQuery asset. - Identifying downstream dependencies (tables, dashboards, processes) of a BigQuery asset. Don't use for: - General BigQuery querying or data analysis (use BigQuery-related tools instead). - Non-BigQuery assets (e.g., Cloud Storage files) unless they are part of the BigQuery lineage. - Creating or modifying lineage links directly.

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

OpenLineage, DataHub, Marquez for data lineage tracking and impact analysis. Activate on: data lineage, OpenLineage, DataHub, Marquez, impact analysis, data catalog, column lineage, data discovery. NOT for: data quality validation (use data-quality-guardian), dbt documentation (use dbt-analytics-engineer).

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

Use this skill when a company needs recovery objectives it can defend, before a continuity plan, a disaster recovery design, an audit or a resilience review, and asks "do a BIA", "business impact analysis", "set our RTO and RPO", "what is our maximum tolerable downtime", "which services are critical", "impact tolerance" or "can our backups meet our recovery targets". Lists services from the customer's view, prices an outage over time in the company's own money and obligations, sets recovery time and data loss objectives, maps dependencies, and compares each objective with what backups, restore tests, suppliers and people actually allow, listing the gaps for a decision.

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

Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs to reconstruct forgotten work, plus git commits and GitHub PRs. Enforces a 3-part impact contract (action → result → evidence). Works standalone with zero dependencies. Trigger for: "brag", "log work", "what did I do", "backfill my work history", "performance review", "self-review", "self assessment", "write impact statement", "review prep", "promo packet", "promotion case", "weekly update", "status report", "accomplishments", "what did I ship", "I forgot to log my work", "summarize my work", "track my wins", "what should I highlight", "end of half", "career growth", "work journal", or any request to document, summarize, or organize work accomplishments.

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

Prepares a DRAFT data incident impact brief from the incident notes and data inventory the user provides: the timeline as stated, systems involved matched to the inventory, data categories held and evidenced as involved, people and record counts potentially affected with the source and method behind every figure, third parties, notification questions for legal and the data protection officer, and every UNKNOWN with the evidence that would settle it. No legal determination: it never states whether the incident is a reportable breach, whether notice is due, to whom or by when. Use when the user asks to "prepare the impact brief for this incident", "what data was involved", "how many people are affected", "map the incident to our data inventory" or "pull together what legal needs on the incident". Do not use for the blameless postmortem or root-cause timeline, use incident-postmortem-drafter instead. Drafts for human review; never approves, authorises or signs off.

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

Drafts a blameless incident postmortem (summary, impact, timeline, detection and response, contributing factors as candidates for review, action items) from an incident channel export, ticket notes and any alert or change records, with UNKNOWN for every fact the inputs do not contain. Never assigns blame, names a root cause or re-rates severity. Use when the user asks to "write the postmortem for this incident", "build the incident timeline from the chat export", "draft the post-incident review" or "turn this ticket and channel log into an incident report". Do not use for a knowledge article from the resolved ticket, use knowledge-article-drafter instead; for project retrospectives, use lessons-learned-synthesis; for data-breach impact and notification questions, use data-incident-impact-brief. Drafts for human review; never approves, authorises or signs off.

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

Reads a project or processing description and returns a DRAFT data protection impact assessment pack: processing description, necessity and proportionality questions, a risk table with blank rating cells, mitigations to consider and open questions. Never rates risk, determines the lawful basis or judges adequacy; the DPO assesses and signs. Works from descriptions, never personal data. Use when the user asks to "start a DPIA for the new monitoring tool", "draft a data protection impact assessment", "scaffold a DPIA from this processing description" or "what would the DPO need for a DPIA on this". Do not use for redacting or de-identifying a document, use document-deidentification-pass instead; do not use for working out what data an incident exposed, use data-incident-impact-brief instead. Drafts for human review; never approves, authorises or signs off.

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

diff-time で「影響範囲を repo 全体で調査した証拠」「失敗系を検証した証拠」「外部依存・レート制限・キャッシュ整合を確認した証拠」の欠落を検出する evidence-sufficiency 観点。defect そのものは既存 skill へ委譲し、本 skill は「そのリスク種別を調査した証拠が差分・PR 本文・テストに残っているか」の meta 評価のみを行う。証拠が同一 diff に同梱（テスト・canary・grep 記録）されていれば充足とみなす

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

OpenLineage, DataHub, Marquez for data lineage tracking and impact analysis. Activate on: data lineage, OpenLineage, DataHub, Marquez, impact analysis, data catalog, column lineage, data discovery. NOT for: data quality validation (use data-quality-guardian), dbt documentation (use dbt-analytics-engineer).

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

[30] ANALYZE. Understand how changes impact the system — what's the core, what's affected, what depends on what. Use when planning changes, analyzing systems, debugging issues, or anytime you need to see the full picture of cause and effect. Triggers on "what's affected", "impact analysis", "dependencies", "scope mapping", or when you need to understand ripple effects.

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

지정한 대화와 기간에 공유된 OpenClaw 변경 제안과 이슈를 모읍니다. GitHub에서 상태와 근거를 확인하고 영향도와 처리 준비 정도에 따라 우선순위를 정합니다.

• 지난주 대화에 공유된 PR 정리
• 기존 목록에 있는 제안의 상태 재확인
• 같은 기간에서 목록에 없는 제안 찾기

저장소에서 외부 요청이나 사용자 입력으로 악용할 수 있는 취약점을 찾습니다. 입력 경로와 재현 절차, 영향을 확인해 버그 바운티 보고서 작성을 지원합니다.

• 외부 요청으로 도달 가능한 취약점 조사
• 정적 분석 결과 검토
• 최소 재현 절차와 영향 정리

모호한 기능 요청이나 영향이 큰 변경의 범위·전제·위험을 정리합니다. 기대 동작과 검증 방법을 명시한 인수 기준이나 인계 자료로 만듭니다.

• 모호한 기능 요청을 정리합니다
• 인증 변경과 데이터 이전 기준을 만듭니다
• 다른 에이전트나 팀에 구현을 인계합니다

고객의 구독·청구 상태를 조사하고 중복 구매와 갱신 실패를 분류합니다. 환불·해지·청구 관리 화면 복구부터 고객 답변 초안과 제품 개선 사항까지 정리합니다.

• 중복 구독과 의도하지 않은 청구 조사
• 갱신 실패와 결제 수단 문제 대응
• 청구 관리 및 해지 화면 복구

Explore a knowledge graph, a network of entities and relationships, from a chosen starting point. Rank relevant paths and summarize dependencies or indirect connections to help understand code structure and assess the impact of changes.

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

• Assessing the impact of changing a component
• Tracing dependency chains
• Discovering indirect connections between entities

Extract classes, functions, modules, and their relationships from source code or documentation into AgentDB. Build a knowledge graph, a map of connected entities, to understand code structure, dependencies, and potential change impacts.

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

• Understanding a codebase's structure
• Investigating dependencies between modules
• Assessing the impact of code changes

Audit website images and guide conversion to WebP and AVIF, formats that reduce image transfer size. Identify affected files, add fallback images, and review dimensions and loading behavior alongside the impact on initially visible content.

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

• Finding JPEG and PNG images to convert
• Adding WebP and AVIF sources with fallback images
• Reviewing CSS background image formats

Guide production incident handling by establishing impact, start time, and recent changes before proposing action. Document evidence for rollback requests, keep the issue updated, and distinguish service recovery from resolution that explains the incident.

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

• Establish the impact and start time of a production incident
• Check whether deployments align with the incident timeline
• Prepare a rollback request with supporting evidence

Prepare and review research funding proposals for NSF, NIH, DOE, DARPA, and Taiwan NSTC. Maps application requirements to draft sections, identifies gaps, and helps refine research aims, budgets, impact statements, and responses to reviewers.

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

• Map funding-call requirements to proposal sections
• Review research aims against evaluation criteria
• Align budgets and timelines with the research plan

Examine hidden assumptions behind decisions, business ideas, or personal beliefs. Classify each premise, rank it by fragility and impact, and rebuild the conclusion from verified evidence, with concrete questions showing what to check first.

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

• Examining assumptions behind a career change
• Testing the premises of a startup idea
• Questioning beliefs treated as obvious facts

Review Monte Carlo alerts, score their likelihood of indicating an incident and their potential impact, and investigate likely causes. Use the same stages to design and test a repeatable triage workflow, starting with recommendations before enabling actions.

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

• Reviewing recent Monte Carlo alerts
• Prioritizing alerts by incident likelihood and impact
• Designing and testing a recurring triage workflow