Identify and classify persona re-injection channels across repo, ancestor, and user scopes.
npx skills add https://github.com/jscottchapman/skills --skill persona-exorcist
Please help me install this Agent Skill. Skill: persona-exorcist Source: https://github.com/jscottchapman/skills/tree/main/persona-exorcist Command: npx skills add https://github.com/jscottchapman/skills --skill persona-exorcist
This skill helps you locate and eradicate hidden re-injection channels that keep re-adding deleted AI personas across a codebase, including repo, ancestor, and user-level configurations.
Run a sweep across the project to identify live sources and then scrub the most persistent channel if approved.
High-intent search queries and answers about installing and using this skill.
Deleted AI personas reappear through hidden re-injection channels like hooks, memory entries, imports, and symlinks. You must surface all definition sources across repo, ancestor, and user scopes, then perform a reversible scrub followed by a re-sweep to confirm permanent removal.
Cross-scope hauntings cause ghost AI personas to return when ancestor or user-level configurations re-inject deleted personas into repo scopes. Identifying and classifying these re-injection channels by strength allows you to quarantine sources and prevent future re-injections across projects.
Finding hidden hooks and memory entries requires sweeping the project to capture exact file paths, hook commands, memory entries, and symlink edges. Classifying these sources by scope and strength guides safe, reversible scrubbing to eradicate the re-injection channels.
The safest way to scrub AI persona configurations is through a reversible process that quarantines and backs up files before removal. Capturing exact file paths and hook commands ensures strict governance, while a post-scrub re-sweep confirms the personas are permanently eradicated.
Yes, you must check user-level configurations when removing AI personas because re-injection channels operate across repo, ancestor, and user scopes. Cross-scope sweeps prevent ghosts from returning by ensuring all hidden definition sources are surfaced and scrubbed.
Your deleted persona comes back because hidden re-injection channels like hooks, memory entries, imports, and symlinks automatically re-add it. Ancestor and user-level configurations can override repo-level deletions, requiring a full cross-scope sweep to identify and scrub all active sources.
NominexHQHydrate empty or template-only PMM memory files using existing session context.
AlexKapadiaDelete a Pixie tool folder, .venv, data, and configuration permanently.
satanyakivConfigure Sentry crash reporting for Kotlin Multiplatform Android and iOS projects.
romiluz13Review persistent agent memory files and database entries using a five-outcome classification rubric.
