← ClaudeAtlas

prompt-clarity-enginelisted

Rewrites vague or underspecified prompts into clear, LLM-friendly instructions, using a categorised taxonomy of 200+ instruction verbs (reading, extraction, synthesis, evaluation, verification, risk detection, planning, iteration and more), a fixed instruction order, and a six-question completeness check. Diagnoses catch-all wording such as "ingest", "process", "understand", "improve", "optimise", "fix", "continue" and "research", and reconstructs the prompt around an observable action, explicit scope, a stated output form and a validation step. Use whenever someone wants a clearer prompt for an LLM, asks "how do I ask this better", "make this prompt more specific", "why isn't the model doing what I want", or pastes a rough instruction and wants it tightened or made implementation-ready. Also covers prompt engineering audits and turning a one-line ask into a properly scoped brief.
TABARC-Code/prompt-clarity-engine · ★ 0 · AI & Automation · score 70
Install: claude install-skill TABARC-Code/prompt-clarity-engine
# Prompt Clarity Engine Author: TABARC-Code Repository: https://github.com/TABARC-Code/ ## Purpose Language models are not mind readers. A prompt built from vague, all-purpose verbs — *ingest*, *process*, *understand*, *improve* — feels clear to the human who wrote it, because the human instinctively fills in the missing intent. The model has to guess it instead, and it doesn't always guess well. This skill takes a rough prompt and rebuilds it around verbs that describe an action a reader could actually observe in the output, so the model has somewhere specific to go rather than a vague direction and a shrug. ## Reference file `references/instruction-keyword-taxonomy.md` holds the full categorised verb tables (twenty categories, from reading and extraction through to planning and output modifiers), the weak-verb upgrade patterns, and the compound prompt templates. Consult the category that matches the operation you're choosing a verb for — you don't need to read the whole file for every prompt, just the sections relevant to the stages you've identified for this particular one. ## Workflow ### Step 1 — Read the submitted prompt Take it at face value first. Don't assume the person wrote it badly on purpose; most vague prompts are vague because the writer knows exactly what they mean and hasn't noticed that the model doesn't share that context. ### Step 2 — Diagnose Check the prompt against the weak-verb list below and against the six questions. A prompt is weak where