Skill UI

This meta-skill is designed to automate the diagnosis of complex programming errors. When presented with a stack trace, traceback, or failing log, it orchestrates a multi-step investigation. It parses the trace, searches the repository history, checks relevant issues, and analyzes code diffs to provide a comprehensive brief for root cause analysis and debugging.

A comprehensive guide detailing the structured process for responding to phishing incidents. It covers email header analysis, malicious content sandboxing (URLs/attachments), scoping the impact across the organization, and performing thorough remediation, including mailbox purging and credential reset.

Plaso (log2timeline) is an open-source engine used to generate forensic super-timelines. This skill guides the process of normalizing hundreds of diverse artifact types—including MACB times, registry keys, EVTX logs, and browser history—into a single, cohesive chronological view. The workflow covers extraction, filtering, and importing the timeline into Timesketch for collaborative analysis, which is crucial for incident response, correlating complex activity chains, and detecting anti-forensic techniques like timestomping.

A comprehensive, four-phase methodology for debugging complex software issues. It guides users through root cause investigation, pattern analysis, hypothesis testing, and controlled implementation. The core principle emphasizes finding the underlying cause rather than applying quick, symptomatic fixes, ensuring robust and reliable code improvements across various failure scenarios.

This sophisticated skill is designed to locate the root cause of a confirmed software failure. It performs a systematic, semi-formal tracing process: first tracing backward from the observed failure point (using provided stack traces, assertions, or error messages) to identify the original premise, and then tracing forward to confirm the symptom. It outputs a highly structured report detailing the divergence, premises, and remedy.

This tool detects and flags Personally Identifiable Information (PII) across text, code, and configuration files. It is essential to use this before committing code, writing logs, or generating model responses to prevent accidental exposure of sensitive data. It identifies various types of PII, including emails, phone numbers, SSNs, credit card numbers, API keys, and passwords, offering quick checks, detailed scans, and full context-aware analysis.