feishu-cli-visual

A Feishu visualization and presentation skill for choosing and creating visual formats such as diagrams, charts, posters, slides, interactive HTML components, and dashboards.

In plain words
What is it for?
Use it to create editable boards, flowcharts, Mermaid or SVG diagrams, slide decks, dynamic HTML components, standalone HTML apps, and data visualizations.
Why use it?
It helps match a communication task to a suitable Feishu output format and apply consistent visualization rules.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/riba2534/feishu-cli/feishu-cli-visual
Any agent
npx skills add riba2534/feishu-cli --skill feishu-cli-visual
Clone the repo
git clone --depth 1 https://github.com/riba2534/feishu-cli

Made for: Claude Code, Codex.

Per session 167 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 582 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00167 $0.00582
Opus 5 $0.00084 $0.00291
Sonnet 5 $0.00033 $0.00116
Haiku 4.5 $0.00017 $0.00058

Measured 3d ago against content hash a846ad9160d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

feishu-cli-visual scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

The scan reads SKILL.md. This mod also ships 6 executable files (references/workflows/board/scripts/svg_to_board.py, references/workflows/dataviz/scripts/check_docs.js, references/workflows/dataviz/scripts/validate_palette.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/feishu-cli-visual/SKILL.md · 40 lines

What it actually says

飞书可视化与展示

加载工作流后,将其中 references/scripts/templates/examples/ 相对路径按该 workflow.md 所在目录解析;执行脚本时使用解析后的实际路径,不要依赖当前 shell 目录。

先读 dataviz 选择载体;用户已明确载体时直接读取对应工作流。

路由

意图 读取文件
未指定载体的数据图表、配色和形式选择 references/workflows/dataviz/workflow.md
静态画板、可编辑节点、SVG、Mermaid/PlantUML references/workflows/board/workflow.md
创建或修改 Slides 演示文稿 references/workflows/slides/workflow.md
文档内动态、交互、CSS/JS、ECharts、3D references/workflows/htmlbox/workflow.md
把 HTML 发布为妙搭应用 references/workflows/apps/workflow.md

载体边界

  • 要动态或交互:htmlbox。
  • 要静态且节点可编辑:board。
  • 要演示文稿:slides。
  • 要独立可分享 HTML 应用:apps。
  • 要消息通知卡片:feishu-cli-messaging 的 card 工作流。

改动色板或底色后运行本 Skill 的 dataviz 校验脚本;原样使用已校验色板无需重复验证。

Files

What ships with it

37 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 40 lines · 167 tokens per session scan A a846ad9160d6

Subscribe to this mod's changes

feishu-cli-visual is a skill published in the GitHub repository riba2534/feishu-cli (1,378 stars, last pushed 5d ago), licensed MIT. It adds 167 tokens to every session and 582 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens