Skill UI

This comprehensive guide provides solutions for the most frequent errors encountered when using Clay for data enrichment, webhooks, and API integrations. It covers issues such as 422/404 webhooks, credit limits, data quality failures, and rate limiting, ensuring smooth data workflow management.

A comprehensive guide to diagnosing and resolving common technical issues encountered with the Granola application. Covers fixes for audio capture failures, transcription quality degradation, calendar syncing problems, and integration errors with platforms like Slack and Notion. Includes platform-specific troubleshooting steps for macOS and Windows users.

Control an open Obsidian vault from the CLI: read, create, append, search, manage metadata, run plugin/theme reloads, capture errors, and take diagnostics screenshots without leaving the terminal.

This tool gathers comprehensive diagnostic evidence from an Obsidian vault. It collects details such as app versions, installed plugins, appearance settings, file statistics, and console errors into a structured markdown report. Use it when troubleshooting persistent issues or preparing detailed bug reports for developer support.

A comprehensive runbook for managing and resolving common incidents within the TwinMind meeting AI platform. This guide covers failures such as transcription not starting, audio capture issues, syncing errors, and calendar disconnections. It provides API setup, code snippets, and detailed troubleshooting steps to ensure a stable, continuous meeting AI workflow.

Defines strict guidelines for creating and maintaining Excel financial models, covering zero formula errors, industry color coding, number formatting, documented assumptions, and mandatory use of Excel formulas to ensure accuracy and auditability before recalculation.

Forces a terse caveman-style voice in every reply: answer first, ceremony and filler removed, while all technical facts, code, paths, numbers and errors stay verbatim. Activate with /caveman or "be brief" to cut token cost without losing accuracy.

A comprehensive guide to diagnosing and fixing common technical and workflow errors encountered in the Finta fundraising CRM. It covers API status codes (400-502), data validation issues (e.g., duplicate investors, missing fields), and synchronization breakdowns for investors, pipelines, and emails. Essential for maintaining data integrity during fundraising operations.

This guide provides comprehensive technical guidance for performance tuning and automating workflows using TechSmith Snagit COM API and Camtasia. It details key considerations for robust scripting, including using PowerShell and Python interop, defining various input/output types (like desktop, window, clipboard, or file), and solving common errors (such as COM registration failures or permission issues). Use this skill when building complex, automated pipelines for screen capture and video editing.

A comprehensive final checklist guiding authors through the submission process for Agricultural Systems journals (AgSy) via Editorial Manager. It ensures compliance with detailed guidelines, covering abstract word limits, required declarations (CRediT, COI, Funding, AI), graphical abstract preparation, and data/code deposit. Use this guide as the last step before final submission to avoid common desk-rejection errors.

This tool provides a comprehensive pre-submission checklist tailored for submitting manuscripts to high-tier academic journals. It verifies adherence to complex guidelines, covering manuscript length, abstract structure, citation formats (footnotes and real references), data reproducibility requirements, and double-blind anonymity protocols. It helps authors catch technical errors and formatting inconsistencies before official submission.

This comprehensive guide details the critical steps authors must follow after their manuscript is accepted for publication in a major academic journal (e.g., CJC). It covers everything from signing copyright agreements and confirming author details to meticulous final layout checks, proper citation formatting (GB/T 7714), and strict rules for the proofreading stage. The focus is on ensuring the paper is delivered to print with zero errors, emphasizing that the stage is for correction, not substantive revision.