CtrlK
BlogDocsLog inGet started
Tessl Logo

report-to-google-doc

Narrow conversion skill. Invoke only when the user explicitly asks to convert an existing local or blob-hosted HTML analytics report into a Google Doc, DOCX, or shareable document.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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.

A lean, highly actionable skill body that delegates complex logic to a bundled helper, sequences a multi-step conversion with explicit preflight/upload validation gates and repair feedback loops, and keeps operational guidance organized without teaching known concepts. It is a strong example of an efficient instruction-and-code skill.

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanations of concepts Claude already knows (no "what is HTML/DOCX/Drive" padding); every section — Workflow, Standards, Repairs, Local Checks — is task-specific guidance where each token earns its place, matching anchor 3 rather than the padded anchor 2 example.

3 / 3

Actionability

It provides fully executable, copy-paste-ready guidance: the exact `python3 .../report_to_google_doc_plan.py` invocation with absolute paths (the script is a real bundle file), a concrete `mcp__codex_apps__google_drive._upload_file` JSON call, and specific required output filenames, matching anchor 3.

3 / 3

Workflow Clarity

The six-step Workflow has an explicit validation gate ("Do not upload until preflight_checks.json has status: \"passed\" with zero errors"), a dedicated Validate step with a comparison checklist, and a Repairs table that supplies fix-after-failure feedback loops, satisfying anchor 3 and avoiding the destructive/batch cap.

3 / 3

Progressive Disclosure

SKILL.md acts as an overview that delegates heavy implementation to a real one-level-deep bundle (scripts/report_to_google_doc_plan.py plus the html_parser/rendering/docx_writer/quality modules), with well-organized sections and no nested reference chains, matching anchor 3.

3 / 3

Total

12

/

12

Passed

Description

75%

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 precise, well-gated description that clearly defines both its narrow purpose and explicit invocation trigger, giving it strong completeness and distinctiveness. Trigger-term naturalness is slightly weakened by the internal term "blob-hosted" and a few missing common variations.

Suggestions

Drop or demote "blob-hosted" (e.g., "downloaded or remote HTML report") so the trigger terms are all phrased the way a user would actually say them.

Add common variations such as "Google Docs" and "Word document" to broaden natural keyword coverage.

Consider naming a second concrete action beyond "convert" (e.g., "render and upload") to lift specificity from anchor 2 toward anchor 3.

DimensionReasoningScore

Specificity

The description names a concrete domain and action — "convert an existing local or blob-hosted HTML analytics report into a Google Doc, DOCX, or shareable document" — but the action is a single verb (convert) split across output formats rather than the multiple distinct operations (extract/fill/merge) that anchor 3 calls for, so it sits at anchor 2.

2 / 3

Completeness

It states both what (convert an HTML analytics report into Google Doc/DOCX/shareable document) and an explicit when clause — "Invoke only when the user explicitly asks to convert ..." — which satisfies the anchor 3 requirement for an explicit trigger, avoiding the cap described for missing "Use when..." guidance.

3 / 3

Trigger Term Quality

It includes natural user terms like "Google Doc", "DOCX", "shareable document", and "HTML analytics report", but "blob-hosted" is internal jargon a user would not say, and common variations such as the plural "Google Docs" or "Word document" are absent, matching anchor 2.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and specific — HTML analytics reports to Google Doc/DOCX — and the trigger is gated to an explicit user request, making overlap with unrelated skills unlikely, matching anchor 3.

3 / 3

Total

10

/

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
XiaomiMiMo/MiMo-Code
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.