Skill UI

This skill analyzes Active Directory (AD) Access Control Lists (ACLs) to detect dangerous misconfigurations. It uses the ldap3 Python library to query domain controllers, parse security descriptors (SDDL), and identify instances where non-privileged users or groups are granted dangerous permissions like GenericAll, WriteDACL, or WriteOwner on sensitive objects. Essential for security incident response and privilege escalation path discovery.

This skill utilizes the Microsoft Graph API to parse Office 365 Unified Audit Logs for security incident investigation. It is designed to detect critical indicators of account compromise, including the creation of suspicious email forwarding rules, unauthorized mailbox delegation changes, suspicious OAuth application consent grants, and other signs related to Business Email Compromise (BEC).

A comprehensive guide to configuring secure OAuth 2.0 authorization flows, covering best practices for Authorization Code with PKCE, Client Credentials, and Device Authorization Grant. Learn how to implement mandatory security controls, manage token lifecycles, and align with OAuth 2.1 standards to build robust identity and access management systems.

This skill analyzes Azure AD/Microsoft Entra ID environments to detect illicit OAuth application consent grants. It leverages the Microsoft Graph API and directory audit logs to enumerate permissions, identify overly broad scopes, and flag high-risk applications based on publisher verification status. It is essential for SOC analysts and threat hunters investigating cloud identity security incidents.

This skill guides the implementation of Just-In-Time (JIT) access provisioning, eliminating standing privileges by granting temporary, time-bound access. It covers designing robust approval workflows, integrating with PAM/IGA systems, automating revocation, and adhering to Zero Trust principles, significantly reducing the attack surface.

Enforces explicit user approval before running any delete command so file removals only proceed after permission is granted.

This comprehensive skill guide provides deep insight into Oracle Cloud Infrastructure (OCI) IAM policy syntax and best practices. It covers the privilege verb hierarchy (inspect, read, use, manage), the correct structure for policy statements, and common patterns for granting least-privilege access across various compartments. Use this when developing automation scripts, setting up complex access control policies, or performing security audits in OCI.

This guide outlines essential security best practices for managing and protecting your SerpApi API key. Since the key grants full account access, developers must never expose it in client-side code. It details how to implement secure backend proxies, manage environment variables using secret managers, set up rate limiting to prevent abuse, and monitor usage patterns in production environments.

The Desktop Commander MCP grants agents deep reach across the user's entire operating environment, extending far beyond the typical IDE sandbox. Key capabilities include maintaining persistent shell sessions, managing long-running background processes, accessing arbitrary filesystems, and natively handling structured data formats (Excel, PDF, DOCX). It also enables remote operations via SSH and large-scale content search, making it ideal for complex, multi-turn development, DevOps, and data analysis workflows.

This skill mints tamper-evident, post-quantum-signed receipts for consequential agent actions (e.g., deployment, payment, access grant). It records who, what, and under which policy the action occurred, ensuring the evidence cannot be altered later. By providing verifiable proof from the certificate alone, it is crucial for meeting regulatory compliance requirements, such as the EU AI Act, and building auditable, trustworthy systems.

This comprehensive guide provides a detailed audit checklist for submitting research papers to the PPoPP conference. It covers crucial academic requirements, including adherence to the two-column ACM format, strict page limits, abstract guidelines, and maintaining double-blind anonymity by scrubbing identifying information (e.g., cluster names, grant numbers). Use this checklist before final submission to avoid desk-rejection.