Skill UI

This skill provides comprehensive strategies for managing API rate limits and webhooks within the Clay platform. It addresses webhook throttling, plan-level rate limits (hourly/per-second), and webhook submission exhaustion (50K limit). Use this when integrating with Clay to ensure reliable, optimized data throughput and handle 429 errors gracefully with backoff strategies.

This module provides a compliance-grade, tamper-evident logging solution for tracking all Kling AI operations. It records task submissions, status changes, and credential usage into structured, hashed logs. Use this when meeting regulatory compliance requirements or preparing for internal/external security audits.

This comprehensive checklist guides developers through the pre-release verification process for Obsidian community plugins. It covers critical technical areas such as validating manifest structure, ensuring clean production builds (e.g., removing sourcemaps), identifying potential memory leaks, and verifying cross-platform readiness, ensuring a high-quality user experience upon submission.

Provides Playwright-powered browser automation that detects dev servers, writes tests to /tmp, launches a visible Chromium, and exercises login flows, responsive layouts, form submissions, link checks, or any browser task to validate web functionality.

Guides building Next.js Server Actions for App Router forms, mutations, and optimistic updates, covering useFormState/useFormStatus hooks, revalidation helpers, and post-submission redirects.

Guided workflow for turning PM notes or rough drafts into compliant repo skills, covering draft generation, validation checks, README updates, and optional packaging so every submission passes the repo standards.

This skill helps users create a new Git branch that strictly adheres to established project naming conventions (e.g., Sentry standards). It automatically determines the appropriate branch type (such as `feat`, `fix`, `chore`, etc.) and generates a descriptive, standardized branch name by analyzing the provided work description or local code differences (diff). It guides the entire branching workflow, ensuring proper lineage and classification for code submissions.

Use this guide to build and manage Expo development clients using EAS Build. This is the recommended setup for production-grade testing, allowing developers to test custom native code, local modules, and advanced features that exceed Expo Go's capabilities. It covers local builds, TestFlight submission, and connecting to the Metro bundler.

This skill fetches unread GitHub Pull Requests (PRs) that require review from a specified team or were opened by a team member. It is ideal for users who need to check their team's review queue, find PRs needing attention, or automate the process of reviewing open code submissions without manually browsing GitHub notifications. Requires GitHub CLI authentication.

Proof Of Vulnerability streamlines the creation and submission of evidence that a security flaw can be exploited, ensuring teams can quickly validate issues and coordinate fixes with a reproducible discovery narrative.

This comprehensive tool validates Claude Code plugins against official Anthropic specifications and internal enterprise standards. It performs two main types of checks: structural validation (checking `plugin.json` fields, file references, and permissions) and content validation (conducting deep grading using `SKILL.md`). Use this when building, auditing, or preparing plugins for marketplace submission to ensure compliance and quality.

Builds a comprehensive, automated pipeline for malware submission and analysis. It collects suspicious files from multiple sources (EDR, email gateways), automatically submits them to sandbox environments and multi-engine scanners, and generates detailed verdicts and Indicators of Compromise (IOCs). Essential for SOC teams needing to scale high-volume malware triage and incident response.