「event」の検索結果

Use when recovery planning requires verification that backups are restorable, complete, and safe to trust before an incident or recovery event.

日本語の概要は準備中です。原文の説明を表示しています。

Systematically remove malware, backdoors, and attacker persistence mechanisms from infected systems while ensuring complete eradication and preventing re-infection.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the work needs analytics architecture, event planning, KPI design, attribution boundaries, or instrumentation review across product and growth.

日本語の概要は準備中です。原文の説明を表示しています。

Route Microsoft Graph work from VS Code. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.

日本語の概要は準備中です。原文の説明を表示しています。

Instrument and post-process PFC 5.0 asphalt damage studies using bond-break hits, clustered AE events, macro energy density, source fields, stage summaries, and auditable CSV outputs.

日本語の概要は準備中です。原文の説明を表示しています。

"Apply the Efficient Market Hypothesis (Fama, 1970) to evaluate information incorporation in asset prices across weak, semi-strong, and strong forms. Use this skill when the user needs to assess market efficiency, determine if a trading strategy can generate abnormal returns, evaluate event studies, or when they ask 'can technical analysis work', 'does the market already know this', or 'is this anomaly exploitable'.".

日本語の概要は準備中です。原文の説明を表示しています。

"Apply Bhaskar's critical realism to analyze phenomena through three ontological domains (real, actual, empirical), identify generative causal mechanisms via retroduction, and examine structure-agency interplay. Use this skill when the user needs to go beyond surface correlations to underlying causes, design research that distinguishes mechanisms from events from experiences, or when they ask 'what causes this beyond the observed pattern', 'what structures enable or constrain this behavior', or 'how do I move from correlation to causal explanation'.".

日本語の概要は準備中です。原文の説明を表示しています。

"Analyze inventory health using turnover ratios, ABC classification, safety stock calculations, and stockout vs overstock diagnostics. Use this skill when the user needs to optimize inventory levels, reduce carrying costs, prevent stockouts, or classify products by inventory priority — even if they say 'we have too much stock', 'we keep running out of bestsellers', 'how much safety stock do we need', or 'which products should we focus on'.".

日本語の概要は準備中です。原文の説明を表示しています。

"Calculate safety stock levels to buffer against demand and lead time uncertainty. Use this skill when the user needs to set inventory buffers, determine service level trade-offs, or optimize safety stock across SKUs — even if they say 'how much buffer inventory', 'stockout prevention', or 'service level calculation'.".

日本語の概要は準備中です。原文の説明を表示しています。

Plan, build, scaffold, or safely extend Atlassian Forge apps using current official documentation. Use for fresh Forge apps, existing-app feature work, module and manifest changes, UI Kit or Custom UI implementation, backend functions and events, Atlassian or external APIs, storage, permissions, environment configuration, distribution-affecting implementation, validation, and explicitly authorized deployment or installation; route standalone debugging and specialist reviews to their dedicated skills.

日本語の概要は準備中です。原文の説明を表示しています。

Facilitate SAFe 6.0 PI Planning events. Structure the 2-day cadence, generate PI Objectives with Business Value scores, build the Program Board for dependency visualization, and run the Confidence Vote. Use before every Program Increment when the organization follows SAFe.

日本語の概要は準備中です。原文の説明を表示しています。

Draft crisis communication packages including holding statements, stakeholder updates, Q&A documents, and internal briefs. Follows ICS (Incident Command System) communication principles. Use during PR crises, data breaches, product recalls, or any event requiring rapid coordinated messaging.

日本語の概要は準備中です。原文の説明を表示しています。

Write blameless incident postmortems following Google SRE methodology. Covers timeline reconstruction, root cause analysis (5 Whys), impact assessment, and action items with owners. Use after production incidents, outages, or significant bugs to prevent recurrence.

日本語の概要は準備中です。原文の説明を表示しています。

