← ClaudeAtlas

study-firstlisted

Load BEFORE answering any message that asks for more than a single fact, and whenever answering means reading something (a document, PDF, chat transcript, web page, code, screenshot, task status, ad campaign). It makes the agent break down EVERYTHING the user asked (including messy dictated voice messages and "scratch that" corrections), read the sources IN FULL (not the title, not the first lines, not the "succeeded" label), cross-check with a second source, and answer point by point with evidence, never writing a detail it did not actually see. Triggers on "study this", "look into it properly", "read it carefully", "analyze", "investigate", "what does it say", "how is it going", "did it work", long or dictated messages, and in Spanish "estudia", "revisa a fondo", "a profundidad", "léelo bien", "analiza", "cómo vas", "qué pasó con", "funcionó".
RabbitDesigns22/claude-skills · ★ 0 · AI & Automation · score 75
Install: claude install-skill RabbitDesigns22/claude-skills
# Study first, then answer Most agent mistakes share one root: **the agent skimmed and then answered as if it had studied.** Real cases this skill was built from: - A scheduled task was reported fine because the app said "succeeded". All 6 runs had died on a permission prompt. - An account was said to belong to the agency because a link redirected there. - A data format was changed without searching for its readers, and another part of the code broke. - A file number was taken from memory instead of from the folder, and an existing file was overwritten. This skill puts the study before the answer. It cannot promise zero mistakes. It does make sure no answer rests on something nobody read. ## 0. Size it (5 seconds) - **A single fact** from one source (a time, a number, a yes/no): read it at the source and answer. Skip the rest. - **Anything else**: steps 1-5. The more a mistake costs (a client, money, publishing, deleting), the deeper you go. ## 1. Break down what the user said (before opening anything) Write, for yourself, the **list of asks**: every question, every instruction, every condition, and anything that clearly bothers them. - Use their exact words for names, numbers, dates, prices and clients. - People dictate and type fast. Read what they meant ("Hit" may be "GitHub", "OCMO VAS" is "cómo vas"). - If they change their mind ("scratch that", "no, better..."), the **last** version counts. - A long message usually carries 3 to 6 asks. If you found only one, rea