CtrlK
BlogDocsLog inGet started
Tessl Logo

prompt-me

Prompt the user with pointed questions to extract what is in their head about a project — remaining work, what is being avoided, what really matters, what does not. Use when the user says "prompt me", "ask me questions", or wants the agent to figure out priorities by questioning them.

52

Quality

57%

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/prompt-me/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%

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

The body is an early draft: it states a core idea and one example trigger but provides no concrete questions, workflow, or actionable guidance. It reads as a placeholder rather than a usable skill body.

Suggestions

Replace the draft stub with concrete guidance, e.g. a list of pointed question categories to ask (remaining work, avoided work, importance) and the order to ask them in.

Add a short workflow with an explicit checkpoint, such as summarizing the extracted priorities back to the user for confirmation.

Remove the "DRAFT — being refined" meta-note once content is finalized, as it adds tokens without actionable value.

DimensionReasoningScore

Conciseness

The body is short and not padded with concepts Claude already knows, but tokens like "DRAFT — being refined with the user" and the restated core idea do not earn their place as actionable instruction. Not 3 because most tokens convey no usable guidance; not 1 because it is lean rather than verbose.

2 / 3

Actionability

"Core idea: the agent interviews the user to extract priorities..." describes the intent rather than instructing; there is no concrete example question, script, or executable guidance. Not above 1 because it gives Claude nothing concrete to actually do or say.

1 / 3

Workflow Clarity

No steps, sequence, or validation checkpoints are present — the body is an unfinished draft stub. Not above 1 because there is no discernible workflow to follow.

1 / 3

Progressive Disclosure

There are no references or nested files, and for a tiny single-purpose skill that can be acceptable, but the body is not organized into usable sections — it is an unstructured draft. Not 1 because it avoids deep/nested references; not 3 because nothing is organized for navigation or use.

2 / 3

Total

6

/

12

Passed

Description

92%

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 well-formed: concrete capabilities, an explicit Use-when trigger clause, and natural trigger phrases. Its only soft spot is distinctiveness, since "ask me questions" is generic enough to overlap with ordinary clarifying behavior.

Suggestions

Sharpen the trigger to reduce overlap, e.g. narrow "ask me questions" to a more distinctive phrasing tied to extracting project priorities specifically.

Consider stating the output format (e.g. "produces a prioritized list of remaining work") to further separate it from generic questioning skills.

DimensionReasoningScore

Specificity

Names concrete actions — "Prompt the user with pointed questions to extract... remaining work, what is being avoided, what really matters, what does not" — listing several specific extraction targets rather than vague language. Not below 3 because it lists multiple specific concrete actions; not above because the scale caps at 3.

3 / 3

Completeness

Explicitly answers both what ("Prompt the user with pointed questions to extract...") and when ("Use when the user says 'prompt me', 'ask me questions'...") via an explicit Use-when clause. Not below 3 because both halves are clearly present.

3 / 3

Trigger Term Quality

Includes natural phrases a user would actually say — "prompt me", "ask me questions", "figure out priorities by questioning them" — with good coverage of common variations. Not below 3 because these are exactly the kinds of phrases a user would utter.

3 / 3

Distinctiveness Conflict Risk

"prompt me" is a fairly distinct trigger, but "ask me questions" and "figure out priorities by questioning them" are generic enough to overlap with general clarifying-question behavior in other skills. Not 3 because the niche is not sharply bounded from ordinary questioning; not 1 because the primary "prompt me" trigger gives it a recognizable identity.

2 / 3

Total

11

/

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.