reset-context-contamination

Solid

Discards this thread's accumulated drafts and framings and re-derives the task from a clean problem statement. Use when the user says the thread is contaminated, the conversation is going in circles, or that they want a fresh take.

AI & Automation 36 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
52
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
49
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

This thread's history has become the problem - prior drafts and framings are anchoring every new attempt. Reset. First, extract what's worth keeping, in plain factual terms: who is involved, the outcome I want, the hard constraints, the known facts, and - critically - what's already been tried and ruled out, so a fresh derivation doesn't walk back into a dead end. Then pick the path by severity: - Deep contamination, or anything high-stakes: do not try to reset yourself - the contaminated model cannot be trusted to author its own reset. Hand the extracted brief to a fresh subagent, or recommend I start a new session. A genuinely clean context window is the only reliable reset. - Mild drift only: re-derive in-thread from the extracted brief, as if seeing the task for the first time. Void the earlier drafts entirely - no referencing, quoting, or patching them. If you are unsure the brief itself is right, show it to me before drafting; otherwise just proceed.

Details

Author
tenequm
Repository
tenequm/skills
Created
10 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

ground-first

Use BEFORE acting whenever getting it wrong has real cost — in ANY domain, not just infra. Fire for complex or multi-step work; irreversible or hard-to-undo actions; anything touching production, shared state, real user data, money/payments, security/credentials, schema/migrations, external APIs/integrations, concurrency, or a change rippling across many call sites; and debugging where acting on the wrong root cause makes it worse. Judge the REAL work from your own understanding, not keywords — a request can say "payment" or "migrate" or "refactor" and be a one-line cosmetic edit, while a plain-sounding one is deeply consequential. It splits what you KNOW from what you're ASSUMING, surfaces the silent failure modes, and verifies your riskiest assumptions before the irreversible step. Do NOT use for trivial reversible edits — renames of a local symbol, typos, comments, formatting, cosmetic tweaks.

0 Updated 1 weeks ago
88plug
AI & Automation Listed

attention-reset

Use when the agent changes objectives, chases optional discoveries, context-switches repeatedly, abandons the active item, or shows ADHD-like distraction as a behavioral analogy.

3 Updated 3 weeks ago
ihabkhaled
AI & Automation Listed

manage-context

Use when the session is long, the repo is unfamiliar, the work is multi-file, you are stuck, or you need to escalate to a stronger model. Context budget, session hygiene, zoom-out, deep triage, escalate, onboarding, post-compact re-anchor. Phase = Recovery / Re-context / Escalate.

3 Updated today
nuttaruj