본문으로 건너뛰기
cccskills
무료GitHub에 공개

xlsx-processing-openai

Toolkit for comprehensive Spreadsheet reading, creation, editing, and analysis with visual quality control. Use to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing tabular data, (3) Modifying existing spreadsheets while preserving formulas, (4) Building financial models with proper formatting, (5) Data visualization with in-sheet charts, or any other spreadsheet tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구Excel

실행 점수 미검증

설치 방법 보기

포함된 파일(7)

  • SKILL.md5.3 KB
  • LICENSE.txt10.5 KB
  • README.md462 B
  • 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 Codex 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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Public-safe preliminary screen for challenges to the impartiality of an AI evaluator, LLM-as-a-judge, decision-support agent, or adjudicative system based on prior outputs, suspected bias, unstable reasoning, or self-reinforcing memory. Use when asked whether an AI should be recused, disqualified, replaced, audited, or escalated. Does not decide real cases or claim that human judicial-recusal doctrine automatically applies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

lawve-ai/awesome-legal-skills8942026년 10월 20일 업데이트

Creates an Agent Authority Charter for enterprise or regulated AI agents before deployment. Use this Skill when a user needs to define what an AI agent is allowed to do, who delegated authority to it, what actions are permitted or prohibited, when human approval is required, what evidence must be preserved, and how the agent can be suspended, revoked, or escalated.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

lawve-ai/awesome-legal-skills8942026년 10월 20일 업데이트

EU AI Act Knowledge Engine — authoritative regulatory Q&A grounded in 70 official EU source documents (including the 2026 Commission draft guidelines on Art. 6 high-risk classification — general principles, Annex I, Annex III). Answers any question about the AI Act with article-level citations from the full regulation text, Commission guidelines, EDPB/EDPS opinions, codes of practice, harmonised standards, FRIA guides, incident templates, and sector-specific guidance. This skill should be used when the user asks about the "EU AI Act", "AI Act regulation", "Regulation 2024/1689", "KI-Verordnung", asks to "explain an AI Act article", "what does Article X say", "AI Act requirements", "AI Act penalties", "AI Act timeline", "GPAI obligations", "high-risk AI", "prohibited AI practices", "AI Act and GDPR", "fundamental rights impact assessment", "AI Act standards", "AI Act national implementation", "AI literacy", "serious incident reporting", "Digital Omnibus", "AI regulatory sandbox", or any question about EU artificial intelligence regulation. Also triggers on German terms: "KI-Gesetz", "KI-Verordnung", "Hochrisiko-KI", "KI-Kompetenz", "Grundrechte-Folgenabschaetzung", "GPAI-Verhaltenskodex". For assessment workflows that produce a classification decision rather than a knowledge answer, offer to run a structured risk-tier classification in-session.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

lawve-ai/awesome-legal-skills8942026년 10월 20일 업데이트

This skill builds a structured audit trail of an AI-assisted task: what the tool was asked to do, what materials it was given, what it produced, how the output was verified, and what was ultimately relied upon. It documents the workflow for supervision and later review without ruling on privilege or disclosure, so the record stays accurate rather than self-serving.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

lawve-ai/awesome-legal-skills8942026년 10월 20일 업데이트

Use this skill when the user wants an AI governance, legal-risk, privacy, compliance, procurement, or vendor-risk review of an internal AI use case, an AI product feature, an LLM workflow, or a third-party AI vendor. The skill asks intake and clarifying questions first when facts or evidence are missing, identifies required documentation and missing evidence, maps the use case to AI governance frameworks and applicable legal domains, and produces a preliminary or final governance review with scorecards, findings, owners, remediation actions, and follow-up questions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

lawve-ai/awesome-legal-skills8942026년 10월 20일 업데이트

Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable. Produces a multi-page website (default), a single-page interactive site, a Microsoft Word document, a PowerPoint deck, or a LaTeX/PDF. Use whenever a user has a stress-test result, ambiguity audit, or "where will this be litigated" scenarios and wants to publish, present, or share them. Triggers on "publish the audit," "make a report from this," "turn this into a website / deck / brief / Word doc," "make a Netlify site," "build slides of these ambiguities," "render the scenarios," "package this stress test," "produce a LaTeX version," and similar. Pairs with the ambiguity-stress-test skill (the underlying analysis) but works on any structured or semi-structured ambiguity analysis. Visual design is opinionated but the user can override colors, fonts, and brand label. Most formats need Python and a writable filesystem; single-file HTML works where the host has neither.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

lawve-ai/awesome-legal-skills8942026년 10월 20일 업데이트

lawve-ai의 스킬 모두 보기

이 스킬의 문제 신고