Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
The author's original description, preserved in English. It describes intent, not verified performance.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
xlsx is a Claude Code Skill packaged as a fixed source snapshot. This editorial preview summarizes its declared purpose, on-disk structure and reviewable risk surface; it is not a controlled task evaluation.
Review scope
Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.
Observable capabilities
Source-declared purpose: Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns,
Collected 53 file(s), including 12 script(s) and 1 reference(s).
Source-described workflow candidates are linked to exact source lines.
Limitations & scope
No controlled task evaluation was performed.
Exact token counts are unavailable and are not estimated.
Static findings are review prompts, not safety guarantees.
Relevant for
Technical readers evaluating this Skill
Reviewers studying how the Skill is constructed
02 / STRUCTURE
What ships with the skill
The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.
{
"name": "xlsx",
"description": "Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.",
"license": "Complete terms in LICENSE.txt"
}
03 / WORKFLOW
A reading of the operating sequence
This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.
01
Input
Confirm scope
Read the trigger conditions and decide whether this skill matches the current task.
Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.
Items warrant review
290 lexical/coverage finding(s) require review. At least one known file was not retained and could not be scanned; this is not a no-findings or safety result.
Network accessObserved
File writesObserved
Credential useNot observed
Medium
Network access is mentioned
38 occurrences
A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 38 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 213 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
skills/xlsx/scripts/office/schemas/ecma/fouth-edition/opc-contentTypes.xsd is known from collection metadata but its content is unavailable. No line-level finding can be made for this file; absence of other matches is not a safety result. Content was not retained by collection policy. This rule matched 39 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
Review source evidence and runtime permissions before installing.
05 / CONTEXT
Where context can be spent
Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.
Exact token counts unavailable
All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.
No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.
06 / EVALUATION
Controlled evaluation
No controlled evaluation
This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.
Open the immutable source at https://github.com/anthropics/skills/tree/e4bb5d960d87126ff3b3a8af1a104b7db67560ba/skills/xlsx/SKILL.md.
Review the license, prerequisites and all bundled resources.
Install the skill into a personal or project-level Claude Code skills directory.
Restart or refresh Claude Code so the skill can be discovered.
Verify installation
Open Claude Code and confirm the skill appears in the installed skills list, then run a representative prompt below.
Prerequisites
No controlled task evaluation was performed.
Exact token counts are unavailable and are not estimated.
Static findings are review prompts, not safety guarantees.
Example prompts
Representative task
Use the xlsx skill to help with this task. First summarize what the skill will do, then execute its documented workflow and show the source-linked evidence for each major decision.
Inspect before use
Read the xlsx skill files at https://github.com/anthropics/skills/tree/e4bb5d960d87126ff3b3a8af1a104b7db67560ba/skills/xlsx/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.
08 / VERDICT
A decision, with its limits attached
Strengths
Source is pinned to an immutable commit.
Instructions and resource inventory are available for inspection.
Considerations
Effectiveness has not been measured.
Review the source and runtime requirements before installation.
Research conclusion
Editorial preview: this dossier has a complete research layout; controlled evaluation is deferred until after deployment.
09 / PROVENANCE
Traceable by construction
The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.
Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.