Token导航 LogoToken导航

Agent Skill · 前端设计

excel-xlsx-zc(Excel XLSX ZC 前端)

用于辅助数据整理、表格处理、CSV/Excel 分析、指标计算和图表准备。它适合让 Agent 清洗字段、汇总数据、发现异常、生成统计口径或把分析结果转成可读说明。使用时需要确认数据来源、字段含义和时间范围,避免把样本数据当全量事实;涉及敏感数据、导出文件或批量写回时,应先确认权限和脱敏边界。

excel-xlsx-zc 是前端设计类 Agent Skill,可用宿主为 Local Agent,通过unknown获取,权限为需要联网;许可证信息还不明确,暂无第三方扫描结果,按安装量在前端设计类的 10,216 个 Skill 里排第 10,194。

总安装 1周安装 8下载 65核验 2026-05-01
前端设计需要联网unknown未标认证来源可访问许可证需确认审计未展示Local Agent

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:excel-xlsx-zc(Excel XLSX ZC 前端)
来源仓库:https://skills.volces.com
仓库路径:excel-xlsx-zc
安装命令:
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。当前暂无明确安装命令,请以来源页面说明为准。

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

excel-xlsx-zc 用于辅助数据整理、表格处理和 XLSX 文件分析,支持特定业务场景数据准备。它能生成统计口径或异常报告,适合定制化数据分析需求。安装方式未知,暂无安装命令。excel-xlsx-zc 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

使用时需确认数据来源与时间范围,避免样本误判为全量。涉及文件操作时应检查权限与数据安全机制。

来源仓库内路径:excel-xlsx-zc

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Local Agent;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    没有现成安装命令,按unknown的说明从来源页面获取,仓库路径是 excel-xlsx-zc。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

excel-xlsx-zc 怎么安装?

公开资料没有给出可以直接复制的命令,需要按来源页面说明手动安装,仓库内路径为 excel-xlsx-zc。

excel-xlsx-zc 支持哪些 AI 工具?

公开资料标注支持 Local Agent。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

excel-xlsx-zc 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

excel-xlsx-zc 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

excel-xlsx-zc 用的人多吗?

公开数据是累计安装 1 次,近一周安装 8 次,下载 65 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

excel-xlsx-zc 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 Local Agent 一种宿主,触发方式和使用习惯不用来回切换。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Local Agent,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
excel-xlsx-zc

Excel XLSX ZC 前端 · 本页

1—需要联网未明确未收录

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

When to Use

Use when the main artifact is a Microsoft Excel workbook or spreadsheet file, especially when formulas, dates, formatting, merged cells, workbook structure, or cross-platform behavior matter.

Core Rules

1. Choose the workflow by job, not by habit

  • Use pandas for analysis, reshaping, and CSV-like tasks.
  • Use openpyxl when formulas, styles, sheets, comments, merged cells, or workbook preservation matter.
  • Treat CSV as plain data exchange, not as an Excel feature-complete format.
  • Reading values, preserving a live workbook, and building a model from scratch are different spreadsheet jobs.

2. Dates are serial numbers with legacy quirks

  • Excel stores dates as serial numbers, not real date objects.
  • The 1900 date system includes the false leap-day bug, and some workbooks use the 1904 system.
  • Time is fractional day data, so formatting and conversion both matter.
  • Date correctness is not enough if the number format still displays the wrong thing to the user.

3. Keep calculations in Excel when the workbook should stay live

  • Write formulas into cells instead of hardcoding derived results from Python.
  • Use references to assumption cells instead of magic numbers inside formulas.
  • Cached formula values can be stale, so do not trust them blindly after edits.
  • Check copied formulas for wrong ranges, wrong sheets, and silent off-by-one drift before delivery.
  • Absolute and relative references are part of the logic, so copied formulas can be wrong even when they still "work".
  • Test new formulas on a few representative cells before filling them across a whole block.
  • Verify denominators, named ranges, and precedent cells before shipping formulas that depend on them.
  • A workbook should ship with zero formula errors, not with known #REF!, #DIV/0!, #VALUE!, #NAME?, or circular-reference fallout left for the user to fix.
  • For model-style work, document non-obvious hardcodes, assumptions, or source inputs in comments or nearby notes.

