oxen-office

Inspect, build, and verify Office documents using the oxen CLI.

39|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/trkbt10/claude-skills --skill oxen-office
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oxen-office
Source: https://github.com/trkbt10/claude-skills/tree/main/skills/oxen-office
Command: npx skills add https://github.com/trkbt10/claude-skills --skill oxen-office

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables quick and reliable inspection, construction, and verification of Office documents (PPTX, DOCX, XLSX) using a dedicated CLI, reducing manual effort and error-prone workflows.

Core Features & Use Cases

  • Inspect existing Office files to extract metadata, structure, and content.
  • Build PPTX/DOCX/XLSX from JSON specifications and verify the resulting document.
  • Preview slide/document/sheet content directly in the terminal and extract text or data for downstream processing.
  • Answer questions about file types and their contents, or generate reports from document data.

Quick Start

Analyze a sample PPTX to preview slides and verify the build output against a JSON spec.

Frequently Asked Questions about oxen-office

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inspect and extract text from Office documents using a CLI?

You can inspect Office documents using a CLI to extract metadata, structure, and text content. This CLI workflow previews PPTX, DOCX, and XLSX files directly in the terminal for immediate review and downstream processing.

Can I build PPTX, DOCX, or XLSX files from a JSON specification?

Yes, you can build PPTX, DOCX, and XLSX files from JSON specifications. The CLI workflow constructs the document and verifies the resulting build output against the original JSON spec to ensure structural accuracy.

What is the best way to verify the build results of Office files?

The best way to verify Office file build results is through a dedicated CLI. It verifies the generated PPTX, DOCX, or XLSX documents by inspecting and comparing the final output against the defined JSON specifications.

Does this CLI approach work for generating reports from existing Office document data?

Yes, this CLI approach works for generating reports from existing Office document data. It applies to scenarios where users need to preview content, extract text or data, and answer questions about PPTX, DOCX, and XLSX file contents.

Do I need any external dependencies or libraries to automate Office document verification via CLI?

No external dependencies or libraries are required to automate Office document verification via CLI. The Skill operates independently using the oxen CLI to inspect, build, and verify PPTX, DOCX, and XLSX files without additional packages.