Agent skill

Spreadsheet Direct Verification

by HKUDS in HKUDS/OpenSpace

Use a deterministic Python/openpyxl inspection pass to verify workbook structure, counts, marked rows, and output-file existence when delegated spreadsheet summaries seem inconsistent.

MITAuto-check passedDocuments & Office

Install Spreadsheet Direct Verification

skills CLI
$ npx skills add HKUDS/OpenSpace --skill spreadsheet-direct-verification -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HKUDS/OpenSpace spreadsheet-direct-verification --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/gdpval/skills/spreadsheet-direct-verification .claude/skills/spreadsheet-direct-verification && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
spreadsheet-direct-verification
GitHub stars
7.7k
Token cost
~3.6k tokens
SKILL.md length
961 words
Files
2
Skills in repo
199
Repo updated
First seen
Licence
MIT

At a glance

Use a deterministic Python/openpyxl inspection pass to verify workbook structure, counts, marked rows, and output-file existence when delegated spreadsheet summaries seem inconsistent.

  • Works in 6 steps: Identify the workbook(s) and expected… → Determine what "marked row" means for… → Run a direct Python inspection on the… → …
  • Tasks that involve Excel spreadsheets
  • SKILL.md covers When to use this, Core principle, Workflow and Minimum verification checklist, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spreadsheet Direct Verification is an agent skill from HKUDS/OpenSpace. Use a deterministic Python/openpyxl inspection pass to verify workbook structure, counts, marked rows, and output-file existence when delegated spreadsheet summaries seem inconsistent.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

It sits in Documents & Office, covering Excel spreadsheets. It works with Python and openpyxl. The repository describes itself as: "OpenSpace: The Skill Management Layer for AI Agents" -- https://open-space.cloud/. The licence is MIT.

When your agent uses it

  • Tasks that involve Excel spreadsheets

Example prompts

  • “/spreadsheet-direct-verification”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Identify the workbook(s) and expected output file(s).
  2. Determine what "marked row" means for the task.
  3. Run a direct Python inspection on the files from disk.
  4. Compare the script output against any delegated summary.
  5. If they differ, treat the script as authoritative.
  6. Only then provide the final user-facing summary.

What it can do on your machine

Read from SKILL.md and the folder at commit 3827781. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Spreadsheet Direct Verification loads about 3.6k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 961 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HKUDS/OpenSpace at commit 3827781, republished under its MIT licence (© HKUDS). 961 words, ~3,569 tokens.

Download SKILL.mdSave it as .claude/skills/spreadsheet-direct-verification/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
spreadsheet-direct-verification
description
Use a deterministic Python/openpyxl inspection pass to verify workbook structure, counts, marked rows, and output-file existence when delegated spreadsheet summaries seem inconsistent.

Spreadsheet Direct Verification

Use this workflow when a higher-level or delegated agent has interacted with spreadsheet files, but its summaries or claims are inconsistent, incomplete, or hard to trust.

The goal is to replace uncertain narrative summaries with a direct, reproducible inspection from disk before you finalize your answer.

When to use this

Apply this skill when any of the following happen:

  • A delegated agent reports conflicting workbook facts across messages
  • Sheet names, row counts, headers, or output paths are inconsistent
  • The agent says a file was created or modified, but did not verify it from disk
  • The task depends on exact workbook contents, especially after edits
  • You need a trustworthy final summary of what actually exists on disk

Core principle

When spreadsheet state matters, trust a deterministic script over a conversational summary.

Inspect the workbook directly with Python and openpyxl, and print a compact report covering:

  • workbook path
  • whether the file exists
  • sheet names
  • per-sheet headers
  • per-sheet row counts
  • totals for "marked" rows, if relevant to the task
  • whether expected output files exist

Use the script output as the basis for your final response.

Workflow

  1. Identify the workbook(s) and expected output file(s).
  2. Determine what "marked row" means for the task.
    • Examples:
      • rows with a non-empty marker column
      • rows with x, yes, true, or 1
      • rows highlighted by a prior workflow that also wrote a marker column
  3. Run a direct Python inspection on the files from disk.
  4. Compare the script output against any delegated summary.
  5. If they differ, treat the script as authoritative.
  6. Only then provide the final user-facing summary.

Minimum verification checklist

Before finalizing, verify and record:

  • exact input workbook path inspected
    • exact output workbook path inspected
    • whether each file exists
    • all sheet names in each workbook
    • header row for each relevant sheet
    • number of non-empty data rows per sheet
    • number of marked rows per sheet, if applicable
    • whether modifications appear in the saved output file

