Agent Skills › harumiWeb/exstruct › exstruct-cli

exstruct-cli

GitHub

指导Agent使用ExStruct CLI安全处理Excel工作簿的创建、编辑与验证。涵盖命令选择、安全规则及干跑流程，适用于新建、修改或校验场景，复杂任务移交MCP。

.agents/skills/exstruct-cli/SKILL.md harumiWeb/exstruct

Trigger Scenarios

需要创建新的Excel工作簿需要编辑现有Excel文件不确定文件可读性或需验证格式查询操作列表或具体约束涉及Excel处理的决策咨询

Install

npx skills add harumiWeb/exstruct --skill exstruct-cli -g -y

More Options

Non-standard path

npx skills add https://github.com/harumiWeb/exstruct/tree/main/.agents/skills/exstruct-cli -g -y

Use without installing

npx skills use harumiWeb/exstruct@exstruct-cli

指定 Agent (Claude Code)

npx skills add harumiWeb/exstruct --skill exstruct-cli -a claude-code -g -y

安装 repo 全部 skill

npx skills add harumiWeb/exstruct --all -g -y

预览 repo 内 skill

npx skills add harumiWeb/exstruct --list

SKILL.md

Frontmatter

{
    "name": "exstruct-cli",
    "description": "Use ExStruct CLI to validate, inspect, create, and edit Excel workbooks safely. Trigger when an agent needs `exstruct patch`, `exstruct make`, `exstruct validate`, `exstruct ops list`, or `exstruct ops describe`, especially for create-vs-edit decisions, dry-run workflows, backend constraints, or safe workbook-edit guidance."
}

ExStruct CLI

Use the existing editing CLI as the default local operational interface for ExStruct workbook create/edit requests.

Select a command

Use exstruct make when the user wants a new workbook created and populated.
Use exstruct patch when the user wants an existing workbook edited.
Use exstruct validate when workbook readability is uncertain or before a risky edit on an unfamiliar file.
Use exstruct ops list when the required operation is still unclear.
Use exstruct ops describe <op> when you know the likely op name but need the exact schema or constraints.
Hand the workflow off to MCP when the user needs host-owned path policy, transport mapping, artifact mirroring, or other server-managed behavior.

Safety rules

Do not invent unsupported patch ops.
Do not apply destructive edits immediately when the request is ambiguous.
Prefer --dry-run before risky edits.
Pin --backend openpyxl when the dry run and the real apply must use the same engine.
Explain backend-specific failures directly instead of hiding them behind a generic retry.