CtrlK
BlogDocsLog inGet started
Tessl Logo

cover-letter

Describe the role and your background, get a concise, compelling cover letter paragraph.

64

Quality

75%

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 ./skills/gemma/cover-letter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

The body is concise, fully actionable, and well-organized for a simple single-purpose skill, with concrete tool/parameter guidance and clear sections.

DimensionReasoningScore

Conciseness

The body is lean — a one-line intro, four short examples, and a compact field spec — with no concept explanation Claude already knows; every section earns its place.

3 / 3

Actionability

"You MUST use the `run_js` tool with the following exact parameters" followed by a fully specified JSON field schema gives concrete, copy-paste-ready executable guidance, reinforced by concrete input examples.

3 / 3

Workflow Clarity

This is a simple single-task skill under 50 lines with one unambiguous action (call run_js with the given data), so per the simple-skills note workflow clarity scores 3.

3 / 3

Progressive Disclosure

Content is organized into clear Examples and Instructions sections with no monolithic wall or nested references; the bundle files (scripts/index.html, assets/webview.html) are implementation infrastructure wired by the run_js tool, so a short single-purpose skill needs no further reference navigation.

3 / 3

Total

12

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 conveys the skill's purpose and a natural trigger term, but it stops short of listing multiple concrete actions and omits an explicit "Use when" clause, leaving it at the middle band across all dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user needs a cover letter for a job application."

Expand concrete actions beyond the input/output framing, e.g. "Drafts, tailors, and polishes a cover letter opening paragraph from your role and background."

Add natural trigger variations such as "job application letter" or "apply for a role" to improve keyword coverage.

DimensionReasoningScore

Specificity

"Describe the role and your background" and "get a concise, compelling cover letter paragraph" name the domain and two actions, but unlike the score-3 anchor they do not list multiple distinct concrete actions.

2 / 3

Completeness

It clearly answers what ("get a... cover letter paragraph") but has no "Use when..." or equivalent explicit trigger guidance, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

"cover letter" is a natural keyword a user would say, but coverage is thin with no common variations such as "job application" or "apply".

2 / 3

Distinctiveness Conflict Risk

"cover letter" is a recognizable niche, but without explicit distinct triggers it could still overlap with general writing or resume skills.

2 / 3

Total

8

/

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
mergisi/awesome-openclaw-agents
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.