Production planning validation checklist

For manufacturing and production planning spreadsheets, extend the verification to include:

  1. Max daily minutes per press: Verify that no press exceeds the daily labor minute limit (e.g., 450 minutes per day per press).

    • Sum labor minutes grouped by press and date
    • Flag any press-date combinations exceeding the threshold
  2. Max weekly hours per team member: Verify that no team member exceeds weekly hour limits (e.g., 37.5 hours per week).

    • Sum assigned hours grouped by team member and week
    • Flag any team-member-week combinations exceeding the threshold
  3. Required roles per press: Verify that each press assignment includes all required roles (e.g., 1 operator + 1 water spider per press).

    • Count distinct role assignments per press per shift or date
    • Flag any press assignments missing required roles
  4. Minimum changeover requirements per press: Verify that required changeovers are scheduled (e.g., minimum 3 changeovers per press per week).

    • Count changeover events grouped by press and time period
    • Flag any press-period combinations below the minimum threshold
Example production planning verification script extension

Extend the base inspection script with these production-specific checks:

python
# Add to the INPUTS list if you have separate labor/assignment sheets
# Extend MARKER_CANDIDATES for production-specific columns
PRODUCTION_MARKER_CANDIDATES = MARKER_CANDIDATES | {"press", "team_member", "role", "changeover", "date", "week"}

# Production constraint thresholds (adjust per task)
MAX_DAILY_MINUTES_PER_PRESS = 450
MAX_WEEKLY_HOURS_PER_MEMBER = 37.5
REQUIRED_ROLES_PER_PRESS = {"operator", "water_spider"}  # or {"Operator", "Water Spider"}
MIN_CHANGEOVERS_PER_PRESS_PER_WEEK = 3

def validate_production_constraints(ws, headers):
    """Return a dict of constraint violations found in the worksheet."""
    violations = {
        "daily_minutes_exceeded": [],
        "weekly_hours_exceeded": [],
        "missing_roles": [],
        "insufficient_changeovers": [],
    }
    
    if not headers:
        return violations
    
    normalized_headers = [normalize(h).lower() for h in headers]
    
    # Find column indices
    press_idx = next((i for i, h in enumerate(normalized_headers) if "press" in h), None)
    member_idx = next((i for i, h in enumerate(normalized_headers) if "member" in h or "team" in h), None)
    role_idx = next((i for i, h in enumerate(normalized_headers) if "role" in h), None)
    minutes_idx = next((i for i, h in enumerate(normalized_headers) if "minute" in h or "labor" in h), None)
    date_idx = next((i for i, h in enumerate(normalized_headers) if "date" in h), None)
    changeover_idx = next((i for i, h in enumerate(normalized_headers) if "changeover" in h), None)
    
    # Aggregate data
    press_daily_minutes = {}  # (press, date) -> total minutes
    member_weekly_hours = {}  # (member, week) -> total hours
    press_roles = {}  # (press, date) -> set of roles
    press_changeovers = {}  # (press, week) -> count
    
    for row in ws.iter_rows(min_row=2, values_only=True):
        if not any(v is not None and str(v).strip() != "" for v in row):
            continue
        
        press = normalize(row[press_idx]) if press_idx is not None and press_idx < len(row) else None
        member = normalize(row[member_idx]) if member_idx is not None and member_idx < len(row) else None
        role = normalize(row[role_idx]).lower() if role_idx is not None and role_idx < len(row) else None
        minutes = float(row[minutes_idx]) if minutes_idx is not None and minutes_idx < len(row) and row[minutes_idx] else 0
        date_val = row[date_idx] if date_idx is not None and date_idx < len(row) else None
        is_changeover = row[changeover_idx] if changeover_idx is not None and changeover_idx < len(row) else None
        
        # Derive week from date if available
        week = None
        date_str = ""
        if date_val:
            try:
                from datetime import datetime
                if isinstance(date_val, datetime):
                    week = date_val.isocalendar()[1]
                date_str = str(date_val)
            except:
                date_str = str(date_val) if date_val else ""
                week = None
        else:
            date_str = ""
        
        # Aggregate daily minutes per press
        if press and minutes:
            key = (press, date_str)
            press_daily_minutes[key] = press_daily_minutes.get(key, 0) + minutes
        
        # Aggregate weekly hours per member (assume minutes -> hours)
        if member and minutes and week:
            key = (member, week)
            member_weekly_hours[key] = member_weekly_hours.get(key, 0) + minutes / 60
        
        # Track roles per press per date
        if press and role and date_str:
            key = (press, date_str)
            if key not in press_roles:
                press_roles[key] = set()
            press_roles[key].add(role)
        
        # Count changeovers per press per week
        if press and is_changeover and week:
            if is_truthy(is_changeover) or str(is_changeover).lower() in {"yes", "true", "1", "y", "x"}:
                key = (press, week)
                press_changeovers[key] = press_changeovers.get(key, 0) + 1
    
    # Check violations
    for (press, date), total in press_daily_minutes.items():
        if total > MAX_DAILY_MINUTES_PER_PRESS:
            violations["daily_minutes_exceeded"].append(f"{press} on {date}: {total} min")
    
    for (member, week), total in member_weekly_hours.items():
        if total > MAX_WEEKLY_HOURS_PER_MEMBER:
            violations["weekly_hours_exceeded"].append(f"{member} week {week}: {total:.1f} hrs")
    
    for (press, date), roles in press_roles.items():
        missing = REQUIRED_ROLES_PER_PRESS - roles
        if missing:
            violations["missing_roles"].append(f"{press} on {date}: missing {missing}")
    
    for (press, week), count in press_changeovers.items():
        if count < MIN_CHANGEOVERS_PER_PRESS_PER_WEEK:
            violations["insufficient_changeovers"].append(f"{press} week {week}: {count} changeovers")
    
    return violations

