966 skills · sorted by relevance
Assess business impact of a proposed change. Use when the user says "impact assessment", "impact analysis", "what will this change affect", "change impact", "who is impacted", "ripple effects", "downstream impact", "impact mapping", "what breaks if we change this", "readiness for change" - even if they don't explicitly say "impact assessment".
The English summary is being prepared. Showing the original description.
Assess how changes, failures, or paused updates to a BigQuery table or view affect downstream assets. Trace data lineage, the relationships showing where data flows, and summarize dependent tables, dashboards, and processes with direct and indirect impacts.
Map the impact of a proposed change using real dependencies and project documentation. Identify affected code, data, interfaces, tests, and release steps, then compare the implemented changes with the plan to expose gaps and unverified risks.
Assess the impact of code changes with GitNexus by tracing callers, dependencies, and affected execution flows. Check existing changes and report their scope, risk, and uncertainty before editing or committing.
Assess potential data breach impact by reviewing sensitive data and its movement through a codebase. Produce an inventory, exposure rankings, financial estimates, and prioritized safeguards, distinguishing legal source figures from planning estimates.
Model trading costs and execution assumptions in backtests, including slippage, the gap between expected and simulated fill prices. Compare price impact, fees, execution delays, and order splitting to assess how assumptions affect strategy results.
Review new and spiking Sentry errors, rank their impact, and check for existing GitHub issues. Create triage issues for the highest-impact untracked errors and post a Slack summary, while leaving Sentry error states and assignments unchanged.
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.
Expert knowledge for Azure Impact Reporting development including troubleshooting, configuration, and integrations & coding patterns. Use when wiring Impact Reporting to Monitor alerts, Logic Apps, Service Health, HPC Guest Health, or diagnostic logs, and other Azure Impact Reporting related development tasks. Not for Azure Carbon Optimization (use azure-carbon-optimization), Cost Management (use azure-cost-management), Azure Monitor (use azure-monitor).
The English summary is being prepared. Showing the original description.
Guides the post-Schrems II Transfer Impact Assessment process following EDPB Recommendations 01/2020 six-step methodology. Covers destination country surveillance law assessment, European Essential Guarantees evaluation, and supplementary measures determination. Keywords: TIA, transfer impact assessment, Schrems II, EDPB recommendations, supplementary measures.
The English summary is being prepared. Showing the original description.
Guides privacy law change monitoring and impact assessment for multi-jurisdiction organisations. Covers regulatory tracking sources, change classification, impact scoring methodology, and implementation prioritisation. Keywords: law monitoring, regulatory tracking, change management, impact assessment, implementation priority.
The English summary is being prepared. Showing the original description.
Use when ranking backlogs, deciding what to do first based on effort vs impact (quick wins vs big bets), prioritizing feature roadmaps, triaging bugs or technical debt, allocating resources across initiatives, identifying low-hanging fruit, evaluating strategic options with 2x2 matrix, or when user mentions prioritization, quick wins, effort-impact matrix, high-impact low-effort, big bets, or asks "what should we do first?".
The English summary is being prepared. Showing the original description.
Use when looking up journal impact factors (JCR IF), checking a journal's impact factor by name, comparing IF across journals, or answering questions about "影响因子" / "impact factor" / "IF". Triggers on "impact factor", "journal IF", "影响因子", "JCR", "IF score", "journal rank", "which journal has higher IF", "what is the IF of". PROACTIVELY USE when user mentions journal prestige, publication venue quality, or manuscript submission target evaluation.
The English summary is being prepared. Showing the original description.
Assessing anthropogenic environmental impacts — pollution pathways, habitat destruction and fragmentation, land-use change, invasive species, overharvest, and extinction debt. Covers environmental impact assessment (EIA) methodology, exposure-effect relationships, population viability analysis, IPAT and ecological footprint frameworks, and strategic environmental assessment. Use when quantifying or forecasting human impacts on ecosystems, designing monitoring programs, or evaluating a proposed intervention against a baseline.
The English summary is being prepared. Showing the original description.
事業継続計画（BCP）と災害復旧計画（DRP）の策定支援スキル。ビジネスインパクト分析、リスク評価、復旧戦略策定、 BCP/DRP文書作成、テスト・訓練計画を提供。ISO 22301準拠。 Use when developing business continuity plans, disaster recovery strategies, or conducting business impact analysis. Triggers: "BCP", "business continuity", "disaster recovery", "DRP", "business impact analysis", "BIA", "contingency planning".
The English summary is being prepared. Showing the original description.
Builds and maintains a DRAFT impact log from notes, messages, status updates and completed work: one row per outcome with its evidence and evidence level, date, who benefited and the source it traces to, plus a gap list of outcomes that still lack evidence, structured so a later review, appraisal or promotion case can draw on it. Use when the user asks to "start an impact log", "add this to my impact log", "log what I achieved this quarter", "pull my wins out of these notes", "turn these messages into evidence for my review" or "what do I have evidence for so far". Do not use for a performance rating, ranking, pay or promotion decision, the skill records evidence and never judges it; for the review narrative itself, use performance-review-drafter; for a role profile built from the work, use job-description-drafter instead. Drafts for human review; never approves, authorises or signs off.
The English summary is being prepared. Showing the original description.
Build a staff-engineer promotion deck that connects responsibilities, evidence, work artifacts, and impact. Present the case to a manager or review committee using a white editorial HTML template with speaker notes and slide navigation.
Review Archify issues, pull requests, and code by weighing user value, implementation and maintenance costs, and wider impact. Use evidence to decide whether work is worthwhile, compare alternatives, and identify questions that still affect the decision.
Review website image delivery and configure an image CDN, a service that optimizes and distributes images. Check file formats, dimensions, loading behavior, and initial screen impact, with guidance on verifying changes in DevTools.
Generate sound effects and ambient audio from written descriptions using ElevenLabs. Create cinematic impacts, app notification sounds, or background textures, with controls for duration, seamless looping, and how closely the sound follows the description.
Organize Power Automate flows by business impact and responsible team using FlowStudio’s cached records. Find resources without active owners, audit connections to other services, review compliance metadata, and configure notifications for failures or missing runs.
Turn work history into clear accomplishment statements for performance reviews, promotion cases, and weekly updates. Use Copilot CLI sessions, git commits, and GitHub pull requests to connect each action with its result and supporting evidence.
Explore unfamiliar code with Codebase Memory to map architecture, trace function calls and dependencies, and assess change impact. Findings are checked against source files, with index freshness and coverage considered before drawing conclusions.
Assess whether a container can escape its isolation and reach the host during an authorized security test. Review privileges, shared mounts, Docker socket exposure, and runC vulnerabilities, then document demonstrated impact and remediation.