Loading...
Loading...
Found 104 Skills
Analyze session history for learnings and persist to skills. Solves "memory zero" - correct once, never again.
AI Tarot Diviner, interpreting tarot cards from a Jungian psychology perspective. Supports 12 spreads including 1-card, 3-card, and 5-card layouts. Use this when the user asks for tarot reading, card drawing, daily fortune, or mentions keywords like tarot, divination, card drawing, fortune-telling, luck, or spreads.
Help users replan their lives from the top level of NLP understanding hierarchy; use this when users feel confused, trapped in a daily execution loop, and don't know how to break through the current situation
An interactive Skill based on the 5-step framework from the book *Hey, Just Get It Done*, which helps you reflect on stalled work without self-blame and uncover hidden assumptions as well as your next actionable step. Use this when you need to work through procrastination, perfectionism, fear of submission, or stagnation after receiving feedback. Do not use this for simple execution tasks, explanations, minor revisions, or comprehensive planning.
Guide a PhD student through a structured weekly review of their research progress. Use this skill whenever the user wants to do a weekly check-in, prepare a progress update for their advisor, reflect on the past week's research, or plan the upcoming week. Trigger on phrases like "weekly review", "this week's progress", "advisor update", "reflect on my week", "plan next week", "how did my week go", or whenever the user mentions wanting to take stock of their recent research work. Also trigger when the user seems to be venting about the week without structure — help them channel it into a productive review.
Generates a structured implementation report reflecting on a just-completed feature — what was done, divergences, challenges. Use right after finishing an implementation, as the input to a system review.
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.
Reflect on the conversation and update the brain. Use when wrapping up, after mistakes or corrections, or when significant codebase knowledge was gained. Triggers: "reflect", "remember this".