CtrlK
BlogDocsLog inGet started
Tessl Logo

swift-docc-comments

Use when writing or enhancing Swift documentation comments for DocC generation, adding inline doc comments to Swift source files, or when user asks for API documentation

81

1.00x
Quality

Does it follow best practices?

Impact

95%

1.00x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is actionable and well-structured, with concrete executable Swift examples and a real build command. Its only weakness is mild redundancy between the Common Mistakes table and the Red Flags list.

Suggestions

Merge the 'Red Flags' list into the 'Common Mistakes' table (or vice versa) to remove the duplication of ## Overview/## Topics/parameters-before-code.

Optionally add a one-line negative example showing a wrongly-formatted comment alongside the 'Correct Format' block for direct before/after contrast.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the 'Red Flags' list substantially duplicates the 'Common Mistakes' table (## Overview, ## Topics, parameters-before-code), so it could be tightened.

2 / 3

Actionability

Provides a complete, executable 'Correct Format' Swift example with real - Parameter/- Returns/- Note: markup, a structure template, a quick-reference mapping table, and the concrete command 'swift package generate-documentation' — copy-paste ready.

3 / 3

Workflow Clarity

A single-purpose formatting skill with an unambiguous action (write DocC-format inline comments); per the simple-skills note it qualifies for 3, and no validation feedback loop is required for non-destructive comment writing.

3 / 3

Progressive Disclosure

A self-contained skill with no bundle files and no need for external references, organized into clear well-labeled sections (Overview, Structure, Quick Reference, Correct Format, Common Mistakes, Red Flags, Generate Documentation).

3 / 3

Total

11

/

12

Passed

Description

85%

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

The description is specific and complete, explicitly pairing concrete actions with a 'Use when...' trigger and carving out a distinct Swift-DocC niche. It loses a point on trigger term quality only for missing some natural user phrasings.

Suggestions

Broaden trigger terms with natural phrasings users actually say, e.g. 'document my Swift code', 'add docs to functions/types', or 'fix DocC warnings'.

Consider mentioning the output (DocC-generated documentation site) to sharpen the 'what' beyond the input actions.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('writing or enhancing Swift documentation comments for DocC generation', 'adding inline doc comments to Swift source files') rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what (write/enhance/add inline DocC comments) and when via a present 'Use when...' trigger clause ('or when user asks for API documentation'), matching the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Includes natural terms ('API documentation', 'DocC generation', 'documentation comments') but misses common variations a user might say ('document my Swift code', 'add docs to my functions'), matching the some-relevant-keywords-but-missing-variations anchor.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (Swift-specific DocC inline source comments) with distinct triggers unlikely to fire for unrelated skills, matching the clear-niche-with-distinct-triggers anchor.

3 / 3

Total

11

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
ivan-magda/claude-superpowers
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.