When validating production planning workbooks, run this extended script and report any constraint violations found.

Use a standalone Python script snippet instead of relying on ad hoc tool narration. This makes the inspection:

  • reproducible
  • easy to rerun
  • less prone to memory or interpretation errors
  • suitable for attaching exact findings to the final answer

Example inspection script

Adapt this script to the task. It is intentionally simple and explicit.

python
from pathlib import Path
from openpyxl import load_workbook

INPUTS = [
    "input.xlsx",
    "output.xlsx",
]

MARKER_CANDIDATES = {"mark", "marked", "flag", "selected", "include", "status"}

TRUTHY = {"x", "yes", "true", "1", "y"}

def normalize(value):
    if value is None:
        return ""
    return str(value).strip()

def is_truthy(value):
    return normalize(value).lower() in TRUTHY

def first_nonempty_row(ws, max_scan=10):
    for row in ws.iter_rows(min_row=1, max_row=min(ws.max_row, max_scan), values_only=True):
        if any(v is not None and str(v).strip() != "" for v in row):
            return list(row)
    return []

def data_row_count(ws):
    count = 0
    for row in ws.iter_rows(min_row=2, values_only=True):
        if any(v is not None and str(v).strip() != "" for v in row):
            count += 1
    return count

def marked_row_count(ws, headers):
    if not headers:
        return 0, None
    normalized_headers = [normalize(h).lower() for h in headers]
    marker_idx = None
    for i, h in enumerate(normalized_headers):
        if h in MARKER_CANDIDATES:
            marker_idx = i
            break
    if marker_idx is None:
        return 0, None

    count = 0
    for row in ws.iter_rows(min_row=2, values_only=True):
        if not any(v is not None and str(v).strip() != "" for v in row):
            continue
        value = row[marker_idx] if marker_idx < len(row) else None
        if is_truthy(value):
            count += 1
    return count, headers[marker_idx]

for file_str in INPUTS:
    path = Path(file_str)
    print(f"FILE: {path}")
    print(f"EXISTS: {path.exists()}")

    if not path.exists():
        print()
        continue

    wb = load_workbook(path, data_only=False)
    print(f"SHEETS: {wb.sheetnames}")

    for ws in wb.worksheets:
        headers = first_nonempty_row(ws)
        rows = data_row_count(ws)
        marked_count, marker_name = marked_row_count(ws, headers)

        print(f"  SHEET: {ws.title}")
        print(f"    HEADERS: {headers}")
        print(f"    DATA_ROWS: {rows}")
        if marker_name is not None:
            print(f"    MARKER_COLUMN: {marker_name}")
            print(f"    MARKED_ROWS: {marked_count}")
        else:
            print("    MARKER_COLUMN: <not found>")
    print()
Show full SKILL.md (387 more words)Show less

How to adapt the script safely

Adjust only the task-specific parts:

  • INPUTS: the exact workbook paths to verify
  • MARKER_CANDIDATES: possible names of the marker column
  • TRUTHY: accepted values that count as marked
  • row counting logic, if headers do not start on row 1
  • any expected output file paths to confirm

