Skill UI

This skill systematically audits Playwright End-to-End (E2E) test files. It checks for common anti-patterns, adherence to best practices, and identifies coverage gaps across the entire test suite. It provides a detailed score (1-10) and generates actionable reports, including suggested code fixes, significantly improving test reliability and maintainability.

Analyze binaries with radare2/r2 from the command line, including reverse engineering, disassembly, function analysis, imports/strings inspection, patching, binary diffing, hex inspection, and r2 scripting. Supports PE/ELF/Mach-O/DEX/WASM files and sub-tools like rabin2, rasm2, radiff2, and r2pipe.

Use this skill to formally report bugs, file issues, or submit problems encountered with the canvas-apps plugin. It facilitates the submission of detailed bug reports directly to the associated GitHub repository, helping developers track and resolve technical problems.

This utility provides fundamental text processing capabilities, including detailed word and character counting, frequency analysis, and various text transformations (e.g., uppercase, title case). It is designed for analyzing documents and batch processing files, supporting output in both JSON and human-readable formats.

Provides comprehensive architectural guidance for implementing robust, crash-safe, and versioned save/load systems for games. Covers serialization best practices, atomic file writing, schema migration, and autosave implementation, ensuring player progress persists reliably across updates and crashes.

This skill guides the user through the manual process of linking a Power Apps Wrap mobile application to an existing Entra ID application registration. It resolves the necessary environment and tenant IDs, and then updates the local auth.config.json file with the captured Client ID, enabling the application's authentication against a specified Entra ID tenant.

A comprehensive skill to configure authentication (login/logout) and role-based authorization for Power Pages code sites. It supports multiple identity providers (Microsoft Entra ID, Okta, Google, Facebook, etc.) and handles framework-appropriate patterns, generating necessary service files, utilities, and UI components.

This skill provides an end-to-end wizard for creating a Dataverse Mobile Offline Profile, enabling Power Apps to function in an offline environment. It meticulously designs per-table row scopes, manages relationships, and defines column synchronization frequency through a multi-gate approval flow. It creates necessary Dataverse entities and configures the full app-level offline metadata, ensuring seamless offline data access for native mobile clients (iOS/Android).

This skill automates the setup of continuous integration and continuous deployment (CI/CD) pipelines specifically for Power Pages solutions within the Power Platform. It creates pipeline configurations natively in Dataverse, eliminating the need for external YAML files or separate CI/CD infrastructure. It guides users through the Application Lifecycle Management (ALM) process, ensuring structured, automated deployment from development stages to production.

This skill analyzes raw project descriptions or site requirements and synthesizes a comprehensive, structured project constitution into a SITE.md file. Acting as the project's central source of truth, it defines core identity, visual guidelines, architectural structure, sitemap, and prioritized development roadmap, ensuring scope alignment throughout the build lifecycle.

Restructure oversized single-file SKILL.md or scattered project rules into a well-organized Skill directory with progressive rigor, routing, validation, and drift-resistant maintenance for AI agent harnesses.

This skill automates the final deployment phase of an agent system. It converts a validated build sheet into four ordered JSON payloads (environment, agent, session, kickoff) and generates a resumable `launch.sh` script. Crucially, this process enforces API-key safety by requiring the user to run the script in their shell, pulling the Anthropic API key from the environment variable, thus ensuring the key never appears in logs or files. It provides a structured, multi-step launch sequence.