A tool for finding and using Feishu OpenAPI endpoints that are not already covered by an existing skill or lark-cli command. OpenAPI is the documented interface that lets software call a service programmatically.
Use when first setting up lark-cli, running auth login, switching user/bot identity (--as), handling permission denied or scope errors, needing to update lark-cli, or seeing notice in JSON output.
A spreadsheet tool for Feishu, a workplace collaboration platform. It can create and manage workbooks and sheets, read and write cell data, search within known spreadsheets, and export files.
A guide for creating custom skills that use lark-cli, the command-line tool for Feishu. It helps package one API call or a sequence of API calls into a reusable instruction file.
A Feishu presentation tool for creating, reading, and editing slide decks. It can work with whole presentations or make targeted changes to individual slides and elements.
A Feishu task-management tool for creating and organizing tasks, checklists, subtasks, assignments, and task-related records. It also supports task agents and attachments.
A meeting assistant that can join an ongoing Feishu video meeting on a user's behalf and read live events such as people joining, speaking, chatting, or sharing their screen. It works during the meeting rather than only after it ends.
A tool for finding completed Feishu video meetings and retrieving their follow-up records, such as summaries, action items, chapters, transcripts, recordings, and participant lists. A transcript is a written record of what people said, usually with speakers and times.
A tool for viewing and editing Feishu whiteboards, which are shared online canvases for diagrams and other visual information. It can export a board as an image or as its underlying structure.
A guide for designing interface elements for browser games, including status displays, menus, overlays, and responsive layouts. It treats the game world and the text-heavy interface as separate layers.
A workflow for collecting completed Feishu meeting notes from a time range and turning them into a structured report. Meeting notes can include summaries, decisions, action items, and links to supporting records.
A workflow that combines calendar events and unfinished tasks into a short stand-up report for a chosen day or week. A stand-up report is a quick summary of what is scheduled and what still needs attention.
Run browser-game playtests and frontend QA. Use when the user asks for smoke tests, screenshot-based verification, browser automation, HUD or overlay review, or structured issue-finding in a browser game.
Route early browser-game work. Use when the user needs stack selection and workflow planning across design, implementation, assets, and playtesting before moving to a specialist skill.
Design UI surfaces for browser games. Use when the user asks for HUDs, menus, overlays, responsive layouts, or visual direction that must protect the playfield.
Implement 2D browser games with Phaser. Use when the user wants a Phaser, TypeScript, and Vite stack for scenes, gameplay systems, cameras, sprite animation, and DOM-overlay HUD patterns.
Build React-hosted 3D browser games with React Three Fiber. Use when the user wants pmndrs-based scene composition, shared React state, and 3D HUD integration inside a React app.
Generate and normalize 2D sprite animations. Use when the user asks for full-strip generation from approved source frames, consistent anchor and scale normalization, or preview assets for browser-game animation.
Implement browser-game runtimes with plain Three.js. Use when the user wants imperative scene control in TypeScript or Vite with GLB assets, loaders, physics, and low-level WebGL debugging.
Prepare and optimize browser-game 3D assets. Use when the user asks for GLB or glTF shipping work, including Blender cleanup and export, collision or LOD setup, compression, texture packaging, and runtime validation.
Set browser-game architecture before implementation. Use when the user needs engine choice, simulation and render boundaries, input model, asset organization, or save/debug/performance strategy.
Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes. Use the GitHub app for PR metadata and flat comment reads, and use the bundled GraphQL script via gh whenever…
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Use the GitHub app from this plugin for PR metadata and patch context, and use gh for Actions check and log inspection before implementing any approved fix.
Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: