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

83%

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

The canonical home for this skill is prompt in BigSimmo/PsychSift

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, instruction-first skill body with a concrete template, exact control flags, and a properly signaled single reference. All dimensions sit just below top: mild cross-section redundancy, no worked example, template-level rather than explicit validation loops, and a body that is somewhat heavy for an overview.

Suggestions

Add one short worked example (rough request input to perfected prompt output) to the Prompt construction section to make the guidance fully concrete for common cases.

Deduplicate the smallest-necessary-tool and untrusted-content rules, each of which currently appears in two or three sections (Operating principles, workflow steps, Context, Boundaries).

Move the 'API and ChatGPT prompt practice' and 'Model and tool choice' sections into a one-level-deep reference file like the existing coding-workflow.md, keeping SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

Largely lean and instruction-first with no explanations of concepts Claude already knows, e.g. 'Do not request hidden chain-of-thought; request concise rationale'. Minor trimmable redundancy: the smallest-necessary-tool rule appears in Operating principles, workflow step 7, and Model and tool choice; untrusted-content rules repeat across the Context and Boundaries sections.

4 / 5

Actionability

Concrete, executable guidance: a copy-paste-ready prompt template with exact fields (Goal, Success criteria, Verification and stop rules), enumerated control flags with exact semantics ('prompt only', 'review first', 'literal', 'variants', 'no prompt shown'), and numbered default output sections. Not anchor 5 because no worked example shows a rough request transformed into a perfected prompt.

4 / 5

Workflow Clarity

A clearly sequenced 9-step core workflow with task classification routing, explicit ask/stop checkpoints ('ask a single targeted question before executing', 'End when the stated success criteria are met'), and verification/stop rules embedded in the template. Not anchor 5 because error-recovery feedback loops are only template-level and the interleaved review/diagnosis/implementation branches add mild complexity.

4 / 5

Progressive Disclosure

One real, one-level-deep reference (references/coding-workflow.md) with clear read and skip conditions ('read references/coding-workflow.md before relying on findings or editing... Skip the reference for prompt-only or answer-only work'). Not anchor 5 because the ~121-line body carries sections such as 'API and ChatGPT prompt practice' and 'Model and tool choice' that are heavier than an overview and could live in reference files.

4 / 5

Total

16

/

20

Passed

Description

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

A strong description with a clear what/when structure, multiple concrete trigger verbs, and an explicit exclusion boundary. Its main gaps are minor: a few missing natural trigger synonyms and an abstract lead action ('perfect') whose concrete coverage skews toward the code-changing edge case.

DimensionReasoningScore

Specificity

Lists several specific concrete actions ('verify task ownership and use an isolated checkout', 'preserve verified same-task continuation', 'answer or execute it') beyond the headline 'perfect a rough request or draft prompt'. Falls short of anchor 5 because 'perfect' is somewhat abstract as the lead action and coverage emphasizes the code-changing edge case rather than comprehensively enumerating capabilities.

4 / 5

Completeness

Explicitly answers both 'what' ('Perfect a rough request or draft prompt... then answer or execute it') and 'when' with concrete trigger phrases ('Use when the user invokes $prompt or asks to improve, rewrite, sharpen, expand, contextualize, or optimize their prompt before acting'), plus a negative trigger ('Do not use for ordinary code or content review unless prompt improvement is requested').

5 / 5

Trigger Term Quality

Good keyword coverage: 'Use when the user invokes $prompt or asks to improve, rewrite, sharpen, expand, contextualize, or optimize their prompt' captures six natural trigger verbs plus the explicit invocation. Not anchor 5 because common variations like 'refine', 'polish', or 'make this prompt better' are missing.

4 / 5

Distinctiveness Conflict Risk

Mostly distinct with explicit conflict exclusions ('Do not use for ordinary code or content review unless prompt improvement is requested') and a clear prompt-perfection niche. Not anchor 5 because the body itself must disambiguate against the closely related 'prompt-perfector' skill, indicating residual overlap risk.

4 / 5

Total

17

/

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/cloud-profile/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.