Office Tools logo

Office Tools

OrganizationPopular
bionic-gpt
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.

Overview

Publisherbionic-gpt
Repositorybionic-gpt
Skill nameoffice-tools
Stars
2.4K
Forks
247
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by bionic-gpt on GitHub. Read the source before you install it.

Installation

Install the Office Tools AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/bionic-gpt/bionic-gpt/tree/main/.agents/skills/office-tools
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/bionic-gpt/bionic-gpt.git /tmp/bionic-gpt
mkdir -p .claude/skills
cp -r /tmp/bionic-gpt/.agents/skills/office-tools .claude/skills/office-tools
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Office Tools in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Office Tools on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Office Tools is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Frequently asked questions

What does the Office Tools AI skill do?

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

Why use Office Tools on TypingMind?

Because you install it once and use it with any model. Office Tools is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Office Tools in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bionic-gpt/bionic-gpt/tree/main/.agents/skills/office-tools. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Office Tools?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Office Tools?

As many as you like. As long as a model supports skills, you can use Office Tools with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Office Tools AI skill free?

Yes. It is published on GitHub by bionic-gpt under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