Do not weaken the script by replacing direct inspection with summary text from another agent.

If the workbook layout is unusual

Handle these cases explicitly:

Header row is not row 1

Search the first few rows for the first non-empty row or the row containing expected header names.

Multiple tables in one sheet

Limit verification to the relevant region and state that assumption.

Marked rows are based on formatting, not a marker column

If required, inspect formatting directly with openpyxl, but prefer a visible marker column whenever possible. If formatting-based logic is necessary, document exactly what you counted.

Formula-driven workbooks

If you need displayed values, consider load_workbook(..., data_only=True) in a separate pass. If you need formulas and saved values, inspect both modes and note which one you used.

Final response pattern

After running the verification script, summarize findings using facts from the output only. Include:

  • file verified
  • sheets present
  • row counts
  • marked-row totals
  • output file existence
  • any discrepancy discovered between delegated claims and actual disk state

Example final phrasing:

  • "I verified the workbook directly from disk with openpyxl."
  • "The output file exists at ...."
  • "The workbook contains sheets ...."
  • "Sheet ... has N data rows and M marked rows."
  • "A prior delegated summary was inconsistent, so I used the direct inspection results as authoritative."

Decision rule

If delegated spreadsheet summaries and direct inspection disagree:

  • trust the direct inspection
  • cite the discrepancy internally
  • base the final answer on the deterministic script output

Anti-patterns to avoid

Do not:

  • finalize based only on a delegated agent's prose summary
  • assume a workbook was saved without checking file existence
  • quote row counts without reading the workbook from disk
  • report sheet names from memory when they can be enumerated directly
  • mix speculative statements with verified spreadsheet facts

Why this skill is reusable

This pattern applies broadly to spreadsheet tasks involving:

  • workbook edits
  • filtering or marking rows
  • creating output copies
  • validating agent-performed file changes
  • reconciling conflicting intermediate reports

Whenever workbook facts are important and agent summaries are unreliable, a direct openpyxl verification pass is the safe fallback.

© HKUDS, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in benchmarks/gdpval/skills/spreadsheet-direct-verification of HKUDS/OpenSpace.

  • SKILL.md
  • .skill_id

Open the folder on GitHubat commit 3827781

Compare with similar skills

Spreadsheet Direct Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Spreadsheet Direct Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spreadsheet Direct Verification this skillHKUDS/OpenSpace7.7k—~3.6kAutomated safety check: PassMIT
Excel Workbook EditorTokenRhythm/opensquilla7.1k—~1.6kAutomated safety check: PassApache-2.0
Kimi XLSXthvroyal/kimi-skills238—~9.5kAutomated safety check: PassNone
Office XLSXopen-octo/octo-agent125—~1.8kAutomated safety check: NotesMIT
Cc Streaming Export Safetydoccker/cc-use-exp1.1k—~2.2kAutomated safety check: PassCustom licence
XLSXnexus-research-lab/nexus150—~501Automated safety check: PassApache-2.0

Similar skills

  • Excel Workbook Editor

    TokenRhythm/opensquilla

    Inspects, edits in place or creates Microsoft Excel .xlsx workbooks with openpyxl, treating each cell as a typed number, string, datetime or formula value.

    7.1k GitHub stars~1.6k tokensUpdated 4 days ago
    Documents & OfficeAuto-check passed
  • Kimi XLSX

    thvroyal/kimi-skills

    Specialized utility for advanced manipulation, analysis, and creation of spreadsheet files, including (but not limited to) XLSX, XLSM, CSV formats.

    238 GitHub stars~9.5k tokensUpdated 6 mo ago
    Documents & OfficeAuto-check passed
  • Office XLSX

    open-octo/octo-agent

    Create, read, and edit Excel (.xlsx) spreadsheets programmatically with openpyxl — cell values, formulas, styling (fonts/fills/borders/alignment/number formats), merged cells, multiple sheets…

    125 GitHub stars~1.8k tokensUpdated today
    Documents & OfficeAuto-check: notes
  • Cc Streaming Export Safety

    doccker/cc-use-exp

    当实现用户驱动的大文件导出或批量序列化(Excel/CSV/JSON/JSONL/PDF,数据量未知或超过 1 万行/10 MB)时触发;普通小文件下载、静态资源下载、非导出 Writer/Report 类不触发。防止 OOM、临时文件残留、同步导出阻塞 HTTP 线程和表格公式注入。

    1.1k GitHub stars~2.2k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • XLSX

    nexus-research-lab/nexus

    只要电子表格文件(.xlsx、.xlsm、旧版 .xls、.csv、.tsv)是任务的主要输入或输出,或者需要 被打开、读取、创建、修改,就使用本 Skill。也适用于公式、格式、图表、数据清洗和表格格式转换。

    150 GitHub stars~501 tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Office XLSX

    singula-ai/alego

    Read, create, and modify Excel workbooks (.xlsx), including data, formulas, formatting, and pandas analysis.

    109 GitHub starsUsed in 1 repo~2.3k tokens
    Documents & OfficeAuto-check passed

