XLSX Author
Generate a .xlsx file directly in headless sessions.
The skill limits output to a local ./out/<name>.xlsx artifact and uses a headless workflow without requiring external services or broad permissions. It lacks user confirmation, sensitive-data guidance, overwrite protection, rollback, and explicit data-flow disclosure, so points are deducted.
The instructions, example, output path, and workbook conventions are internally coherent. However, openpyxl availability and version are unspecified, and there is no input validation, exception handling, failure feedback, or static evidence of reproducible key-path tests; deductions apply and the static ceiling is respected.
The target scenario is clear: managed-agent/CMA sessions without an open Office application, with a stated non-fit case when live Excel tools are available. Trigger precision, input boundaries, complex-workbook limitations, and Chinese-environment support are insufficiently documented, so points are deducted.
The document is concise and layered around an output contract, construction method, conventions, and non-use case. Repository-level Apache-2.0 licensing and CI are present, but the skill lacks its own versioning, changelog, maintenance owner, update path, FAQ, and troubleshooting guidance, so points are deducted.
The skill plausibly produces a directly collectable .xlsx artifact and provides useful modeling conventions for inputs, formulas, links, and checks. There is no committed representative output, completeness validation, formula-calculation compatibility guidance, or comparative-benefit evidence, so the score remains moderate and within the static limit.
The skill text and repository CI are auditable, and CI validates plugin structure. There is no committed test suite, execution log, or third-party reproduction evidence covering the xlsx-author key paths, so only limited credit is justified.
- Execution assumes that openpyxl is available, but no version, installation, or dependency check is documented.
- The skill specifies file creation but does not ensure formula recalculation, external-link integrity, or correctness for complex workbooks; human review is required, and overwrite risk should be checked.
- The repository CI primarily validates plugin structure and does not establish that this skill generates correct workbooks.
What it does & when to use it
This skill is for headless managed-agent sessions that need an Excel workbook as a file artifact. It writes the workbook to local disk at `./out/<name>.xlsx` instead of driving an open Excel workbook. The skill body shows a Python example built with `openpyxl`, including formulas and formatting. It fits workflows where you need a deliverable spreadsheet and there is no live Office app to control.
Creates ./out/ if needed and saves a .xlsx file there; uses Python and openpyxl to build a workbook; writes worksheets, cell values, formulas, and font styling; returns the relative output path for collection by the orchestration layer.
- You need to hand back an Excel file from a managed-agent run, not edit a live workbook
- You want to generate a spreadsheet model with formulas and formatting from Python
- There is no open Office app available, so the workflow must produce a file artifact
- You need the output saved under `./out/` for downstream retrieval
Pros & cons
- Produces a real `.xlsx` file artifact
- Straightforward dependency set: Bash, Python, and openpyxl
- Well suited to headless sessions without a live Excel app
- Only the file-generation path is documented; there is no advanced templating or validation workflow here
- It is not the right fit when you need to control an already-open Excel workbook
- No built-in test or error-handling guidance is shown
How to install
Place the skill at plugins/agent-plugins/model-builder/skills/xlsx-author/SKILL.md. The repository README says the collection can be deployed as a Claude Cowork plugin or through Claude Managed Agents.
How to use
Write a short Python script using openpyxl, then save the workbook to ./out/<name>.xlsx. The example in the skill saves ./out/model.xlsx; return that relative path in your final response.
Compared to similar skills
Compared with live-workbook control, this skill uses a file-output workflow. The README also says to use mcp__office__excel_* tools when they are available; this skill is the headless fallback.