Skill UI

This utility automatically collects comprehensive diagnostic data for the Granola application, including system specifications, audio configurations, network connectivity tests, and application metadata. It packages all findings into a single ZIP file for support teams. Use this when preparing a detailed support ticket or troubleshooting complex, persistent issues. The process is designed to collect diagnostic context without exposing sensitive meeting content, transcripts, or private API keys.

This skill collects a comprehensive debug bundle from the Instantly workspace. It gathers critical metrics including campaign state, account health, warmup analytics, webhooks, and background job status. The resulting structured JSON report is ideal for creating detailed support tickets, performing technical troubleshooting, or conducting internal system audits.

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.

Prepare journal manuscripts, conference papers, posters, and grant documents with venue-specific formatting guidance, verification-first rules, and bundled LaTeX scaffolds.

Builds court-facing litigation chronologies from disclosure bundles, witness statements, and matter files. Applies CPR 31.22 implied-undertaking check, privilege screen, and case-theory significance tagging. Use for UK civil litigation to generate working or Statement-of-Facts timelines.

Routing guide for Cherry Studio's first-party MCP tools: knowledge bases, memory, schedules, sessions, skills, MCP servers, web search, and bundled bun/uv/rg runtimes. Read it before attempting shell workarounds.

Investigate what went wrong in a Superpowers session and report findings with hard evidence. Reads on-disk transcripts to trace skill timelines, plan adherence, repeated work, stumbles and cost, then drafts an evidence-backed report, an optional GitHub issue, or a sanitized bundle for maintainers.