1.1K skills · sorted by relevance
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing. Covers training data lawfulness evaluation, model risk assessment, automated decision triggers, and AI-specific DPIA methodology. Keywords: AI DPIA, machine learning impact assessment, EDPB AI guidelines, model risk, training data.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use when the user wants full metadata for a paper — from a DOI, PMID, arXiv id, OpenAlex id, or title. Returns title, author list, first author, corresponding author(s), publication date, journal name + ISO-4 abbreviation, impact factor, volume/issue/pages, DOI/PMID, citation count, and abstract in one record. Triggers on "paper metadata", "who is the corresponding author", "first author of", "what journal / impact factor for this DOI/PMID", "cite this paper", "文献元数据", "通讯作者", "第一作者", "影响因子". PROACTIVELY USE when the user pastes a DOI/PMID/arXiv id or paper title and asks about its authors, venue, or impact.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
diff-time で「影響範囲を repo 全体で調査した証拠」「失敗系を検証した証拠」「外部依存・レート制限・キャッシュ整合を確認した証拠」の欠落を検出する evidence-sufficiency 観点。defect そのものは既存 skill へ委譲し、本 skill は「そのリスク種別を調査した証拠が差分・PR 本文・テストに残っているか」の meta 評価のみを行う。証拠が同一 diff に同梱（テスト・canary・grep 記録）されていれば充足とみなす
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
[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.
The English summary is being prepared. Showing the original description.
Collect OpenClaw pull requests, proposed code changes, and issues shared in a specified conversation and time window. Recheck them on GitHub, assess impact and readiness, and return a prioritized queue with evidence and coverage gaps.
Find remotely reachable security flaws in repository code and assess whether they warrant a vulnerability report. The workflow checks scope, traces attacker-controlled input, confirms impact with a minimal proof of concept, and structures findings for disclosure.
Turn unclear feature requests or high-impact changes into acceptance criteria: observable conditions for judging completion. Define scope, assumptions, risks, and verification methods, or review an existing specification so another agent or team can implement it with clearer requirements.
Handle customer billing issues with connected tools such as Stripe. Review subscriptions and invoices, classify the problem, address refunds or cancellations, and prepare a handoff with revenue impact, customer follow-up text, and product gaps.
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.
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.
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.
Draft and publish English and Chinese notes for an existing Mole release. Organize changes by their impact on users, identify contributors from the release history, and update the release with approved notes, acknowledgments, and reactions.