Skill UI

A standardized, multi-phase workflow designed for initiating large-scale, complex software tasks (e.g., migration, overhaul, refactoring). This process ensures that all necessary planning, project analysis, risk assessment, and task decomposition are completed *before* any actual coding begins. It guides users through intent confirmation, deep codebase analysis, and creating a detailed, trackable development plan.

AgentPhone exposes a telephony-first API that lets you provision phone numbers, configure webhooks or hosted voice mode, and run AI agents that make calls, send SMS, and inspect transcripts.

Feishu plugin troubleshooting tool combining FAQ guidance with the /feishu doctor command to inspect permissions, API connectivity, app credentials, and user authorizations, then generate diagnostic reports and remediation steps.

Automates Feishu doc edits with seven modes (append, overwrite, replace_range, replace_all, insert_before/after, delete_range) plus optional title sync, letting teams tweak specific sections without rebuilding entire files.

Designs emotionally paced email nurture and multi-touch flows that build curiosity, reciprocity, and commitment before the ask, ensuring each touchpoint prepares the next for respectful conversion.

Diagnoses the specific psychological obstacles that make audiences skeptical of a brand or offer and prescribes precisely timed credibility signals so messaging lands confidently without overclaiming.

Structured workflow that has an AI agent capture failures, diagnose root causes, apply minimal recovery steps, and report introspection to avoid repeat loops or context drift.

Classify ECC skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets by using repo-specific evidence so the install surface matches only the components a project actually needs.

This skill guides the construction of new API connectors or providers by strictly adhering to the host repository's established integration patterns. It is specifically designed for scenarios where a new integration surface is needed, rather than just using a generic HTTP client. Key considerations include matching the connector layout, configuration schema, authentication model, error handling, testing style, and registry wiring to ensure the new component feels native to the codebase.

Provides a HIPAA-specific entrypoint covering PHI handling, BAAs, auditability, and escalation steps for US healthcare software so requests explicitly invoking HIPAA trigger the right compliance review and guardrails.

Guides ECC agents through live message retrieval, inspection, and code recovery workflows while ensuring the exact messaging surface, thread, and status are documented before replying or proving a source.

Structured evidence-first workflow for repository work: run commands, inspect git state, debug CI or builds, apply narrow fixes, and document exact verification steps when the user demands proof of execution.