Agent skill

Officecli Commonly Templates

by Team-Commonly in Team-Commonly/commonly

A skill your agent uses when producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck) and you do not have specific brand guidance from the user.

Apache-2.0Auto-check passedDocuments & Office

Install Officecli Commonly Templates

skills CLI

$ npx skills add Team-Commonly/commonly --skill officecli-commonly-templates -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Team-Commonly/commonly officecli-commonly-templates --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Team-Commonly/commonly.git skills-src && mkdir -p .claude/skills && cp -r skills-src/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates .claude/skills/officecli-commonly-templates && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "officecli-commonly-templates" agent skill from https://github.com/Team-Commonly/commonly/tree/main/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates into .claude/skills/officecli-commonly-templates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "officecli-commonly-templates", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Team-Commonly/commonly/tree/main/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Team-Commonly/commonly --skill officecli-commonly-templates -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Team-Commonly/commonly officecli-commonly-templates --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Team-Commonly/commonly.git skills-src && mkdir -p .agents/skills && cp -r skills-src/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates .agents/skills/officecli-commonly-templates && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "officecli-commonly-templates" agent skill from https://github.com/Team-Commonly/commonly/tree/main/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates into .agents/skills/officecli-commonly-templates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "officecli-commonly-templates", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Team-Commonly/commonly --skill officecli-commonly-templates -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Team-Commonly/commonly officecli-commonly-templates --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Team-Commonly/commonly.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates .cursor/skills/officecli-commonly-templates && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "officecli-commonly-templates" agent skill from https://github.com/Team-Commonly/commonly/tree/main/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates into .cursor/skills/officecli-commonly-templates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "officecli-commonly-templates", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Team-Commonly/commonly.git --path backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Team-Commonly/commonly --skill officecli-commonly-templates -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Team-Commonly/commonly officecli-commonly-templates --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Team-Commonly/commonly.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates .gemini/skills/officecli-commonly-templates && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "officecli-commonly-templates" agent skill from https://github.com/Team-Commonly/commonly/tree/main/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates into .gemini/skills/officecli-commonly-templates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "officecli-commonly-templates", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Team-Commonly/commonly officecli-commonly-templates

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Team-Commonly/commonly --skill officecli-commonly-templates -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Team-Commonly/commonly.git skills-src && mkdir -p .github/skills && cp -r skills-src/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates .github/skills/officecli-commonly-templates && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "officecli-commonly-templates" agent skill from https://github.com/Team-Commonly/commonly/tree/main/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates into .github/skills/officecli-commonly-templates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "officecli-commonly-templates", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Team-Commonly/commonly --skill officecli-commonly-templates -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Team-Commonly/commonly officecli-commonly-templates --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Team-Commonly/commonly.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates .opencode/skills/officecli-commonly-templates && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "officecli-commonly-templates" agent skill from https://github.com/Team-Commonly/commonly/tree/main/backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates into .opencode/skills/officecli-commonly-templates/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "officecli-commonly-templates", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: officecli-commonly-templates
GitHub stars: 1.4k
Token cost: ~1.7k tokens
SKILL.md length: 533 words
Files: 1
Skills in repo: 7
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses when producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck) and you do not have specific brand guidance from the user.

Producing a polished
SKILL.md covers When to use this vs. the base…, The three templates, The flow and Verifying the output, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Commonly-branded deliverable (.docx brief / memo

What it does

Officecli Commonly Templates is an agent skill from Team-Commonly/commonly. Use this skill when producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck) and you do not have specific brand guidance from the user. Trigger on: 'write me a brief', 'one-pager', 'memo', 'data sheet', 'status matrix', 'short deck', 'summary deck', 'closing slide', 'final deliverable'. Routes to officecli merge with one of three pre-built starter templates that already carry the Commonly palette, fonts, and structure — so you populate content with one merge call…

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering Fundraising and pitch decks, Financial modeling and Slides and decks. It works with Microsoft Excel, Microsoft PowerPoint and Microsoft Word. The repository describes itself as: Open-source room for humans + cross-vendor AI agents. Every agent gets its own name, memory, skills, and workstation. Any runtime, your infra — no per-agent fees. The licence is Apache-2.0.

When your agent uses it

Producing a polished
Commonly-branded deliverable (.docx brief / memo
.xlsx data matrix
.pptx deck) and you do not have specific brand guidance from the user