More from HKUDS/OpenSpace

All 199 skills in this repo
  • Walks through producing a master audio track plus stems in Python, from checking a reference file and timing sections by BPM to effects, a zip archive and final verification.

    7.7k GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Handle cascading data retrieval tool failures by falling back to embedded knowledge generation

    7.7k GitHub stars~765 tokensUpdated 1 mo ago
    Auto-check passed
  • Gives an agent a workaround when its code-execution sandbox keeps failing: save the Python script to a file and run it through the shell instead.

    7.7k GitHub stars~588 tokensUpdated 1 mo ago
    Auto-check passed
  • A recovery routine for agents whose sandboxed code runner keeps failing: save the Python script to disk, then run it through the shell and read the output.

    7.7k GitHub stars~652 tokensUpdated 1 mo ago
    Auto-check passed
  • Fallback ladder for failed sandboxed code runs, plus the habit of fixing the working directory first so generated files land in the right place.

    7.7k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Fallback workflow for executing Python code when executecodesandbox fails repeatedly

    7.7k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Questions about Spreadsheet Direct Verification

What does Spreadsheet Direct Verification do?

Use a deterministic Python/openpyxl inspection pass to verify workbook structure, counts, marked rows, and output-file existence when delegated spreadsheet summaries seem inconsistent. Spreadsheet Direct Verification is an agent skill from HKUDS/OpenSpace. Use a deterministic Python/openpyxl inspection pass to verify workbook structure, counts, marked rows, and output-file existence when delegated spreadsheet summaries seem inconsistent.

When should I use Spreadsheet Direct Verification?

Spreadsheet Direct Verification fits situations like: tasks that involve Excel spreadsheets.

How do I install Spreadsheet Direct Verification in Claude Code?

Run `npx skills add HKUDS/OpenSpace --skill spreadsheet-direct-verification -a claude-code`. Or copy the skill folder (benchmarks/gdpval/skills/spreadsheet-direct-verification in HKUDS/OpenSpace) into .claude/skills/spreadsheet-direct-verification in your project. Claude Code loads it when a task matches its description.

How do I install Spreadsheet Direct Verification in Codex?

Run `npx skills add HKUDS/OpenSpace --skill spreadsheet-direct-verification -a codex`. Or copy the skill folder (benchmarks/gdpval/skills/spreadsheet-direct-verification in HKUDS/OpenSpace) into .agents/skills/spreadsheet-direct-verification in your project. Codex loads it when a task matches its description.

Can I use Spreadsheet Direct Verification in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HKUDS/OpenSpace --skill spreadsheet-direct-verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spreadsheet-direct-verification, .gemini/skills/spreadsheet-direct-verification, .github/skills/spreadsheet-direct-verification and .opencode/skills/spreadsheet-direct-verification in your project.

What does Spreadsheet Direct Verification need to run?

SKILL.md names no scripts, command-line tools or credentials: Spreadsheet Direct Verification is instructions for the agent only. Our summary lists: Python 3.

Does Spreadsheet Direct Verification access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Spreadsheet Direct Verification safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Spreadsheet Direct Verification use?

Spreadsheet Direct Verification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Spreadsheet Direct Verification use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Spreadsheet Direct Verification?

Skills that share tags, products or a category with Spreadsheet Direct Verification: Excel Workbook Editor (TokenRhythm/opensquilla, 7.1k stars), Kimi XLSX (thvroyal/kimi-skills, 238 stars), Office XLSX (open-octo/octo-agent, 125 stars) and Cc Streaming Export Safety (doccker/cc-use-exp, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spreadsheet Direct Verification?

HKUDS (a GitHub organization) maintains it in HKUDS/OpenSpace, which has 7,749 GitHub stars. The repository holds 199 skills in this directory. The repository was last updated on August 12, 2026.

Source: HKUDS/OpenSpace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.