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

85%

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-structured skill body with a copy-paste-ready workflow and an explicit verification check. The only drag is conciseness: a rationale section and build-tooling footnote add maintainer detail that the executing agent does not need, and one XLSX caveat is repeated.

Suggestions

Trim or remove the 'Why this exists' section and the 'Building blocks: python-docx, openpyxl, python-pptx... build_templates.py' footnote; move that maintainer context to a separate doc or drop it.

State the multi-row XLSX guidance once (either in the template block or the reverse-handoff list) rather than repeating it across the `commonly-data.xlsx` section.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence (no concept explanations, a tight comparison table, precise placeholder keys), but the 'Why this exists' rationale and the build-tooling footnote ('python-docx, openpyxl, and python-pptx... build_templates.py') are maintainer-facing detail that does not earn its place for executing the skill, and the multi-row XLSX caveat is stated twice.	2 / 3
Actionability	It provides a fully executable, copy-paste-ready bash flow — concrete template path, a complete `--data` JSON file, the `officecli merge` command, and a `view` check — plus exact placeholder keys for each of the three templates.	3 / 3
Workflow Clarity	The flow is a clear numbered sequence (pick template → write data → merge → view → attach) and includes an explicit verification step (`officecli view ... \| grep -E '\{\{[a-z_]+\}\}'` to catch leftover placeholders) with explained failure modes (the upload stub guard).	3 / 3
Progressive Disclosure	The skill is a single well-organized SKILL.md with no bundle files and no nested references; sections (when-to-use table, three templates, flow, verifying, reverse handoff) are clearly headed and the inline placeholder keys are small enough to belong in the body.	3 / 3
	Total	11 / 12 Passed

Description

90%

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-structured description with explicit triggers, clear what/when coverage, and effective negative-routing for distinctiveness. The only meaningful weakness is the second-person phrasing, which violates the third-person-voice guideline and costs one specificity point.

Suggestions

Rewrite in third person to satisfy the voice guideline, e.g. 'Produces a polished, Commonly-branded deliverable... when the agent does not have specific brand guidance from the user.'

Drop the parenthetical 'so you populate content with one merge call instead of 30 individual `officecli set` commands' from the description; that rationale fits the body, not the trigger.

Dimension	Reasoning	Score
Specificity	The description names concrete actions ('producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck)', 'Routes to `officecli merge`', 'populate content with one merge call') that would normally score 3, but it uses second-person voice ('you do not have specific brand guidance from the user'), which per the judging guidelines reduces specificity by one point.	2 / 3
Completeness	It explicitly answers both what (produces Commonly-branded deliverables via `officecli merge` with pre-built templates) and when ('Use this skill when producing... you do not have specific brand guidance' plus an explicit 'Trigger on:' list), with clear negative routing to other skills.	3 / 3
Trigger Term Quality	It lists a strong set of natural trigger phrases users would actually say — 'write me a brief', 'one-pager', 'memo', 'data sheet', 'status matrix', 'short deck', 'summary deck', 'closing slide', 'final deliverable' — giving good coverage across the three deliverable shapes.	3 / 3
Distinctiveness Conflict Risk	It carves a clear niche (everyday Commonly-branded business deliverables) and explicitly excludes adjacent cases — fundraising decks, academic papers, financial models — routing each to a named sibling skill, making conflicts unlikely.	3 / 3
	Total	11 / 12 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: 69b6005

Reviewed: about 19 hours 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.