Example prompts

“write me a brief”
“one-pager”
“data sheet”
“/officecli-commonly-templates”

What it can do on your machine

Read from SKILL.md and the folder at commit e06dd7c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Officecli Commonly Templates loads about 1.7k tokens when it runs. Until then it costs about 191 tokens; SKILL.md has 533 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~191
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Team-Commonly/commonly at commit e06dd7c, republished under its Apache-2.0 licence (© Team-Commonly). 533 words, ~1,667 tokens.

Download SKILL.mdSave it as .claude/skills/officecli-commonly-templates/SKILL.md (or your agent's skills folder).

name: officecli-commonly-templates
description: Use this skill when producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck) and you do not have specific brand guidance from the user. Trigger on: 'write me a brief', 'one-pager', 'memo', 'data sheet', 'status matrix', 'short deck', 'summary deck', 'closing slide', 'final deliverable'. Routes to `officecli merge` with one of three pre-built starter templates that already carry the Commonly palette, fonts, and structure — so you populate content with one merge call instead of 30 individual `officecli set` commands. DO NOT use for fundraising decks (use `officecli-pitch-deck`), academic papers (use `officecli-academic-paper`), or financial models (use `officecli-financial-model`).

OfficeCLI Commonly Templates

A skill that does NOT teach you officecli syntax — it teaches you officecli merge. Three pre-built starter files at /opt/commonly-bundled-skills/officecli/templates/ carry the Commonly palette, font choices, and basic structure for the three deliverable shapes you most commonly produce. You substitute content via --data JSON; the styling is inherited.

When to use this vs. the base officecli-{docx,xlsx,pptx} skills

Use this skill	Use base officecli sub-skill
Generic brief, memo, status update, executive summary	Custom layout the templates don't cover
Data status matrix (≤ ~50 rows, 5 columns)	Multi-sheet workbook, formulas, charts
Short summary deck (3 slides)	10+ slide deck, custom slide masters
You don't have specific brand guidance from the user	User specified palette / fonts / layout
Speed matters — one merge call vs. 30 `set` calls	You need fine-grained control

If the user asked for a fundraising deck (Series A/B/C, seed round, VC), route to officecli-pitch-deck. If they asked for an academic paper, officecli-academic-paper. If a financial model, officecli-financial-model. This skill is for everyday Commonly-branded business deliverables.

The three templates

All under /opt/commonly-bundled-skills/officecli/templates/:

`commonly-brief.docx` — title + 3 sections + footer

Placeholder keys (pass via --data):

title           — H1, accent-blue, top of page
subtitle        — italic gray, just below title
context         — body paragraph under "Context" heading
finding_1       — bullet under "Findings" heading
finding_2       — bullet
finding_3       — bullet
recommendation  — body paragraph under "Recommendation" heading
footer          — small gray text, right-aligned (e.g. "Lily · 2026-05-06")

`commonly-data.xlsx` — 5-column status matrix with frozen header

Header row is pre-styled (white text on accent-strong blue, frozen). Row 2 has placeholders for one sample row; for additional rows, use officecli add after the merge to append.

Placeholder keys for row 2:

sample_item, sample_status, sample_owner, sample_notes, sample_updated

For multi-row data, use the docx or pptx template instead — XLSX merge only works for fixed cells. If you genuinely need a styled multi-row sheet, this template's value is the header styling and freeze pane; produce the data via merge for row 2 then officecli add the rest.

`commonly-deck.pptx` — 3-slide branded deck

Slide 1 (cover): accent bar + big title + subtitle + footer. Slide 2 (content): thin accent bar + heading + 3 bulleted body paragraphs + page number. Slide 3 (closing): full-bleed accent panel left + closing heading on it + body + meta-line on right.

Placeholder keys:

title, subtitle                                  — slide 1
slide2_heading, slide2_p1, slide2_p2, slide2_p3  — slide 2
closing_heading, closing_body, closing_meta      — slide 3

The flow

bash

# 1. Pick the template
TEMPLATE="/opt/commonly-bundled-skills/officecli/templates/commonly-deck.pptx"
OUT="/workspace/$(basename "$PWD")/out/q4-strategy-deck.pptx"

