Skill UI

This skill details how to conduct comprehensive Operational Technology (OT) vulnerability assessments using platforms like Claroty xDome. It covers passive asset discovery, correlating vulnerabilities against CISA/ICS-CERT advisories, calculating risk scores, and prioritizing remediation based on operational impact and compliance standards (e.g., IEC 62443, NERC CIP). The provided workflow uses Python to manage asset inventory and vulnerability matching for highly regulated industrial environments.

This skill details implementing Software Composition Analysis (SCA) using Snyk. It helps security teams detect known vulnerabilities, check license compliance, and automate dependency remediation within CI/CD pipelines. Learn to integrate scanning into GitHub, GitLab, and Jenkins workflows, generate automated fix PRs, and continuously monitor deployed applications to safeguard the software supply chain.

Guides teams through designing, implementing, and evidencing SOC 2 Type II controls aligned with the AICPA Trust Services Criteria, covering scoping, control mapping, evidence collection, remediation, and audit collaboration for a six- to twelve-month examination.

This tool implements the Stakeholder-Specific Vulnerability Categorization (SSVC) framework, providing a structured decision-tree methodology for advanced vulnerability prioritization. It moves beyond traditional CVSS scoring by incorporating critical factors such as active exploitation status (CISA KEV), technical impact, automatability, and mission prevalence. It generates actionable remediation priorities (Track, Attend, Act) to guide security teams in managing risk and improving security program maturity.

This skill provides a comprehensive, structured workflow for diagnosing performance bottlenecks in SwiftUI applications. It guides users through a code-first review to detect common issues like invalidation storms, layout thrash, or heavy main-thread work. When code review is insufficient, it provides detailed guidance on collecting runtime evidence using Instruments, enabling precise root cause analysis and targeted remediation strategies.

Feishu plugin troubleshooting tool combining FAQ guidance with the /feishu doctor command to inspect permissions, API connectivity, app credentials, and user authorizations, then generate diagnostic reports and remediation steps.

Guides CentOS experts through RHEL-aligned diagnostics using systemctl, journalctl, dnf/yum plus SELinux/firewalld checks, offering remediation, validation, and rollback commands.

This guide outlines the process and mandatory structure for documenting defects found during an Oracle-to-PostgreSQL migration. It details how to write actionable bug reports, covering required elements like Severity, Root Cause, Scenario, and Solution. It emphasizes treating Oracle as the source of truth and handling data layer nuances (e.g., NULL vs. empty string) to ensure accurate defect tracking and remediation.

Guides Fedora experts through confirming release information, executing systemctl/journalctl/dnf diagnostics, applying SELinux-aware remediation, and documenting verification plus rollback steps for distro-specific issues.

A comprehensive guide for rapid incident response when Algolia search functionality fails. This runbook provides structured procedures for triage, differentiating between infrastructure outages and internal configuration errors (e.g., API keys, indexing failures). It includes severity classification, diagnosis steps, and code examples for immediate remediation, such as key rotation or implementing circuit breakers.

This powerful orchestrator automates the entire GitHub issue lifecycle. It fetches issues based on criteria (labels, milestones, assignees), spawns specialized sub-agents to implement necessary code fixes, and automatically opens Pull Requests (PRs). Furthermore, it monitors open PRs, addresses review comments, and manages the remediation process, streamlining the development workflow from issue tracking to merge.

This comprehensive runbook provides structured, step-by-step procedures for diagnosing and mitigating Webflow Data API integration failures. It guides teams through quick triage checks (status page, connectivity, rate limits) and offers specific remediation steps for common error types like Authentication (401/403), Rate Limiting (429), and Server Errors (500/502/503). Designed for rapid incident response, ensuring graceful degradation and postmortem documentation.