CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prompt

Perfect a rough request or draft prompt using relevant context, attachments, files, and the minimum necessary skills or tools, then answer or execute it. Use when the user invokes $prompt or asks to improve, rewrite, sharpen, expand, contextualize, or optimize their prompt before acting. For code-changing prompts, verify task ownership and use an isolated checkout when needed; preserve verified same-task continuation. Do not use for ordinary code or content review unless prompt improvement is requested.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a dense, well-structured instruction-only skill: a 9-step workflow with decision checkpoints and stop rules, a copy-paste prompt template, explicit user controls, and repository detail correctly deferred to a real, clearly signaled one-level-deep reference. It is efficient and actionable, with only minor redundancy across sections and no worked example of the core prompt transformation.

Suggestions

Consolidate the minimal-tools guidance, which appears in three places (Operating principles, Core workflow step 7, and Model and tool choice), into a single section to save tokens.

Add one short worked example (rough request → perfected prompt) so the core transformation is concrete and the most common case is covered.

Merge the stop and validation rules scattered across Operating principles, the prompt template, and the workflow into one place (e.g., the Verification and stop rules section) to sharpen workflow checkpoints.

DimensionReasoningScore

Conciseness

The body is dense with no padding and no explanation of concepts Claude already knowns (e.g., "Do not request hidden chain-of-thought; request concise rationale"). Minor trimmable redundancy remains: minimal-tool guidance appears in "Operating principles" ("Choose the smallest relevant skill, tool, research step, and verification"), workflow step 7 ("Select the minimum relevant skills and tools"), and "Model and tool choice" ("Prefer one focused tool call over broad, repeated discovery"). Anchor 4 fits — efficient with minor instances that could be trimmed; not noticeably padded enough for 3.

4 / 5

Actionability

Concrete, executable guidance throughout: a copy-paste prompt template ("Goal: ... Success criteria: ... Verification and stop rules:"), enumerated output sections ("1. `Perfected prompt` — the ready-to-use prompt in a fenced code block. 2. `Answer`"), and specific user controls ("`prompt only`", "`review first`", "`literal`", "`variants`", "`no prompt shown`"). The one gap versus anchor 5 is the absence of a worked example showing a rough request transformed into a perfected prompt, so specific examples don't fully cover the common cases.

4 / 5

Workflow Clarity

"## Core workflow" gives a clear numbered 9-step sequence from "Reconstruct the real task" through "Show the perfected prompt, then answer or execute it immediately", with explicit decision checkpoints ("ask a single targeted question before executing") and a stop rule ("End when the stated success criteria are met"). This is not a destructive or batch skill, so the validation cap does not apply; it still lacks the explicit validate-fix-retry feedback loops of the anchor-5 example, leaving minor checkpoint gaps at anchor 4.

4 / 5

Progressive Disclosure

The body is organized into clear sections, and the single bundle file references/coding-workflow.md exists and is well-signaled with conditional routing: "read `references/coding-workflow.md` before relying on findings or editing ... Skip the reference for prompt-only or answer-only work". One-level-deep reference, content appropriately split, easy navigation — matches anchor 5 against the actual bundle structure.

5 / 5

Total

17

/

20

Passed

Description

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

The description clearly states what the skill does and provides an explicit 'Use when' clause with multiple natural trigger verbs, a $prompt invocation token, and a de-confliction exclusion for ordinary review work. The abstract core verb 'Perfect' and a few missing natural synonyms (e.g., 'refine', 'fix my prompt') keep specificity and trigger coverage at 4 rather than 5.

DimensionReasoningScore

Specificity

Several concrete actions are named — "Perfect a rough request or draft prompt using relevant context, attachments, files", "then answer or execute it", "verify task ownership and use an isolated checkout", "preserve verified same-task continuation" — but the core verb "Perfect" is more abstract than anchor 5's list of discrete concrete actions. It clearly exceeds anchor 3's '1-2 concrete actions' bar.

4 / 5

Completeness

Explicitly answers both: what — "Perfect a rough request or draft prompt ... then answer or execute it"; when — "Use when the user invokes $prompt or asks to improve, rewrite, sharpen, expand, contextualize, or optimize their prompt before acting", with concrete trigger phrases and a negative-scope clause ("Do not use for ordinary code or content review unless prompt improvement is requested"). Matches the anchor-5 pattern; the 'Use when' cap does not apply.

5 / 5

Trigger Term Quality

"Use when the user invokes $prompt or asks to improve, rewrite, sharpen, expand, contextualize, or optimize their prompt" gives good natural-verb coverage plus an explicit invocation token, but common variations like "refine", "fix my prompt", or "make this prompt better" are missing. Solidly above anchor 3's 'some relevant keywords', just short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche (prompt refinement) with distinct triggers, and the exclusion "Do not use for ordinary code or content review unless prompt improvement is requested" explicitly de-conflicts with review skills. Minimal overlap risk, matching anchor 5.

5 / 5

Total

18

/

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

BigSimmo/PsychSift

Path

.claude/skills/prompt/SKILL.md

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.