Total 50,315 skills
Showing 12 of 50315 skills
Manage note tags in Get笔记 via the getnote CLI
Integrate CometChat into any app. Auto-detects your platform and framework, then walks you through picking and applying a chat experience. Start here — do not invoke platform-specific skills directly. Trigger with "/cometchat", "integrate cometchat", or "add chat to my app".
Use when you have an approved implementation plan document and need to execute it step by step. Triggers on /execute command, when transitioning from planning with an approved plan, or when resuming execution of a partially completed plan. Provides batch-based execution with TDD, checkpoint reviews, and verification gates.
Clay integration. Manage data, records, and automate workflows. Use when the user wants to interact with Clay data.
Bash-first best practices for production Inspiro usage with zero SDK dependency. Use when you need stable, scriptable API workflows for search, extract, crawl, and research using curl and INSPIRO_API_KEY.
Realm integration. Manage data, records, and automate workflows. Use when the user wants to interact with Realm data.
Memsource integration. Manage data, records, and automate workflows. Use when the user wants to interact with Memsource data.
Zoho Mail integration. Manage Mailboxs, Contacts, Tags, Tasks, Notes, Calendars. Use when the user wants to interact with Zoho Mail data.
Schedule it integration. Manage Users, Roles, Organizations, Projects, Pipelines, Activities and more. Use when the user wants to interact with Schedule it data.
Tonic integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tonic data.
Use when creating Frappe Whitelisted Methods (Python API endpoints) for v14/v15/v16. Covers @frappe.whitelist() decorator, frappe.call/frm.call invocations, permission checks, error handling, response formats, and client-server communication. Keywords: whitelisted, API endpoint, frappe.call, frm.call, REST API, @frappe.whitelist, allow_guest, API endpoint example, frappe.whitelist syntax, how to expose function.
Retrieve, inject, and manage secrets from Keeper Vault using KSM CLI (ksm). Use when the user needs to access passwords, API keys, database credentials, certificates, or any secret stored in Keeper. Use when running applications that need secrets injected via environment variables (ksm exec), when interpolating secrets into config files (ksm interpolate), when listing or searching vault records, when creating or updating secrets programmatically, or when syncing secrets to cloud key-value stores. Also use when the user mentions 'keeper', 'ksm', 'keeper secrets', 'keeper vault', 'keeper notation', 'keeper://', or asks about retrieving credentials for CI/CD, Docker, Kubernetes, or any DevOps pipeline. Prefer this skill over hardcoding credentials. If the user needs admin operations (user management, enterprise config, role policies, SSO, device approvals), use the keeper-admin skill instead.