officecli-commonly-templates

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`).

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

83%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced body with a complete merge flow and verification checkpoint — strong on actionability and workflow clarity. The main weakness is progressive disclosure: no bundle files ship with the skill, while the body leans on external paths and inlines all template/placeholder detail that could be split into reference files.

Suggestions

Ship the three starter templates (commonly-brief.docx, commonly-data.xlsx, commonly-deck.pptx) as bundle assets so the referenced `/opt/commonly-bundled-skills/officecli/templates/` files actually exist alongside the skill, or repoint paths to the bundled copies.

Move the per-template placeholder-key listings into one-level-deep reference files (e.g. references/templates.md) and keep SKILL.md as a concise overview pointing to them, improving progressive disclosure and token efficiency.

Trim the 'Why this exists' paragraph and the XLSX multi-row aside to the essential sentence each; they explain background Claude can largely infer.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence (placeholder keys, a copy-paste flow, no padding about what .docx/.pptx are); minor over-explanation in 'Why this exists' and the XLSX multi-row aside that could be trimmed.	4 / 5
Actionability	Fully executable: concrete absolute template paths, a complete `--data` JSON file, the exact `officecli merge` invocation, a verification `grep` command, and per-template placeholder key listings — copy-paste ready and covering the common cases.	5 / 5
Workflow Clarity	The flow is a clearly numbered 5-step sequence (pick template, write data, merge, view, attach) with an explicit verification step ('Verifying the output' section with a guard explanation and a placeholder-leak grep) and a reverse-handoff section for error recovery when templates don't fit.	5 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent), yet the body references template files under `/opt/commonly-bundled-skills/officecli/templates/` and a repo `build_templates.py` that are not part of this skill's bundle; the per-template placeholder detail is all inlined in SKILL.md with no one-level-deep references, so structure is present but not split across files.	3 / 5
	Total	17 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-targeted description that crisply states what it does and when to use it, with explicit trigger phrases and clear negative-routing to sibling skills. It loses a point on specificity only because the concrete 'actions' are essentially a single merge routing rather than a broad set of operations.

Dimension	Reasoning	Score
Specificity	Names the domain (Commonly-branded .docx/.xlsx/.pptx deliverables) and a concrete action (populate content via `officecli merge` with `--data` JSON instead of 30 `set` calls), but the 'actions' are more about routing into a single command than a comprehensive list of operations.	4 / 5
Completeness	Explicitly answers both 'what' (routes to `officecli merge` with one of three pre-built starter templates carrying Commonly palette/fonts/structure) and 'when' (an explicit 'Use this skill when...' clause plus 'Trigger on:' phrases and concrete DO-NOT-use exclusions).	5 / 5
Trigger Term Quality	Comprehensive natural triggers users would actually say ('write me a brief', 'one-pager', 'memo', 'data sheet', 'status matrix', 'short deck', 'closing slide', 'final deliverable') covering synonyms and deliverable shapes.	5 / 5
Distinctiveness Conflict Risk	Clear niche with explicit negative-routing (DO NOT use for fundraising decks / academic papers / financial models, naming the alternative skill for each), minimizing the chance it triggers for the wrong skill.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Team-Commonly/commonly
Path: backend/commonly-bundled-skills/officecli/skills/officecli-commonly-templates/SKILL.md
Commit: e701dba

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.