CtrlK
BlogDocsLog inGet started
Tessl Logo

remind

Rewrite the last response simpler and shorter in plain English, prefixed with a 2-4 sentence TLDR of the conversation so far. Manual-only, invoked as /remind.

56

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/thinking-and-docs/remind/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The body communicates a clear, simple two-part instruction but suffers from notable repetition, a typo, and zero structural organization. Tightening and lightly sectioning the content would materially improve it without adding length.

Suggestions

Collapse the four repetitive paragraphs into one tight instruction block, removing redundant emphasis like 'THE PARAGRAPH SHOULD BE VERY CONCISE' and fixing the typo 'wrritten'.

Add a brief example of the expected output (a sample TLDR paragraph followed by a shortened rewrite) so the desired format is unambiguous.

Introduce minimal section headers (e.g. '## TLDR' and '## Simplified response') to give the simple skill the organization needed for a higher progressive-disclosure score.

DimensionReasoningScore

Conciseness

The body restates 'simpler/shorter/concise/plain English' four or more times and adds emphasis fluff ('THE PARAGRAPH SHOULD BE VERY CONCISE') plus a typo ('wrritten'); it is mostly efficient but visibly padded and could be tightened, matching the anchor for some unnecessary explanation.

2 / 3

Actionability

Guidance is concrete for an instruction skill (2-4 sentences, four named content elements, two-part output structure), but vague phrasing ('nice readable markdown', 'be concise') and the absence of a sample output leave it incomplete rather than fully crisp.

2 / 3

Workflow Clarity

A two-part sequence is present ('start with...summary', 'Below the tldr paragraph, output...'), but it is scattered across four redundant paragraphs rather than laid out as a clean sequence, so checkpoints/structure are implicit.

2 / 3

Progressive Disclosure

The skill is short and needs no external references, but the body has no section organization (no headers) at all, so it does not meet the 'well-organized sections' bar needed for a top score on a simple skill.

2 / 3

Total

8

/

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.

The description is concrete and self-contained, cleanly answering both what it does and when to invoke it via a distinct slash command. It could be strengthened with broader natural-language trigger variations.

Suggestions

Add common natural trigger terms users might say, e.g. 'summarize', 'ELI5', 'recap', or 'dumb it down', alongside 'simpler', 'shorter', and 'TLDR'.

Consider naming the input/output scope more concretely (e.g. 'of the last assistant response') to broaden specificity beyond the narrow rewrite task.

DimensionReasoningScore

Specificity

Names two concrete actions ('Rewrite the last response simpler and shorter' and 'prefixed with a 2-4 sentence TLDR') but the capability is a narrow single task rather than a comprehensive multi-action set, matching the anchor that names domain and some actions.

2 / 3

Completeness

Clearly states what it does and provides explicit trigger guidance via 'Manual-only, invoked as /remind', which is an equivalent explicit 'Use when' clause for a slash-command skill.

3 / 3

Trigger Term Quality

Includes relevant natural terms ('simpler', 'shorter', 'plain English', 'TLDR') a user might say, but misses common variations like 'summarize', 'ELI5', 'recap', or 'dumb it down', so coverage is partial rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

The simplify-plus-TLDR niche and unique '/remind' invocation make it clearly distinguishable and unlikely to trigger for the wrong skill.

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
mishatojk/davidskills
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.