opelpleple
- 17 skills
- 0 followers
- 6 hours ago last updated
- ▌ Compact · opelplepleDistills a long conversation or working document down to its load-bearing essence — decisions, constraints, open questions, and current state — while discarding resolved chatter and noise, so a long-running task stays coherent without exhausting the context window. Use this skill when the user says "compact this", "summarize where we are", "condense the thread", or "let's reset and continue"; when a conversation has grown long and unwieldy; when context is filling up before a big next step; or whenever earlier turns are crowding out the signal the task actually needs.
- ▌ Distill · opelplepleCompresses a long article, paper, report, or transcript into a tiny high-signal output — one-sentence core thesis, three load-bearing bullets, and one open question that remains — optimizing for maximum insight per word rather than coverage. Use this skill when the user shares a long read and says "summarize this", "tl;dr", "give me the gist", "what's the key takeaway", "what's the one thing I need to know", "distill this", or when they're triaging research, papers, reports, meeting transcripts, or long threads and need to decide fast whether something is worth their full attention.
- ▌ Handoff · opelplepleWrites a self-contained brief that lets a fresh agent, a colleague, or a more capable model pick up the work cold — capturing goal, current state, decisions, gotchas, and next steps so nothing is lost across a context boundary. Use this skill when the user says "hand this off", "brief the next person", "write a handoff", or "escalate this with full context"; when ending a session or before a context reset; when switching models or delegating to a sub-agent; or whenever work must cross from one context into another without loss.
- ▌ Red Team · opelplepleAttacks the user's own plan, design, code, or argument the way a motivated adversary or reality would, to surface the holes before a real opponent finds them. Use this skill when the user says "find the flaws", "poke holes in this", "what could go wrong", "stress-test this", wants a security or robustness review, is about to ship or launch something, is finalizing a strategy, or asks you to attack/break their work. Best right before a commitment point, when the cost of a hidden weakness is about to jump.
- ▌ Steelman · opelplepleBefore arguing against any position, builds the strongest, most charitable version of it first, then critiques only that fortified version — never a strawman. Use this skill when the user is evaluating an argument, proposal, competitor, or decision and wants honest critique, or says things like "argue against X", "is this a good idea?", "poke holes in this", "play devil's advocate", "should we do X", "convince me I'm wrong", or is debating a choice. Ensures criticism lands on the real merits instead of an easy-to-knock-down caricature.
- ▌
- ▌ Pre Mortem · opelplepleImagines the plan has already failed six months in the future, then works backwards to enumerate every reason why — surfacing risks that optimism and momentum normally hide. Use this skill when the user is finalizing a plan, launch, migration, hire, or big decision and asks "what could go wrong?", "review my plan", "what am I missing?", "poke holes before we commit", or is about to commit to something expensive or hard to reverse. Pairs with grill-me (which stress-tests at the start); pre-mortem assumes failure has happened and reasons backward.
- ▌ Scratchpad · opelplepleOffloads notes, todos, decisions, and intermediate findings to an external file outside the context window, then pulls only the relevant pieces back when needed — giving the agent persistent memory that survives context limits and resets. Use this skill when the user says "take notes", "keep track of", "remember this for later", or "make a checklist"; when a task is multi-step or spans many tool calls (roughly 20+); when intermediate findings would otherwise be lost; or whenever you're accumulating state that doesn't need to sit live in the context window.
- ▌
- ▌ Rubber Duck · opelplepleActs as a silent rubber duck that mostly listens and asks naive, clarifying questions so you explain your problem aloud until the answer surfaces on its own. Use this skill when the user is stuck debugging or reasoning, wants to think out loud, or says things like "let me talk this through", "I'm stuck", "rubber duck me", "help me think", "I don't know why this isn't working", or "let me explain what I'm trying to do". Deliberately withholds solutions unless explicitly asked, because the value is the user's own articulation, not the assistant's answer.
- ▌ Scope Cutter · opelplepleTakes an ambitious idea and aggressively cuts it down to the smallest version that is still valid, useful, and shippable — a true MVP — killing scope creep before it starts. Use this skill when the user has a big feature or project and says "this is getting big", "what's the MVP?", "help me scope this down", "where do I start", "this feels like too much", or is planning a build that's ballooning. Forces a ruthless distinction between what proves the core hypothesis now and what is genuinely "later".
- ▌
- ▌ Context Budget · opelplepleAudits what is currently consuming the context window — system prompt, tool definitions, conversation history, attached files, retrieved docs — locates the bloat, and cuts or compresses the lowest-value tokens, treating context as a finite budget to be spent deliberately. Use this skill when the user says "context is full", "what's eating my context", "prune this prompt", or "make this cheaper/faster"; when runs feel slow or costly; when too many tools or huge files are loaded; or whenever you need to reclaim room before continuing.
- ▌ Devils Advocate · opelplepleForcefully argues the opposite of whatever the user is already leaning toward, before they commit, to break confirmation bias and groupthink. Use this skill when the user has effectively decided and is seeking validation ("I'm going to do X", "we've decided to...", "just confirming this is right"), shows one-sided enthusiasm with no counterweight, faces a big or irreversible choice, says "talk me out of it", "devil's advocate", "argue the other side", or "what am I not seeing". Best when agreement would be too easy and the downside of being wrong is large.
- ▌ Assumption Audit · opelplepleExcavates the hidden assumptions baked into a plan, belief, or estimate, lists them explicitly, then ranks them by how much damage results if each turns out to be wrong — so the riskiest get tested first. Use this skill when the user asks "what am I assuming", "audit my assumptions", "what am I taking for granted", has a shaky estimate or forecast, is building a plan that depends on unknowns, wants to de-risk before committing resources, or when a plan feels confident but rests on untested beliefs. Best when a plan looks solid on the surface but its foundations have never been checked.
- ▌ First Principles · opelplepleBreaks a problem down to fundamental, irreducible truths and rebuilds a solution from them, refusing to reason by analogy or by copying how others already do it. Use this skill when the user is stuck in conventional thinking, asks "why do we even do it this way", wants to challenge baked-in assumptions, faces a hard design or strategy problem with no obvious answer, says "think from first principles", "go back to basics", "forget how everyone else does it", or suspects the standard approach is cargo-culted rather than reasoned. Best when the default solution feels expensive, slow, or inherited rather than chosen.
- ▌