'reporting' 검색 결과

Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.

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

METAINFORMANT rules for directory src/metainformant/gwas/reporting. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.

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

Produces marketing performance reports and data-driven recommendations from WooCommerce sales data, social media metrics, and campaign analytics. Use when the task asks for "campaign performance", "ROI analysis", "monthly report", "sales trends", "product velocity", "audience insights", or "KPI tracking". Covers metric definition, reporting templates, slow-mover detection, and insight-to-action frameworks.

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

Client reporting, quality assurance, and financial operations management. Handles KPI frameworks, compliance audits, budget tracking, and launch checklists. Use when: managing client dashboards, ensuring brand compliance, conducting QA reviews, tracking marketing spend, ensuring GDPR/CAN-SPAM compliance, proofreading deliverables. Also triggers on: client reporting, QA, quality assurance, brand compliance, marketing budget, financial tracking, legal compliance, GDPR, CAN-SPAM, proofreading, launch checklist

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

Audit cross-platform attribution, conversion definitions, reporting windows, GA4, AdServices and AdAttributionKit, MMPs, browser and server events, offline conversions, and platform reconciliation. Use for attribution audit, attribution models, conversion windows, requests to add or total Meta and Google conversions, incompatible reporting-window aggregation, GA4 attribution, MMP review, AppsFlyer, Adjust, Branch, Singular, or cross-platform discrepancies.

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

Designs and reviews production observability for mobile apps on every stack — Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers crash and error reporting with usable context, breadcrumbs, structured logs, traces and custom metrics, release and cohort segmentation, correlation with backend requests, alerting thresholds, sampling and cost, and what must never be collected. Use when production problems cannot be explained from the available data, when setting up crash reporting or telemetry, or when defining release health alerts.

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

Data Analyst IA — Expert en analyse de données (SQL, BI dashboards, Metabase, Superset, reporting, KPIs)

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

Expert en CRM avancé (HubSpot, Salesforce, pipeline, automation, reporting, contexte DZ, intégrations, data quality)

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

Expert en empreinte carbone (mesure, reporting, stratégies de réduction, crédits carbone, DZ)

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

ペネトレーションテストを対話的に実行するスキル。認可確認(Authorization Gate)→カテゴリ選択（Methodology, Reconnaissance, Scanning, VulnerabilityScanning, WebAppTesting, APITesting, PasswordAttacks, Exploitation, PrivilegeEscalation, ActiveDirectory, PostExploitation, WirelessAttacks, NetworkAttacks, SocialEngineering, CloudPentesting, MobileAppTesting, ContainerK8s, BinaryExploitation, OWASPTop10, Reporting, EmailSecurity, DatabaseAttacks, VPNRemoteAccess の全23カテゴリ）→ツール選択→コマンド実行→発見記録(Finding)→レポート生成をステップバイステップで進行。スコープ/除外チェック・ガードレール付き。「ペンテスト実行」「pentest」「侵入テスト」「脆弱性診断」「セキュリティテスト」「pentest executor」で発火。

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

Builds SOC performance metrics and KPI tracking dashboards measuring Mean Time to Detect (MTTD), Mean Time to Respond (MTTR), alert quality ratios, analyst productivity, and detection coverage using SIEM data. Use when SOC leadership needs operational visibility, continuous improvement tracking, or executive-level reporting on security operations effectiveness.

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

Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.

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

Validates predictive models on omics and biomedical data with nested cross-validation, group/batch/temporal-aware splits, the full data-leakage taxonomy, probability calibration, decision-curve net benefit, optimism correction, sample-size planning, and TRIPOD+AI reporting. Use when estimating model performance honestly, choosing a CV scheme, detecting leakage, or judging whether reported discrimination means the model is actually useful. For feature selection itself see machine-learning/biomarker-discovery; for confirmatory-trial inference see clinical-biostatistics/trial-reporting.

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

Guided statistical analysis with test selection and reporting. Use when you need help choosing appropriate tests for your data, assumption checking, power analysis, and APA-formatted results. Best for academic research reporting, test selection guidance. For implementing specific models programmatically use statsmodels.

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

Use this skill when the user asks about Environmental Health & Safety (EHS) for trucking — fuel spill response, hazmat release reporting, EPA + state environmental reporting, emergency contact information (CHEMTREC), environmental impairment liability insurance, and how to handle a CMV-related environmental incident. Cite 40 CFR + 49 CFR 174.6.

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

Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.

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

Builds SOC performance metrics and KPI tracking dashboards measuring Mean Time to Detect (MTTD), Mean Time to Respond (MTTR), alert quality ratios, analyst productivity, and detection coverage using SIEM data. Use when SOC leadership needs operational visibility, continuous improvement tracking, or executive-level reporting on security operations effectiveness.

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

Automatically categorizes test failures, suggests responsible owners, and provides common fix checklists. Generates actionable test reports with failure analysis. Use for "test reporting", "failure triage", "test analysis", or "test automation".

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

Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC discipline including attribution avoidance and indicator management, EDR and AMSI evasion techniques using direct syscalls and unhooking, data collection with chain-of-custody controls, and structured reporting with purple team debrief workflows. Covers assumed-breach, external-to-internal, insider threat, and hybrid physical-cyber engagement scenarios with MITRE ATT&CK mapping throughout. Targets operators planning or executing adversary simulation engagements against mature defenders.

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

Cross-cutting methodology for the CVE-hunting pipeline (ported from find-cve-agent): when a bug is design-vs-real, false-positive avoidance, version checking before reporting, responsible disclosure norms, acceptance-rate expectations per vuln class, vulnerability chaining playbook, known false-positive patterns, maintainer-response patterns, secure-pattern reference (what NOT to flag), and a self-criticism checklist to run before claiming a finding. Use this alongside the cve-hunter/cve-exploiter/cve-validator agents and the /cve-hunt pipeline — load it whenever judging if a finding is real, worth reporting, or already fixed.

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

OpenClaw 테스트와 플러그인 검증의 시간 및 메모리 사용량을 측정하고 로딩과 시작 과정의 원인을 조사합니다. 검증 범위를 유지하며 개선 전후 수치를 비교합니다.

• 느린 테스트와 과도한 모듈 로딩 원인 조사
• 플러그인 검증 시간과 메모리 사용 절감
• 테스트 중 메모리 증가 조사

Parallels의 macOS 가상 환경에서 설치부터 Discord 메시지 전송, 호스트의 회신, 게스트의 읽기까지 검증하여 양방향 통신의 성공 여부를 확인합니다.

• 새 macOS 환경의 메시지 송수신 확인
• 업그레이드 후 양방향 통신 검증
• Discord 왕복 통신 실패 조사

운영자가 설정한 Team 서버의 업데이트를 지정된 Night Watch 담당자를 통해 조율합니다. 기존 업데이트 체계의 검증과 복구 결과를 확인하고 정식 승인까지 추적합니다.

• Team을 공식 main으로 업데이트합니다
• 실패하거나 연기된 업데이트를 조율합니다
• 데이터베이스 이전과 복구를 조율합니다

MCP 서버를 실행하지 않고 설정을 읽어 승인 후에도 다른 코드를 가져올 수 있는 참조를 확인합니다. npm, Python, Docker의 버전 지정을 분류합니다.

• 승인 전에 MCP 설정을 검토합니다
• latest 태그와 버전 범위를 확인합니다
• CI에 재현 가능한 설정 검사를 추가합니다