Agent Skills › harumiWeb/exstruct › exstruct-cli

exstruct-cli

GitHub

使用 ExStruct CLI 安全地验证、检查、创建和编辑 Excel 工作簿。适用于新建或修改文件、操作查询及后端约束处理，强调通过 dry-run 和后端锁定确保编辑安全。

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

Trigger Scenarios

需要创建新的 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.