CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docx-feedback-tracker

Automatically detect DOCX track-changes history, version rounds, and author feedback to generate a Markdown modification explanation file when you run it on one or more DOCX versions.

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/docx-feedback-tracker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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.

The usage examples and implementation details are genuinely concrete, but the skill is undermined by an entry script that is absent from the bundle, Windows-style paths, contradictory output-naming guidance, and roughly half the body being generic validation/safety boilerplate that adds no skill-specific value.

Suggestions

Ship the actual entry script in the bundle (e.g. scripts/docx_feedback_tracker.py) or correct the path so the documented commands are executable; also use POSIX paths in examples ('path/file.docx').

Delete or drastically trim the generic boilerplate sections (When Not to Use, Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Quick Validation) — they carry no skill-specific information.

Resolve the output-name contradiction: the grouping rule says '<topic>-change-log.md' while Output Contract and Quick Validation say 'docx_feedback_tracker_result.md'; pick one convention. Add a simple validation step (e.g. check the generated Markdown exists and rounds were detected) for --dir batch runs.

DimensionReasoningScore

Conciseness

Roughly half the body is generic template boilerplate with no skill-specific content: 'When Not to Use' ('Do not use this skill when the required source data, identifiers, files, or credentials are missing'), 'Required Inputs', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', and a 'Quick Validation' section that literally states 'No local script validation step is required for this skill.' This matches the 2-anchor ('several unnecessary explanations or padded sections'). Not a 3 because the padding is extensive rather than occasional.

2 / 5

Actionability

Concrete bash commands cover the three main modes (single file, multi-version, --dir batch) and implementation details are specific (w:ins/w:del markers, -vN/-N suffix rules, timestamp fallback), but the commands are not actually executable as delivered: the entry script 'script/docx_feedback_tracker.py' does not exist anywhere in the bundle, and the examples use Windows backslash paths ('"path\file.docx"'). This fits the 3-anchor ('missing key details'). Not a 4 because a broken entry-point reference is more than a minor gap.

3 / 5

Workflow Clarity

Usage modes are sequenced and the implementation pipeline (group by topic, order rounds, parse OOXML, diff fallback, generate output) is described, but the 'Recommended Workflow' section is generic filler ('Validate the request against the skill boundary'), there is no validation/verification step for the batch --dir mode (capping workflow clarity at 3 per the guidelines), and the output contract contradicts itself: 'only one <topic>-change-log.md per series' vs. 'prefer a deterministic output name such as docx_feedback_tracker_result.md'. Not a 2 because concrete command examples for each mode are present.

3 / 5

Progressive Disclosure

The two existing bundle files are well-signaled one level deep ('Template reference: assets/change-log-template.md', 'OOXML reference: references/docx-tracked-changes.md'), but the core referenced path — the entry script 'script/docx_feedback_tracker.py' — is missing from the bundle, and no scripts directory exists at all. Scoring against the actual bundle structure per the guidelines, this broken central reference plus the inlined generic boilerplate fits the 3-anchor. Not a 4 because a missing entry script is not a minor organization gap.

3 / 5

Total

11

/

20

Passed

Description

61%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 reasonably specific, distinct description with a clear 'what' but no explicit 'when to use' trigger clause, and it slips into second-person voice. It would benefit from a 'Use when...' sentence with natural synonyms (.docx, Word, revisions, comments).

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions track changes, revision history, reviewer comments, or multiple DOCX versions (.docx) of a document.'

Rewrite in third person: replace 'when you run it on one or more DOCX versions' with 'when run on one or more DOCX versions'.

Add natural synonyms users would say: 'Word document', 'revisions', 'comments', '.docx'.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("detect DOCX track-changes history, version rounds, and author feedback to generate a Markdown modification explanation file"), which would fit the 4-anchor, but it is written in second person ("when you run it on one or more DOCX versions"), so per the judging guidelines the specificity score is reduced by 1. Not a 5 because the actions overlap heavily (three flavors of 'detect') around one deliverable.

3 / 5

Completeness

The 'what' is clear (detect track changes/versions/author feedback, generate a Markdown explanation file), but there is no 'Use when...' clause or equivalent explicit trigger guidance — "when you run it on one or more DOCX versions" describes an input condition, not when to invoke the skill, so completeness is capped at 3 per the guidelines. Not a 2 because the 'what' is concrete and well stated.

3 / 5

Trigger Term Quality

Good keyword coverage: "DOCX", "track-changes", "version rounds", "author feedback", "Markdown" are natural terms a user would say. Not a 5 because common synonyms and variations are missing (".docx" extension, "Word", "revisions", "comments", "compare versions").

4 / 5

Distinctiveness Conflict Risk

The track-changes/version-round/author-feedback niche is fairly distinct, but generic terms like "DOCX versions" leave minor overlap risk with general DOCX/Word document-processing skills. Not a 5 because "one or more DOCX versions" could plausibly trigger broader document-editing skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/docx-feedback-tracker/SKILL.md

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.