Security Operations Center skill for alert triage, detection engineering, incident response, log analysis, threat hunting, SIEM queries, EDR investigation, timeline building, IOC handling, escalation notes, containment recommendations, and analyst-ready reporting. Use for blue-team operations, suspicious event analysis, and defensive cybersecurity workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Perform forensic analysis of the macOS Unified Logging System (ULS) to investigate system events, application crashes, kernel panics, and potential indicators of compromise (IoCs) such as persistence mechanisms or unauthorized access.

日本語の概要は準備中です。原文の説明を表示しています。

Detects insecure platform interaction in mobile apps (Android/iOS). Trigger on: exported Activity, exported Service, exported BroadcastReceiver, Content Provider, Intent injection, deep link hijacking, WebView JavaScript enabled, JavascriptInterface, addJavascriptInterface, setJavaScriptEnabled, intent:// scheme, file:// scheme, WKWebView, WKScriptMessageHandler, UIPasteboard, URL scheme hijacking, Universal Links, PendingIntent, FLAG_IMMUTABLE, overlay attack, tapjacking, screenshot prevention, FLAG_SECURE, Broadcast sniffing, IPC data exposure. Covers MASVS-PLATFORM-1/2/3.

日本語の概要は準備中です。原文の説明を表示しています。

Test organizational egress controls by executing various data exfiltration techniques during a red team engagement. Use this skill to simulate an adversary attempting to steal sensitive data without triggering DLP (Data Loss Prevention) or network monitoring alerts. Covers exfiltration over DNS, ICMP, HTTP/S, alternative protocols (SSH/FTP), cloud services, and physical methods.

日本語の概要は準備中です。原文の説明を表示しています。

Dangling markup injection playbook. Use when HTML injection is possible but JavaScript execution is blocked (CSP, sanitizer strips event handlers, WAF blocks script tags) — exfiltrate CSRF tokens, session data, and page content by injecting unclosed HTML tags that capture subsequent page content.

日本語の概要は準備中です。原文の説明を表示しています。

Test horizontal and vertical authorization bypass via session ID swapping between accounts, IDOR through parameter manipulation (invoice=, user=, menuitem=, EventID=), and special header injection (X-Original-URL, X-Rewrite-URL, X-Forwarded-For, X-Remote-IP, X-Client-IP with 127.0.0.1/localhost/RFC1918 values). Tools: Burp Suite with Autorize/AuthMatrix extensions, OWASP ZAP Access Control Testing add-on.

日本語の概要は準備中です。原文の説明を表示しています。

Prevent common AI report pitfalls — bug blending, inflated threat models, and generic language. Train Claude with your best past reports for concise, technical submissions. Based on Critical Thinking Bug Bounty Podcast Episode 166.

日本語の概要は準備中です。原文の説明を表示しています。

Use when building 2D games in Python with pygame - game loop and delta time, sprites and groups, collision detection, drawing and surfaces, events and input, sound and fonts, camera, or performance optimization

日本語の概要は準備中です。原文の説明を表示しています。

Use when building terminal user interfaces in Rust with the ratatui crate - layout system, widget usage, input/event handling, app state architecture, TUI testing, or migrating between ratatui 0.29 and 0.30

日本語の概要は準備中です。原文の説明を表示しています。

Use when developing OpenRCT2 plugins in TypeScript - plugin registration and game actions, window and widget UI, event hooks, park, map, ride and entity access, network API, storage, or ES5 runtime constraints

日本語の概要は準備中です。原文の説明を表示しています。

Full instrumentation from day one. PostHog consolidates product analytics + feature flags + error tracking (one platform, one bill). GA4 via GTM (14-step automation, custom dimensions over events, server-side tagging). Sentry (deep error tracking + performance). Stripe (webhook-first with idempotent processing). Listmonk on Coolify (newsletters via Amazon SES SMTP relay). PLG 7-layer framework. Programmatic SEO (5 page types). Incident auto-remediation via Sentry→Inngest pipeline. AI search (GEO) awareness. Local business conversions (phone_click, direction_click, form_submit, booking_click) with CRO patterns for both SaaS and local.

日本語の概要は準備中です。原文の説明を表示しています。