CtrlK
BlogDocsLog inGet started
Tessl Logo

docx

Create, inspect, edit, restyle, review, compare, sanitize, render, audit, and finalize professional Microsoft Word .docx documents. Use this skill whenever PilotDeck must produce or modify a Word document, preserve an existing document while making targeted changes, add comments or tracked replacements, analyze document structure or metadata, verify accessibility and layout quality, compare revisions, remove review data, or deliver a visually checked DOCX. Use only for .docx files, not legacy .doc, macro-enabled .docm, or Google Docs operations.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is a tightly written operational overview: executable commands throughout, an explicit validation/feedback workflow, and well-signaled one-level-deep references to real bundle files. It hits the top anchor on all four dimensions.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows (no "what is a DOCX" padding); sections are dense operational rules and commands where every token earns its place.

3 / 3

Actionability

Every workflow ships copy-paste-ready bash invocations with concrete flags (e.g. `inspect --input ... --out ...`, `audit --profile final`), fully executable rather than pseudocode.

3 / 3

Workflow Clarity

The numbered "Non-negotiable operating contract" sequences operations with explicit validation checkpoints and a fix-then-revalidate feedback loop, and the "Delivery gate" is a checklist — matching the top anchor for risky batch/document operations.

3 / 3

Progressive Disclosure

The routing table clearly signals one-level-deep references to real bundle files ([workflows.md](references/workflows.md), [design-and-layout.md](references/design-and-layout.md), [specifications.md](references/specifications.md), [ooxml-and-safety.md](references/ooxml-and-safety.md)) while keeping SKILL.md an actionable overview.

3 / 3

Total

12

/

12

Passed

Description

100%

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

This is an exemplary description: third-person voice, dense with concrete actions, explicit trigger guidance, and clear scope boundaries that prevent mis-routing. Every dimension lands at the top anchor.

DimensionReasoningScore

Specificity

The description enumerates ten concrete verbs ("Create, inspect, edit, restyle, review, compare, sanitize, render, audit, and finalize") applied to .docx documents, matching the multiple-specific-actions anchor exactly.

3 / 3

Completeness

It explicitly states what (the action list) and when ("Use this skill whenever PilotDeck must produce or modify a Word document...") with an explicit scope exclusion clause, satisfying both what and when.

3 / 3

Trigger Term Quality

It covers natural user-facing terms — "Word document", ".docx", "DOCX", "comments or tracked replacements", "accessibility", "compare revisions", "review data" — that a user would plausibly say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The explicit "Use only for .docx files, not legacy .doc, macro-enabled .docm, or Google Docs operations" clause carves a clear niche unlikely to conflict with adjacent skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
OpenBMB/PilotDeck
Reviewed

Table of Contents

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.