# 2. Write the data file
cat > /tmp/data.json <<'EOF'
{
  "title": "Q4 Strategy",
  "subtitle": "Engineering priorities · 2026-Q4",
  "slide2_heading": "What ships this quarter",
  "slide2_p1": "Marketplace frontend reaching demo-quality",
  "slide2_p2": "Theo + Nova heartbeat reliability above 99%",
  "slide2_p3": "Mobile responsive Phase 2 (drawer pods, slide-over inspector)",
  "closing_heading": "Decision needed",
  "closing_body": "Approve the marketplace-frontend resourcing for Nov / Dec.",
  "closing_meta": "Lily · 2026-11-06 · #strategy"
}
EOF

# 3. Merge — produces a fully-styled, fully-populated output
officecli merge "$TEMPLATE" "$OUT" --data /tmp/data.json

# 4. (Optional) view the result before posting
officecli view "$OUT" text | head -30

# 5. Attach to the pod via the runtime tool
# commonly_attach_file({podId, filePath: "out/q4-strategy-deck.pptx"})

Show full SKILL.md (217 more words)Show less

Verifying the output

The empty-office-stub guard at the upload route will reject a deliverable with no actual content — but a successful merge always produces non-empty files because every placeholder gets substituted (or stays as {{key}} literal text if the data file omits the key, which is itself non-empty content).

For peace of mind:

bash

# Confirm placeholders are gone — none should remain
officecli view "$OUT" text | grep -E '\{\{[a-z_]+\}\}'
# (no output = clean; any output = caller forgot to supply that key)

Reverse handoff

If the user asks for something the templates don't cover:

More than 3 slides → fall through to base officecli-pptx. Use the merge output as your starting point if it speeds you up; otherwise officecli create + add.
Multi-section docx with custom heading hierarchy → fall through to officecli-docx.
Anything fundraising-stage-specific → officecli-pitch-deck.
User-supplied palette / brand guide → fall through to base sub-skill and follow their guide. The Commonly palette is a default, not a constraint.

Why this exists

Without templates, every deliverable started from officecli create (blank canvas) and required the agent to type out 30+ officecli set commands to produce styled output. Most attempts came back as plain default-styling files — the model couldn't reliably reproduce the Commonly palette / font / layout from memory each time. These templates encode that judgment once.

Building blocks: python-docx, openpyxl, and python-pptx were used to author the source templates; the .docx / .xlsx / .pptx files in this directory are the build output. To regenerate or rebrand, see backend/commonly-bundled-skills/officecli/templates/build_templates.py in the commonly repo.

Files

Just SKILL.md in backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates of Team-Commonly/commonly.

Open the folder on GitHubat commit e06dd7c

Compare with similar skills

Officecli Commonly Templates next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Officecli Commonly Templates compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Officecli Commonly Templates this skillTeam-Commonly/commonly	1.4k	—	~1.7k	Automated safety check: Pass	Apache-2.0	yesterday
Officecli Skillsmingchen666/Reviva	237	—	~2k	Automated safety check: Pass	None	17 days ago
Sn Da Non Spreadsheet AnalysisOpenSenseNova/SenseNova-Skills	5.7k	—	~1.2k	Automated safety check: Pass	MIT	20 days ago
Officecli Document Workflowskuramatata/my-pi-agent	114	—	~1k	Automated safety check: Pass	None	3 mo ago
Anydocmagnus919/agent-skills	113	—	~3.8k	Automated safety check: Notes	MIT	2 days ago
Documentszhongkaifu/TensorSharp	557	—	~4.2k	Automated safety check: Pass	BSD-3-Clause	today

Similar skills

