skill-sheet
- Repo stars 435
- Author updated Live
- Author repo nvim
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @benbrastmckie · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: skill-sheet
description: XLSX creation, editing, and analysis routing to sheet-agent Thin wrapper that routes XLSX creati…
category: data
runtime: no special runtime
---
# skill-sheet output preview
## PART A: Task fit
- Use case: XLSX creation, editing, and analysis routing to sheet-agent Thin wrapper that routes XLSX creation, editing, and analysis requests to the sheet-agent, which manipulates spreadsheets using openpyxl and pandas via Bash. Reference (do not load eagerly): This skill activates when: When an implementing agent encounters any of these patterns: Do not invoke for:….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Context Pointers / Trigger Conditions / Direct Invocation” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “XLSX creation, editing, and analysis routing to sheet-agent Thin wrapper that routes XLSX creation, editing, and analysis requests to the sheet-agent, which manipulates spreadsheets using openpyxl and pandas via Bash. Reference (do not load eagerly): This skill activates when: When an implementing agent encounters any of these patterns: Do not invoke for:…”.
- **02** When the source has headings, the agent prioritizes “Context Pointers / Trigger Conditions / Direct Invocation” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/sheet`, `/edit`, `/table`, `/budget`, `/convert`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Context Pointers / Trigger Conditions / Direct Invocation”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-sheet
description: XLSX creation, editing, and analysis routing to sheet-agent Thin wrapper that routes XLSX creati…
category: data
source: benbrastmckie/nvim
---
# skill-sheet
## When to use
- XLSX creation, editing, and analysis routing to sheet-agent Thin wrapper that routes XLSX creation, editing, and analy…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Context Pointers / Trigger Conditions / Direct Invocation” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-sheet" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Context Pointers / Trigger Conditions / Direct Invocation
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} XLSX Skill
Thin wrapper that routes XLSX creation, editing, and analysis requests to the sheet-agent, which manipulates spreadsheets using openpyxl and pandas via Bash.
Context Pointers
Reference (do not load eagerly):
- Path:
.claude/context/formats/subagent-return.md - Purpose: Return validation
- Load at: Subagent execution only
Note: This skill is a thin wrapper. Context is loaded by the delegated agent, not this skill.
Trigger Conditions
This skill activates when:
Direct Invocation
- User explicitly runs
/sheetcommand - User runs
/editcommand with a .xlsx file
Implicit Invocation (during task implementation)
When an implementing agent encounters any of these patterns:
Plan step language patterns:
- "Create spreadsheet [file].xlsx with [content]"
- "Create xlsx [file] with [columns/data]"
- "Edit [file].xlsx to [change]"
- "Edit spreadsheet [file] to [change]"
- "Add formulas to [file].xlsx"
- "Add formatting to [file].xlsx"
- "Update [file].xlsx with [data]"
- "Analyze [file].xlsx for [purpose]"
File extension detection:
- Target file has extension:
.xlsx,.xlsm - Operation type: create, edit, update, modify, analyze, add formulas, add formatting
Task description keywords:
- "XLSX creation"
- "spreadsheet creation"
- "xlsx editing"
- "spreadsheet editing"
- "add formulas"
- "add formatting"
- "xlsx analysis"
When NOT to Trigger
Do not invoke for:
- Spreadsheet-to-table conversion (use skill-filetypes-spreadsheet for /table)
- Simple CSV/TSV reading (use Read tool directly)
- Grant budget creation (use skill-budget for /budget)
- PDF/DOCX operations (use other filetypes skills)
- Presentation operations (use skill-presentation)
Execution
1. Input Validation
Validate required inputs:
file_path- Must be provided; for edit/analyze must exist; for create mode may not exist yetinstruction- Natural language instruction describing the desired operation (required)mode- One of: "create", "edit", "analyze" (inferred from context and file existence)
# For edit mode: validate source exists and is xlsx/xlsm
if [ "$mode" = "edit" ]; then
if [ ! -f "$file_path" ]; then
return error "XLSX file not found: $file_path"
fi
if [[ "${file_path##*.}" != "xlsx" && "${file_path##*.}" != "xlsm" ]]; then
return error "Source must be a .xlsx or .xlsm file: $file_path"
fi
fi
# For analyze mode: validate source exists
if [ "$mode" = "analyze" ]; then
if [ ! -f "$file_path" ]; then
return error "File not found for analysis: $file_path"
fi
fi
# For create mode: validate xlsx extension
if [ "$mode" = "create" ]; then
if [[ "${file_path##*.}" != "xlsx" && "${file_path##*.}" != "xlsm" ]]; then
return error "New file must have .xlsx or .xlsm extension: $file_path"
fi
fi
2. Context Preparation
Prepare delegation context:
{
"file_path": "/absolute/path/to/spreadsheet.xlsx",
"instruction": "Create a budget tracking spreadsheet with categories, monthly columns, and SUM formulas",
"mode": "create",
"metadata": {
"session_id": "sess_{timestamp}_{random}",
"delegation_depth": 1,
"delegation_path": ["orchestrator", "xlsx", "skill-sheet"]
}
}
3. Invoke Agent
CRITICAL: You MUST use the Agent tool to spawn the sheet-agent.
Required Tool Invocation:
Tool: Agent (NOT Skill, NOT Plan)
Parameters:
- subagent_type: "sheet-agent"
- prompt: [Include file_path, instruction, mode, metadata]
- description: "{mode} {file_path}: {instruction}"
DO NOT use Skill(sheet-agent) - this will FAIL.
Agents live in .claude/agents/ or extension agent directories, not .claude/skills/.
The Skill tool can only invoke skills from .claude/skills/.
The agent will:
- Detect available tools (openpyxl, pandas)
- Execute the requested operation (create, edit, or analyze)
- Validate the output file
- Return standardized JSON result
4. Return Validation
Validate return matches subagent-return.md schema:
- Status is one of: created, edited, analyzed, partial, failed
- Summary is non-empty and <100 tokens
- Artifacts array present with output file path
- Metadata contains session_id, agent_type, delegation info
Status value rules:
created- New file successfully creatededited- Existing file successfully modifiedanalyzed- File read and analysis returnedpartial- Some operations succeeded, others failedfailed- No operations applied, error occurred- NEVER use "completed" (triggers Claude stop behavior)
5. Return Propagation
Return validated result to caller without modification.
Return Format
See .claude/context/formats/subagent-return.md for full specification.
Expected successful return:
{
"status": "created",
"summary": "Created budget.xlsx with 4 category rows, monthly columns Jan-Dec, SUM formulas for totals, and currency formatting.",
"artifacts": [
{
"type": "implementation",
"path": "/absolute/path/to/budget.xlsx",
"summary": "XLSX workbook with formulas and formatting"
}
],
"metadata": {
"session_id": "sess_...",
"agent_type": "sheet-agent",
"delegation_depth": 2,
"delegation_path": ["orchestrator", "xlsx", "skill-sheet", "sheet-agent"],
"tool_used": "openpyxl",
"mode": "create",
"sheets": 1,
"rows": 6,
"columns": 14
},
"next_steps": "Open spreadsheet to verify formulas and formatting"
}
Error Handling
Input Validation Errors
Return immediately with failed status if file not found, not a .xlsx/.xlsm, or instruction is empty.
Unsupported Format
Return failed status if file extension is not .xlsx or .xlsm (for create/edit). Suggest using /convert or /table for other spreadsheet operations.
Agent Errors
Pass through the agent's error return verbatim.
Tool Not Available
Return failed status with installation instructions for openpyxl and pandas.
MUST NOT
- Run the postflight step (git commit, status update) -- that is the command's responsibility
- Modify the return from sheet-agent before propagating
- Load context files eagerly -- only reference them when needed
- Use the Skill tool to invoke sheet-agent (use Agent tool instead)
Decide Fit First
Design Intent
How To Use It
Boundaries And Review