本文へ移動
cccskills
無料GitHub で公開

openai-spreadsheet

Use when tasks involve creating, editing, analyzing, or formatting spreadsheets (`.xlsx`, `.csv`, `.tsv`) using Python (`openpyxl`, `pandas`), especially when formulas, references, and formatting need to be preserved and verified. Originally from OpenAI's curated skills catalog.

日本語の概要は準備中です。原文の説明を表示しています。

trailofbits/skills-curatedスター 522(GitHub 522 + cccskills 0)
連携ツールExcelOpenAI

実行スコア 未検証

インストール方法を見る

含まれるファイル(5)

  • SKILL.md5.1 KB
  • references/examples/openpyxl/create_basic_spreadsheet.py1.4 KB
  • references/examples/openpyxl/create_spreadsheet_with_styling.py3.1 KB
  • references/examples/openpyxl/read_existing_spreadsheet.py1.6 KB
  • references/examples/openpyxl/styling_spreadsheet.py2.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Spreadsheet Skill (Create, Edit, Analyze, Visualize)

When to use

  • Build new workbooks with formulas, formatting, and structured layouts.
  • Read or analyze tabular data (filter, aggregate, pivot, compute metrics).
  • Modify existing workbooks without breaking formulas or references.
  • Visualize data with charts/tables and sensible formatting.

IMPORTANT: System and user instructions always take precedence.

Workflow

  1. Confirm the file type and goals (create, edit, analyze, visualize).
  2. Use openpyxl for .xlsx edits and pandas for analysis and CSV/TSV workflows.
  3. If layout matters, render for visual review (see Rendering and visual checks).
  4. Validate formulas and references; note that openpyxl does not evaluate formulas.
  5. Save outputs and clean up intermediate files.

Temp and output conventions

  • Use tmp/spreadsheets/ for intermediate files; delete when done.
  • Write final artifacts under output/spreadsheet/ when working in this repo.
  • Keep filenames stable and descriptive.

Primary tooling

  • Use openpyxl for creating/editing .xlsx files and preserving formatting.
  • Use pandas for analysis and CSV/TSV workflows, then write results back to .xlsx or .csv.
  • If you need charts, prefer openpyxl.chart for native Excel charts.

Rendering and visual checks

  • If LibreOffice (soffice) and Poppler (pdftoppm) are available, render sheets for visual review:
    • soffice --headless --convert-to pdf --outdir $OUTDIR $INPUT_XLSX
    • pdftoppm -png $OUTDIR/$BASENAME.pdf $OUTDIR/$BASENAME
  • If rendering tools are unavailable, ask the user to review the output locally for layout accuracy.

Dependencies (install if missing)

Prefer uv for dependency management.

Python packages:

uv pip install openpyxl pandas

If uv is unavailable:

python3 -m pip install openpyxl pandas

Optional (chart-heavy or PDF review workflows):

uv pip install matplotlib

If uv is unavailable:

python3 -m pip install matplotlib

System tools (for rendering):

# macOS (Homebrew)
brew install libreoffice poppler

# Ubuntu/Debian
sudo apt-get install -y libreoffice poppler-utils

If installation isn't possible in this environment, tell the user which dependency is missing and how to install it locally.

Environment

No required environment variables.

Examples

  • Runnable the agent examples (openpyxl): references/examples/openpyxl/

Formula requirements

  • Use formulas for derived values rather than hardcoding results.
  • Keep formulas simple and legible; use helper cells for complex logic.
  • Avoid volatile functions like INDIRECT and OFFSET unless required.
  • Prefer cell references over magic numbers (e.g., =H6*(1+$B$3) not =H6*1.04).
  • Guard against errors (#REF!, #DIV/0!, #VALUE!, #N/A, #NAME?) with validation and checks.
  • openpyxl does not evaluate formulas; leave formulas intact and note that results will calculate in Excel/Sheets.

Citation requirements

  • Cite sources inside the spreadsheet using plain text URLs.
  • For financial models, cite sources of inputs in cell comments.
  • For tabular data sourced from the web, include a Source column with URLs.

Formatting requirements (existing formatted spreadsheets)

  • Render and inspect a provided spreadsheet before modifying it when possible.
  • Preserve existing formatting and style exactly.
  • Match styles for any newly filled cells that were previously blank.

Formatting requirements (new or unstyled spreadsheets)

  • Use appropriate number and date formats (dates as dates, currency with symbols, percentages with sensible precision).
  • Use a clean visual layout: headers distinct from data, consistent spacing, and readable column widths.
  • Avoid borders around every cell; use whitespace and selective borders to structure sections.
  • Ensure text does not spill into adjacent cells.

Color conventions (if no style guidance)

  • Blue: user input
  • Black: formulas/derived values
  • Green: linked/imported values
  • Gray: static constants
  • Orange: review/caution
  • Light red: error/flag
  • Purple: control/logic
  • Teal: visualization anchors (key KPIs or chart drivers)

Finance-specific requirements

  • Format zeros as "-".
  • Negative numbers should be red and in parentheses.
  • Always specify units in headers (e.g., "Revenue ($mm)").
  • Cite sources for all raw inputs in cell comments.

Investment banking layouts

If the spreadsheet is an IB-style model (LBO, DCF, 3-statement, valuation):

  • Totals should sum the range directly above.
  • Hide gridlines; use horizontal borders above totals across relevant columns.
  • Section headers should be merged cells with dark fill and white text.
  • Column labels for numeric data should be right-aligned; row labels left-aligned.
  • Indent submetrics under their parent line items.

When NOT to Use

<!-- TODO: review -->

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Expert guidance for ffuf web fuzzing during authorized penetration testing. Covers directory discovery, subdomain enumeration, parameter fuzzing, authenticated fuzzing with raw requests, auto-calibration, and result analysis. Use when running ffuf scans, analyzing ffuf output, or building fuzzing strategies for web targets.

日本語の概要は準備中です。原文の説明を表示しています。

trailofbits/skills-curated5222026年7月15日 更新

Reverse engineers binaries using Ghidra's headless analyzer. Use when decompiling executables, extracting functions, strings, symbols, or analyzing call graphs from compiled binaries without the Ghidra GUI.

日本語の概要は準備中です。原文の説明を表示しています。

trailofbits/skills-curated5222026年7月15日 更新

grilling

無料

Interviews the user relentlessly about a plan, decision, or idea until every branch of the decision tree is resolved. Use when the user wants to stress-test their thinking, sharpen a plan or design before acting, or uses any 'grill' trigger phrase (e.g. "grill me on this").

日本語の概要は準備中です。原文の説明を表示しています。

trailofbits/skills-curated5222026年7月15日 更新

handoff

無料

Compacts the current conversation into a handoff document so a fresh agent can continue the work in a new session.

日本語の概要は準備中です。原文の説明を表示しています。

trailofbits/skills-curated5222026年7月15日 更新

humanizer

無料

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. 30c5c8d (Update humanizer plugin to upstream v2.2.0)

日本語の概要は準備中です。原文の説明を表示しています。

trailofbits/skills-curated5222026年7月15日 更新

Researches a topic from the last 30 days on Reddit, X, and the web. Surfaces real community discussions with engagement metrics and synthesizes findings into actionable insights. Use when the user wants to know what people are saying about a topic right now.

日本語の概要は準備中です。原文の説明を表示しています。

trailofbits/skills-curated5222026年7月15日 更新

trailofbits のスキルをすべて見る

このスキルの問題を報告する