4. Protect data types before Excel mangles them

  • Long identifiers, phone numbers, ZIP codes, and leading-zero values should usually be stored as text.
  • Excel silently truncates numeric precision past 15 digits.
  • Mixed text-number columns need explicit handling on read and on write.
  • Scientific notation, auto-parsed dates, and stripped leading zeros are common corruption, not cosmetic issues.

5. Preserve workbook structure before changing content

  • Existing templates override generic styling advice.
  • Only the top-left cell of a merged range stores the value.
  • Hidden rows, hidden columns, named ranges, and external references can still affect formulas and outputs.
  • Shared strings, defined names, and sheet-level conventions can matter even when the visible cells look simple.
  • Match styles for newly filled cells instead of quietly introducing a new visual system.
  • If the workbook is a template, preserve sheet order, widths, freezes, filters, print settings, validations, and visual conventions unless the task explicitly changes them.
  • Conditional formatting, filters, print areas, and data validation often carry business meaning even when users only mention the numbers.
  • If there is no existing style guide and the file is a model, keep editable inputs visually distinguishable from formulas, but never override an established template to force a generic house style.

6. Recalculate and review before delivery

  • Formula strings alone are not enough if the recipient needs current values.
  • openpyxl preserves formulas but does not calculate them.
  • Verify no #REF!, #DIV/0!, #VALUE!, #NAME?, or circular-reference fallout remains.
  • If layout matters, render or visually review the workbook before calling it finished.
  • Be careful with read modes: opening a workbook for values only and then saving can flatten formulas into static values.
  • If assumptions or hardcoded overrides must stay, make them obvious enough that the next editor can audit the workbook.

7. Scale the workflow to the file size

  • Large workbooks can fail for boring reasons: memory spikes, padded empty rows, and slow full-sheet reads.
  • Use streaming or chunked reads when the file is big enough that loading everything at once becomes fragile.
  • Large-file workflows also need narrower reads, explicit dtypes, and sheet targeting to avoid accidental damage.

Common Traps

  • Type inference on read can leave numbers as text or convert IDs into damaged numeric values.
  • Column indexing varies across tools, so off-by-one mistakes are common in generated formulas.
  • Newlines in cells need wrapping to display correctly.
  • External references break easily when source files move.
  • Password protection in old Excel workflows is not serious security.
  • .xlsm can contain macros, and .xls remains a tighter legacy format.
  • Large files may need streaming reads or more careful memory handling.
  • Google Sheets and LibreOffice can reinterpret dates, formulas, or styling differently from Excel.
  • Dynamic array or newer Excel functions like FILTER, XLOOKUP, SORT, or SEQUENCE may fail or degrade in older viewers.
  • A workbook can look fine while still carrying stale cached values from a prior recalculation.
  • Saving the wrong workbook view can replace formulas with cached values and quietly destroy a live model.
  • Copying formulas without checking relative references can push one bad range across an entire block.
  • Hidden sheets, named ranges, validations, and merged areas often keep business logic that is invisible in a quick skim.
  • A workbook can appear numerically correct while still failing because filters, conditional formats, print settings, or data validation were stripped.
  • A workbook can be numerically correct and still fail visually because wrapped text, clipped labels, or narrow columns were never reviewed.

Related Skills

Install with clawhub install <slug> if user confirms:

  • csv — Plain-text tabular import and export workflows.
  • data — General data handling patterns before spreadsheet output.
  • data-analysis — Higher-level analysis that can feed workbook deliverables.

Feedback

  • If useful: clawhub star excel-xlsx
  • Stay updated: clawhub sync

平台分布

Local Agent

74.63%
按下载量换算49

安全审计

暂无安全审计结果可展示。

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills