Skill UI

This skill audits and repairs repository hygiene across artifacts, dependencies, CI, docs, Git state, and code-quality signals. It is used for repository maintenance, cleanup, health checks, or pre-release hardening. It ensures repository health through authorized repairs and protected workflows, validating changes before publishing via pull requests to maintain security and stability.

This skill creates custom Semgrep rules for detecting security vulnerabilities, bug patterns, and code patterns. It guides users through a strict workflow including test-first development, AST analysis, and validation. Ideal for building static analysis detections, enforcing coding standards, and identifying data flow issues using taint mode.

Scan agent skills for security issues before adoption. Detects prompt injection, malicious code, excessive permissions, secret exposure, and supply chain risks. Provides static analysis and manual review workflow.

Audit an Agent Skill, MCP server, connector, or desktop extension before installation by tracing code, dependencies, permissions, credentials, data flow, and irreversible actions.

This tool automates complex Git workflows to save time and reduce manual overhead. It intelligently detects and groups related code changes, automatically generates descriptive branch names (e.g., fix/auth-bug), and streamlines the entire cycle: staging, committing, pushing, and creating Pull Requests (PRs). Use it to maintain clean, consistent commit histories efficiently.

This skill guides the mastery of smart contract security best practices for Solidity. It is essential for writing robust, secure, and efficient contracts, auditing existing code for common vulnerabilities (such as reentrancy, overflow, and access control issues), and implementing secure DeFi protocols. It focuses on preventing common attack vectors while optimizing gas usage.

Squirrel is an advanced, full-cycle AI coding skill designed to guide software development from concept to production. It automatically detects the current project state (greenfield, in-progress, or mature) and adapts an 8-phase engineering pipeline. This comprehensive workflow covers planning, building, rigorous testing, bug hunting, code polishing, documentation, and deployment readiness, ensuring high-quality, maintainable results.

Implement and verify Stripe checkout, subscriptions, webhooks, and refunds with explicit server-side authorization. Covers payment flows, webhook handling, subscription management, and customer management. Provides code patterns for hosted checkout, payment intents, and setup intents. Emphasizes security boundaries and proper use of test accounts.

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.

A comprehensive guide detailing how to refactor large, complex SwiftUI views into smaller, more stable, and explicit components. It emphasizes adopting a lightweight state approach (favoring local state and environment variables over excessive view model layers) to improve data flow, readability, and overall code maintainability in modern iOS development.

This skill acts as an alias for the canonical TDD workflow cycle. It assists developers in implementing Test-Driven Development methodologies by structuring testing cycles and ensuring quality assurance. Use it when working on software development tasks requiring a test-first approach. It redirects to the full TDD cycle implementation for detailed guidance on writing tests before code.

This skill focuses on the 'Green Phase' of Test-Driven Development (TDD). It involves writing the minimal amount of code required to make failing tests pass. It emphasizes simplicity and avoiding premature optimization or architectural changes. Use this when moving from red to green status in your test cycle.