Skill UI

A specialized skill designed to assist in drafting professional and structured internal communications. It provides guidelines and formats for various corporate documents, including 3P updates (Progress, Plans, Problems), company newsletters, status reports, FAQ responses, and incident reports. Use this skill to ensure consistency in tone and structure across all internal messaging.

This comprehensive guide addresses common technical and business logic errors encountered when integrating with the Juicebox API. It covers HTTP status codes (e.g., 401, 403, 429), including authentication failures, quota exhaustion, rate limiting, data validation issues, and analysis timeouts. The resource provides detailed causes, specific fixes, and best practices for building reliable and robust integrations into recruiting and research workflows.

This bundle collects comprehensive diagnostic evidence from the Juicebox platform. It gathers API connectivity status, dataset health reports, analysis quota usage, and rate limit information into a single archive. Use it to systematically troubleshoot complex issues such as failed dataset uploads, stalled AI analysis runs, API authentication failures, or quota exhaustion.

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 tool provides comprehensive Python solutions for processing batches of text-to-video requests using the Kling AI API. It handles controlled parallelism, rate-limiting, and detailed status tracking. Use this when building robust content pipelines that require generating multiple videos efficiently from a list of prompts, supporting synchronous, asynchronous, and webhook callback methods.

This guide provides a comprehensive reference for diagnosing and resolving common errors encountered when interacting with the Kling AI API. It covers various HTTP status codes (e.g., 400, 401, 429), task-level failures (e.g., content policy violations, low image quality), proper JWT token management, and implementing rate limit handling with exponential backoff. Use this resource when troubleshooting failed video generation or API integration issues.

A comprehensive guide for developers on utilizing the Kling AI Text-to-Video REST API. This skill provides minimal working examples in Python and Node.js, demonstrating the complete workflow: submitting a text prompt, polling the task status, and retrieving the final generated video URL. Ideal for integrating advanced AI video generation capabilities into development projects.

This guide details how to implement webhooks for Kling AI video generation tasks. Instead of inefficiently polling the API status, you can provide a callback URL when submitting a task. When the task completes (whether successful or failed), Kling AI will automatically send a POST request containing the full result to your designated endpoint. This mechanism eliminates polling overhead and is essential for building robust, event-driven video processing pipelines.

This bundle collects comprehensive diagnostic evidence for Langfuse support tickets and troubleshooting. It gathers system environment details (Node.js, Python, OS), installed SDK versions, API connectivity status, and redacted application logs. Use this when encountering persistent or complex Langfuse issues to provide full context to support teams.

This skill provides a comprehensive command-line interface (CLI) for managing issues, projects, and teams within the Linear platform. Users can create, update, and track the status of issues, set project phases (e.g., backlog, in-progress), and manage complex workflows directly from the terminal, ensuring better traceability and project organization.

This skill integrates Continuous Integration/Continuous Deployment (CI/CD) pipelines with Linear issue tracking. It automatically detects deployment URLs (e.g., Vercel, Railway), adds detailed deployment comments to relevant Linear issues, and manages state transitions (e.g., moving an issue to 'Review' or 'Done') based on the deployment environment (staging or production). It ensures a seamless link between code commits, deployment status, and project management tickets.

Provides a deep dive into migrating issue tracking data from major platforms like Jira, Asana, and GitHub to Linear. This guide covers the entire lifecycle, including initial workflow assessment, status and priority mapping, data export utilizing API examples, and detailed transformation logic required to ensure data integrity and smooth adoption within Linear.