'reporting' 검색 결과

Expert CSRD (Corporate Sustainability Reporting Directive, EU 2022/2464) compliance advisor. Use this skill whenever a user asks about CSRD, European Sustainability Reporting Standards (ESRS), double materiality assessment, sustainability reporting obligations, ESG disclosure, CSRD scope and thresholds, value chain reporting, XBRL digital tagging, third-party assurance, CSRD gap assessments, CSRD implementation timelines, ESRS E1–E5 environmental standards, ESRS S1–S4 social standards, ESRS G1 governance, the 2026 Omnibus scope change (Directive (EU) 2026/470, 1,000+ employees) and revised/simplified ESRS (July 2026), CSRD vs GRI/TCFD/SASB alignment, or any EU corporate sustainability reporting question. Trigger even if the user only mentions "ESG reporting Europe", "sustainability disclosure EU", or "non-financial reporting".

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

Expert CSRD (Corporate Sustainability Reporting Directive, EU 2022/2464) compliance advisor. Use this skill whenever a user asks about CSRD, European Sustainability Reporting Standards (ESRS), double materiality assessment, sustainability reporting obligations, ESG disclosure, CSRD scope and thresholds, value chain reporting, XBRL digital tagging, third-party assurance, CSRD gap assessments, CSRD implementation timelines, ESRS E1–E5 environmental standards, ESRS S1–S4 social standards, ESRS G1 governance, CSRD vs GRI/TCFD/SASB alignment, or any EU corporate sustainability reporting question. Trigger even if the user only mentions "ESG reporting Europe", "sustainability disclosure EU", or "non-financial reporting".

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

Drafts an Adverse Event Reporting Policy compliant with 21 CFR 312.32 (IND safety reporting), 21 CFR 314.80 (postmarketing), and ICH E2A, with multi-jurisdictional overlays (EMA, PMDA, Health Canada). Covers seriousness/causality frameworks, expedited reporting timelines, roles, documentation standards, training mandates, and QA mechanisms. Use when drafting or updating an adverse event reporting policy, pharmacovigilance policy, AE/SAE reporting SOP, or safety reporting framework for a pharmaceutical company, CRO, biotech, or clinical research institution.

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

Set up an email reporting button and an automated security response workflow. Classify reported messages, extract attack indicators, remove confirmed phishing emails, and send feedback to the people who reported them.

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

• Deploying a phishing reporting button in Outlook
• Automating triage of a dedicated reporting mailbox
• Retracting confirmed phishing emails across inboxes

Runs the period-end close and produces reporting — close calendar, reconciliations, accruals, variance analysis, and reporting that gets read. Use this to shorten or stabilize a monthly close, design a close checklist, investigate a variance, structure management reporting, or work out why the numbers keep changing after close.

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

Stakeholder mapping, communication plan design, reporting hierarchy, and mid-matter comms updates. Use when setting up a new matter and needing to identify who needs what information, designing the communication rhythm, building reporting structures for multi-jurisdiction programmes, or updating the comms plan when the stakeholder landscape changes. Trigger on: 'stakeholder map', 'who needs to be kept informed', 'communication plan', 'reporting structure', 'who do we report to', 'how often do we meet', 'client wants more updates', 'new contact on the client side', 'build the comms plan', 'reporting hierarchy', 'HQ vs regions', 'who is the decision maker', 'comms rhythm', 'meeting cadence', 'status call schedule'.

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

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).

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

Implements data protection compliance for whistleblowing systems under EU Directive 2019/1937 and GDPR. Covers anonymous reporting channels, identity protection for whistleblowers and accused persons, retention limits, access restrictions, and retaliation prevention. Addresses national transpositions and DPA guidance. Keywords: whistleblower, Directive 2019/1937, anonymous reporting, identity protection, retaliation, retention, reporting channel.

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

Creates executive reporting and visualization from RoPA data including processing activity counts, risk heatmaps, compliance scores, trend analysis, and supervisory authority readiness indicators. Activate for RoPA dashboard, executive reporting, risk heatmap, compliance score, trend analysis, board reporting, KPI.

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

Audit whether a paper's EVALUATION DESIGN actually measures what it claims and whether its reporting is complete — the validity layer family D (experiment-forensics) cannot reach. Three patterns: train/test leakage means the reported score may not measure generalization (HP-EVAL-LEAKAGE — adopts the Kapoor & Narayanan 8-type / 3-category leakage taxonomy; the illegitimate-proxy / sampling-bias / pretraining-contamination subtypes hand off as needs_external_check, naming but NEVER running Oren-2023 exchangeability / Shi-2023 Min-K% / Golchin-2023 Time-Travel / BIG-bench canary); a load-bearing LLM judge is conflicted (same model/family as a compared system) or unvalidated (no human-agreement, no bias control) (HP-JUDGE-VALIDITY); a declared condition/metric is dropped or switched to favor the method, or 'best' is chosen with no held-out set (HP-SELECTIVE-REPORTING). Verdict-bearing at L0/L1 from the DESCRIBED protocol — NOT repo-gated like experiment-forensics; L2 only CONFIRMS against split/preprocessing/result files. A fresh cross-model reviewer (gpt-5.6-sol xhigh, read-only, fresh thread per pass) PROPOSES findings, each span-anchored to a ledger claim_id; tools/adjudicate_findings.py DECIDES the verdict. Leakage and under-reporting are usually HONEST methodological errors — every finding describes a discrepancy to CHECK, never an accusation. An LLM generating GROUND-TRUTH labels is HP-FAKE-GT (experiment-forensics) — routed there, not here. Emits eval-design-forensics.findings.json; computes NO verdict. Detect-only. Triggers: "eval design audit", "evaluation validity", "train/test leakage", "data leakage", "is the score measuring generalization", "LLM judge bias", "is the judge validated", "selective reporting", "cherry-picked results", "评估设计审计", "评测有效性", "数据泄漏", "训练测试集泄漏", "裁判模型有没有验证", "选择性报告".

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

