# Office Tools

> Regenerate the built-in Office OpenAPI specs from a selected Archipelago ref. Use when the Office container or its upstream operation surface is updated.

- Skill: `bionic-gpt/office-tools` (Agent Skill)
- Install (CLI): `npx skillmds@latest add bionic-gpt/office-tools`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bionic-gpt/office-tools/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: bionic-gpt (https://skillmd.com/u/bionic-gpt)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bionic-gpt/office-tools

---


# Office tools

Use this skill only when the user asks to update or regenerate the built-in
Office tools. The generated specifications are compiled into Bionic and are
available system-wide; they are not database integrations and do not need a
migration.

## Regenerate specs

From the repository root, run:

```bash
cargo run -p dagger-pipeline -- \
  generate-office-specs \
  --archipelago-ref main
```

Pass a tag or commit instead of `main` when the Office image is built from a
specific upstream revision. The command stages the selected Archipelago
source, generates and validates the three OpenAPI documents, and writes them
to:

```text
crates/tool-runtime/system_specs/office/
```

The files are source-controlled runtime resources. Review their diff after
generation and ensure the matching Office container is built from the same
Archipelago ref.

## Verification

Check the generated documents and focused Rust code with:

```bash
git diff --check
cargo test -p tool-runtime
cargo check -p tool-runtime
```

Do not create a database migration or insert rows into the integrations tables
for these specs. Do not publish or deploy the Office image unless the user
explicitly asks for that separately.