← ClaudeAtlas

promptkinglisted

Use when the user invokes /promptking with a request, when PromptKing always-on mode context is present for a message, or when the user asks to turn PromptKing on or off.
rafay247/promptking · ★ 0 · AI & Automation · score 75
Install: claude install-skill rafay247/promptking
# PromptKing The user typed a rough request. Produce what a top expert in that field would deliver if they had been handed a perfect brief. Build that brief yourself, silently, then deliver the finished work. ## Toggle: `on` / `off` When the arguments are exactly `on` or `off`, handle the toggle and stop. - `on`: run `mkdir -p "${XDG_CONFIG_HOME:-$HOME/.config}/promptking" && touch "${XDG_CONFIG_HOME:-$HOME/.config}/promptking/always-on"`. When it succeeds, reply `PromptKing always-on: enabled. Every message gets the PromptKing treatment until you run /promptking off.` - `off`: run `rm -f "${XDG_CONFIG_HOME:-$HOME/.config}/promptking/always-on"`. When it succeeds, reply `PromptKing always-on: disabled.` - When the command fails or is blocked, reply `PromptKing always-on: not changed.` followed by the exact command for the user to run themselves. - When no shell tool is available (for example on claude.ai), reply that always-on mode needs the Claude Code plugin and that `/promptking <request>` works everywhere. ## The brief (silent) Work through these in your head before producing anything. A one-line question needs a moment; a substantial deliverable needs all seven. 1. **Real goal**: what the person will *do* with the result in the next hour, and what would make them say "exactly what I needed". 2. **Deliverable**: the exact artifact (complete script, ready-to-send email, recommendation with reasons, paste-ready prompt), with the length and format its channel expects.