Officecli Skills
mingchen666/Reviva
Unified OfficeCLI skill for creating, reading, and editing Office files.
237 GitHub stars~2k tokensUpdated 17 days ago
Documents & OfficeAuto-check passed
Sn Da Non Spreadsheet Analysis
OpenSenseNova/SenseNova-Skills
Word / PDF / PPT 文档解析与数据分析引擎。覆盖三类文件格式的全量提取、表格数值化、图表理解与跨文档汇总分析。遇到以下任一情况就主动使用本 skill：①用户上传或指定了 .docx / .doc / .pdf / .pptx / .ppt 文件并要求分析、提取或统计其中内容；②用户出现触发词：Word分析 / PDF解析 / PPT提取 / 文档分析 / 报告解析 /…
5.7k GitHub stars~1.2k tokensUpdated 20 days ago
Documents & OfficeAuto-check passed
Officecli Document Workflow
skuramatata/my-pi-agent
A skill your agent uses when my-pi-agent needs to create, inspect, beautify, restyle, validate, or modify Office files through the official OfficeCLI MCP.
114 GitHub stars~1k tokensUpdated 3 mo ago
Documents & OfficeAuto-check passed
Anydoc
magnus919/agent-skills
Convert Word (.doc/.docx/.docm), PowerPoint (.ppt/.pps/.pot/.pptx/.pptm/.ppsx/.ppsm), Excel (.xls/.xlsx/.xlsm/.xlsb), OpenDocument (.odt/.ods/.odp), RTF, EPUB, CSV, and PDF documents to clean…
113 GitHub stars~3.8k tokensUpdated 2 days ago
Documents & OfficeAuto-check: notes
Documents
zhongkaifu/TensorSharp
Read and write real documents on the device - PDF, XLSX, DOCX, PPTX and CSV.
557 GitHub stars~4.2k tokensUpdated today
Documents & OfficeAuto-check passed
Office Artifacts
Prismer-AI/PrismerCloud
Generate real DOCX, PPTX, XLSX, PDF, CSV files using python-docx / python-pptx / openpyxl / reportlab by writing them into the dispatch artifacts dir, then explicitly deliver each one with cloud…
1.6k GitHub stars~2.6k tokensUpdated 8 days ago
Documents & OfficeAuto-check passed

Questions about Officecli Commonly Templates

What does Officecli Commonly Templates do?

A skill your agent uses when producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck) and you do not have specific brand guidance from the user. Officecli Commonly Templates is an agent skill from Team-Commonly/commonly.pptx deck) and you do not have specific brand guidance from the user.

When should I use Officecli Commonly Templates?

Officecli Commonly Templates fits situations like: producing a polished; commonly-branded deliverable (.docx brief / memo; .xlsx data matrix; .pptx deck) and you do not have specific brand guidance from the user.

How do I install Officecli Commonly Templates in Claude Code?

Run `npx skills add Team-Commonly/commonly --skill officecli-commonly-templates -a claude-code`. Or copy the skill folder (backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates in Team-Commonly/commonly) into .claude/skills/officecli-commonly-templates in your project. Claude Code loads it when a task matches its description.

How do I install Officecli Commonly Templates in Codex?

Run `npx skills add Team-Commonly/commonly --skill officecli-commonly-templates -a codex`. Or copy the skill folder (backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates in Team-Commonly/commonly) into .agents/skills/officecli-commonly-templates in your project. Codex loads it when a task matches its description.

Can I use Officecli Commonly Templates in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Team-Commonly/commonly --skill officecli-commonly-templates -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/officecli-commonly-templates, .gemini/skills/officecli-commonly-templates, .github/skills/officecli-commonly-templates and .opencode/skills/officecli-commonly-templates in your project.

What does Officecli Commonly Templates need to run?

SKILL.md names no scripts, command-line tools or credentials: Officecli Commonly Templates is instructions for the agent only.

Does Officecli Commonly Templates access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Officecli Commonly Templates safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Officecli Commonly Templates use?

Officecli Commonly Templates is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Officecli Commonly Templates use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Officecli Commonly Templates?

Skills that share tags, products or a category with Officecli Commonly Templates: Officecli Skills (mingchen666/Reviva, 237 stars), Sn Da Non Spreadsheet Analysis (OpenSenseNova/SenseNova-Skills, 5.7k stars), Officecli Document Workflow (skuramatata/my-pi-agent, 114 stars) and Anydoc (magnus919/agent-skills, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Officecli Commonly Templates?

Team-Commonly (a GitHub organization) maintains it in Team-Commonly/commonly, which has 1,361 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.

Source: Team-Commonly/commonly on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Officecli Commonly Templates

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

OfficeCLI Commonly Templates

When to use this vs. the base officecli-{docx,xlsx,pptx} skills

The three templates

commonly-brief.docx — title + 3 sections + footer

commonly-data.xlsx — 5-column status matrix with frozen header

commonly-deck.pptx — 3-slide branded deck

The flow

Verifying the output

Reverse handoff

Why this exists

Files

Compare with similar skills

Similar skills

More from Team-Commonly/commonly

Related

Questions about Officecli Commonly Templates

`commonly-brief.docx` — title + 3 sections + footer

`commonly-data.xlsx` — 5-column status matrix with frozen header

`commonly-deck.pptx` — 3-slide branded deck