Skill UI

Reply to every recipient in a Gmail thread from the CLI with gws gmail +reply-all, handling threading automatically while allowing HTML bodies, attachments, drafts, and recipient adjustments such as adds, CC/BCC, or removals.

CLI helper that uploads local Apps Script assets (.gs, .js, .html, appsscript.json) to a project via `gws script +push`, replacing every file while skipping hidden folders and node_modules; specify the target script ID and optional directory.

Announce a Google Drive file inside a Chat space via the `gws workflow +file-announce` command, automatically pulling the file name and supporting optional custom messages and formats.

Google Workflow command surfaces your next meeting’s agenda, attendees, and linked docs so you can quickly review what’s coming and which calendar it belongs to.

Generates a standup-ready summary that combines today’s calendar meetings with open tasks via the GWS workflow command, offering JSON, table, YAML, or CSV output to keep updates concise and ready for reporting.

Creates high-fidelity visuals through structured JSON prompts and a Python generator script, handling subjects, styles, references, and technical specs for characters, scenes, or products.

A disciplined workflow that forces you to build in thin vertical slices, test, verify, and commit each working increment before moving on, ideal for multi-file features or large refactors.

Guidelines for crafting industrial brutalist interfaces that merge Swiss print and military terminal aesthetics, emphasizing rigid grids, stark typography, utilitarian color, and analog degradation for data-heavy dashboards or editorial sites.

This skill provides comprehensive functionality for managing professional schedules, including viewing, creating, and updating events. It supports inviting attendees, checking free/busy times, suggesting optimal meeting slots, and reserving meeting rooms within the Lark ecosystem. It guides users through complex workflows for accurate scheduling.

A utility for interacting with the Lark/Feishu communication directory. It allows users to search for employees by name or email to obtain an open_id, or use an open_id to retrieve comprehensive profile data, including department, contact details, status, and signature. Ideal for preparing information before sending messages or scheduling events. Note that department tree traversal and organizational structure mapping require native OpenAPI calls.

Manage Lark/Feishu Drive files and folders, including upload, download, importing local files (Markdown, Excel, PPTX), managing versions, permissions, and document comments.

Guides developers to wrap Feishu API calls into reusable lark-cli skills, covering API research, command templates, and best practices for authentication, permissions, and orchestration.