Edit or review text to remove signs of AI-generated writing — inflated significance
('pivotal moment', 'evolving landscape'), promotional language ('nestled',
'breathtaking'), superficial -ing analyses ('highlighting', 'underscoring'), vague
attributions ('industry experts'), em-dash overuse, rule-of-three patterns, AI
vocabulary ('delve', 'tapestry'), copula avoidance ('serves as'), passive voice,
negative parallelisms ('not just X, but Y'), filler phrases, sycophantic openings
('Great question!'), and the rest of the 29-pattern catalog from Wikipedia's 'Signs of
AI writing'. Works on written prose only: essays, articles, drafts,
documentation, emails, marketing copy. Use this skill whenever the user wants to
humanize text, remove AI tells, edit AI-sounding writing, make text sound less like
ChatGPT, do a final 'does this read like a person wrote it' pass, or hits you with
phrases like 'humanize this', 'make this sound less AI', 'remove the AI slop', 'edit
this draft', or 'why does this read like an LLM'.
Write production-ready Bash scripts with strict error handling (`set -euo pipefail`),
validated argument parsing, colored user feedback, and cross-platform compatibility
(Linux, macOS, Windows via Git Bash/WSL). Use this skill whenever the user asks for a
`.sh` script, a shell script, a Bash one-liner installer, a CLI wrapper, or a
file-batch processor, and for server and deployment automation generally: releasing or
rolling back a build, restarting or health-checking a service, scheduled and cron jobs,
log rotation, backup and restore, syncing files between machines, and bootstrapping a
box. Includes casual phrasings like "write a script to ...", "automate this in bash",
or "make me a shell tool". Also use when reviewing or hardening an existing Bash
script.
Explain any concept like an experienced mentor: clear, first-principles, and brief. Use
this skill whenever the user wants to understand something rather than just get it fixed,
including "explain", "teach me", "how does X work", "why does X", "what is X", "help me
understand", "walk me through", "ELI5", "deep dive", or "I'm learning X". Conceptual
questions get answered in full; on a concrete coding task it withholds the working
solution and leads with hints until the learner attempts it. Do not use when the user
wants the job done rather than explained.
