CtrlK
BlogDocsLog inGet started
Tessl Logo

xml-doc-writer

Write, validate, and improve XML documentation comments in C# source code. Use when asked to add, fix, review, or complete XML docs for C# APIs.

76

Quality

94%

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

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

An exemplary lean instruction skill: specific, executable directives organized into a clear four-step workflow with a validation step, and appropriately self-contained at ~40 lines. The only gap is the absence of an explicit error-recovery loop after validation, which keeps workflow clarity at 4.

DimensionReasoningScore

Conciseness

Every bullet is a directive ("Indent nested XML elements by two spaces per level", "Preserve a final newline in every modified file") with zero padding or explanation of concepts Claude already knows, matching the lean anchor-5 example.

5 / 5

Actionability

Guidance is copy-paste-ready for an instruction-only skill: exact tag syntax ("<see cref=\"...\"/>", "/// <inheritdoc />"), an explicit element-order list, exact indentation rules, and a specific stale-content pattern ("To be added."). The only mildly underspecified line ("current product names" for Xamarin rewrites) relies on knowledge Claude already has.

5 / 5

Workflow Clarity

The four-step sequence (Gather context, Write and improve, Normalize formatting, Validate) is clear and ends with an explicit validation step ("Review the final diff for valid XML, resolvable cref values"), but there is no validate-fix-retry feedback loop, which anchor 5 expects for a batch documentation operation.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references, and its sections are well-organized with a consistent hierarchy, satisfying the rubric's condition for a top progressive-disclosure score.

5 / 5

Total

19

/

20

Passed

Description

95%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 description: concrete third-person verbs, explicit trigger clause with enumerated user phrasings, and a well-defined C# niche. The only minor gap is that the action list could enumerate a couple more capabilities (e.g., formatting normalization or removing placeholder docs), which keeps specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

"Write, validate, and improve XML documentation comments in C# source code" names the domain and three concrete actions, matching the 'several specific actions; minor gaps' anchor rather than the fully comprehensive anchor-5 list.

4 / 5

Completeness

It explicitly answers both what ("Write, validate, and improve XML documentation comments in C# source code") and when ("Use when asked to add, fix, review, or complete XML docs for C# APIs"), exactly matching the anchor-5 example structure; third-person voice is used throughout.

5 / 5

Trigger Term Quality

"Use when asked to add, fix, review, or complete XML docs for C# APIs" covers the natural user phrasings (add/fix/review/complete) plus synonyms ("XML docs", "XML documentation comments", "C# APIs"), matching the comprehensive synonym coverage of anchor 5.

5 / 5

Distinctiveness Conflict Risk

"C# source code" and "XML documentation comments" carve a clear niche with distinct triggers that would not fire for general C# work or other languages' doc comments, matching anchor 5's minimal conflict risk.

5 / 5

Total

19

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/macios
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.