Structures co-investment reporting with deal-level performance, fee/carry calculations, and co-invest program aggregate analysis. Use when reporting co-invest performance, tracking deal-level returns, or preparing co-invest summaries.

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

Draft and revise scientific manuscripts while linking claims to verified evidence. The skill organizes source records, checks consistency across text and results, tracks reporting requirements, and reviews references and disclosures, with human verification and final approval.

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

• Drafting manuscript sections from verified evidence
• Checking consistency across text, tables, and results
• Reviewing references and reporting checklist coverage

Prepare constructive review drafts for scientific manuscripts, protocols, preprints, and proposals. Organize checks of claims, evidence, methods, statistics, reproducibility, ethics, figures, and citations into specific comments that a responsible human reviewer can verify and revise.

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

• Draft evidence-based comments on a scientific manuscript
• Check methods, statistics, and reproducibility reporting
• Choose reporting guidelines and identify missing information

Explore public pathogen genome data to verify lineage names, summarize weekly sequence proportions, examine reporting delays, and compare mutation frequencies. Results include filters and denominators, with clear limits on what submitted sequences reveal about infections.

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

• Tracking weekly lineage proportions in submitted sequences
• Verifying current Pango lineage names
• Examining delays between sample collection and reporting

Review and improve statistical reporting in manuscript methods, results, and figure captions. It checks sample definitions, repeated measurements, tests, and uncertainty, then provides revised wording and identifies missing information or issues reviewers may raise.

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

• Reviewing a manuscript’s statistical methods section
• Checking sample sizes and repeated measurements
• Aligning figure captions with reported statistics

Plan and coordinate an authorized security assessment across reconnaissance, access testing, privilege escalation, and reporting. Route work to specialist skills, review each stage, and adjust the assessment path within the agreed scope.

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

• Planning an authorized penetration test
• Coordinating specialist assessment skills
• Evaluating the impact of linked vulnerabilities

Turns supplied AI agent evaluation results into reports that distinguish autonomous success, human-assisted success, failure, timeout, and invalid runs. Makes metric denominators, retries, timing, costs, and comparison conditions explicit to support evidence-based decisions.

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

• Separating autonomous and human-assisted success rates
• Reporting evaluations with retries and invalid runs
• Comparing agents or releases under matched conditions

Add clear runtime reporting to Python, PowerShell, or Node.js batch scripts. Design start messages, progress counts, item failures, and final summaries while preserving existing result output, error handling, and exit codes, then verify visibility during execution.

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

• Add progress reporting to long-running batch scripts
• Report individual failures and final outcome counts
• Keep progress logs separate from machine-readable results

Build a central vulnerability dashboard with DefectDojo to combine scanner findings, remove duplicates, and track remediation. Includes Docker deployment, automated scan imports from CI/CD pipelines, Jira ticket integration, and API queries for reporting metrics.

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

• Combining findings from multiple security scanners
• Importing scan results automatically from CI/CD pipelines
• Connecting vulnerability findings to Jira tickets

Find suitable grants and bidding opportunities, check eligibility before drafting, and prepare applications or responses to requests for proposals using past submissions and actual organizational data. It also tracks submission deadlines and reporting obligations after an award.

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

• Finding grants your organization qualifies for
• Screening solicitations before deciding to bid
• Drafting applications from past submissions

Turn Matomo analytics into reports on organic traffic, landing pages, devices, countries, referrers, and search keywords. Use data from a self-hosted instance or Matomo Cloud to support reporting alongside GA4 or as an alternative.

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

• Review organic traffic trends in Matomo
• Identify popular landing pages
• Compare visits by device, country, and referrer

Audit how advertising platforms, GA4, and app measurement tools assign credit for conversions. Compare event definitions, reporting windows, and duplicate handling to explain discrepancies and produce an evidence-based measurement improvement plan.

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

• Investigating discrepancies between Meta and Google conversions
• Checking GA4 against advertising platform reports
• Reviewing app conversion measurement

Checks biomedical manuscripts against reporting guidelines such as CONSORT, STROBE, PRISMA, and TRIPOD to identify missing or weak reporting elements before submission or revision.

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

Reconcile controlled-substance records and prepare for an inspection — the count against the register, the discrepancy investigation, the documentation an inspector asks for, and the reporting obligations a shortfall triggers. Use when asked to reconcile controlled drugs, prepare for a DEA or controlled-drug inspection, investigate a discrepancy or suspected diversion, or audit the CD register. Produces the reconciliation, the discrepancy investigation record, the inspection-readiness checklist, and the escalation and reporting decision tree. A process framework only; reporting thresholds, timelines and obligations are set by law in your jurisdiction and must be verified there.

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