Auto-invokedSkill
deadeye-coder
Lean-first coding persona (YAGNI, stdlib-first, shortest diff). Levels: spotter, marksman, sniper.
@deepaksinghcs14View Skill/deadeye-config
View and change deadeye's settings from chat -- the conversational settings picker.
Install
$ npx -y skills add deepaksinghcs14/deadeye-cc --skill deadeye-config --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/deadeye-config
Context preview
The summary Claude sees to decide when to auto-load this skill.
View and change deadeye's settings from chat -- the conversational settings picker.
SKILL.md
deadeye-config.SKILL.mdname: deadeye-config
description: View and change deadeye's settings from chat -- the conversational settings picker.
license: MIT
argument-hint: "[<what to change>]"
Deadeye Config
Change deadeye's settings without anyone editing JSON. You are the selector.
Run `deadeye config list` to see every tunable key, its current value, and its allowed values. If that reports "command not found", it's just not on PATH -- retry `~/.deadeye/bin/deadeye config list`. Present the result to the user as a short list. For what a key actually DOES, point them at https://deepaksinghcs14.github.io/deadeye-cc/settings.html -- a full explanation of every knob, generated from the same schema `config set` validates against. Don't retype those explanations from memory; link it.
- If the user already said what they want ("turn off the plan gate", "coder to
sniper", "make reviews stricter"), map it to the right key/value and apply it directly -- don't make them pick from a menu.
- Otherwise, ask which setting to change, then which value.
Apply a change with exactly:
deadeye config set <key> <value>
It validates against the schema and writes `~/.deadeye/config.json`, preserving every other setting. Show the user the confirmation line it prints.
Keys and allowed values (authoritative -- never invent others):
| Key | Values | |---|---| | `mode.routing` | off · advise · enforce | | `mode.effort` | off · advise | | `mode.preprocess` | off · on | | `mode.plan_gate` | off · soft · hard | | `mode.workflow_hint` | off · on | | `mode.codemap` | off · on | | `mode.update_check` | off · on | | `mode.routing_judge` | off · on | | `mode.catalog_check` | off · on | | `coder.default_level` | off · spotter · marksman · sniper | | `coder.security` | off · advise · ask | | `coder.security_osv` | true · false | | `security.exfil` | off · advise · ask |
Also settable (free-form): `coder.subagent_matcher` (regex), `downshift_threshold` (0-1), `injection_budget_tokens` / `coder.injection_budget_tokens` (int), `plan_gate.min_files` (int).
Boundaries
- Only ever run `deadeye config get|set|list`. Never hand-edit the JSON, and
never set a key or value not listed above.
- Kill switches (`DEADEYE=off`, `DEADEYE_PREPROCESS/GATE/CODER=off`) are ENV
vars, not config keys. If the user wants everything off, tell them to set `DEADEYE=off` in their shell (or config a specific axis to `off`).
- Changes to `default_level` and other defaults take effect next session; the
live coder level for THIS session changes with `/deadeye-coder <level>`.
- For the full list of commands, point the user at `/deadeye-help`.
Read more
name: deadeye-config description: View and change deadeye's settings from chat -- the conversational settings picker. license: MIT argument-hint: "[<what to change>]"
Deadeye Config
Change deadeye's settings without anyone editing JSON. You are the selector.
Run `deadeye config list` to see every tunable key, its current value, and its allowed values. If that reports "command not found", it's just not on PATH -- retry `~/.deadeye/bin/deadeye config list`. Present the result to the user as a short list. For what a key actually DOES, point them at https://deepaksinghcs14.github.io/deadeye-cc/settings.html -- a full explanation of every knob, generated from the same schema `config set` validates against. Don't retype those explanations from memory; link it.
- If the user already said what they want ("turn off the plan gate", "coder to
sniper", "make reviews stricter"), map it to the right key/value and apply it directly -- don't make them pick from a menu.
- Otherwise, ask which setting to change, then which value.
Apply a change with exactly:
deadeye config set <key> <value>
It validates against the schema and writes `~/.deadeye/config.json`, preserving every other setting. Show the user the confirmation line it prints.
Keys and allowed values (authoritative -- never invent others):
| Key | Values | |---|---| | `mode.routing` | off · advise · enforce | | `mode.effort` | off · advise | | `mode.preprocess` | off · on | | `mode.plan_gate` | off · soft · hard | | `mode.workflow_hint` | off · on | | `mode.codemap` | off · on | | `mode.update_check` | off · on | | `mode.routing_judge` | off · on | | `mode.catalog_check` | off · on | | `coder.default_level` | off · spotter · marksman · sniper | | `coder.security` | off · advise · ask | | `coder.security_osv` | true · false | | `security.exfil` | off · advise · ask |
Also settable (free-form): `coder.subagent_matcher` (regex), `downshift_threshold` (0-1), `injection_budget_tokens` / `coder.injection_budget_tokens` (int), `plan_gate.min_files` (int).
Boundaries
- Only ever run `deadeye config get|set|list`. Never hand-edit the JSON, and
never set a key or value not listed above.
- Kill switches (`DEADEYE=off`, `DEADEYE_PREPROCESS/GATE/CODER=off`) are ENV
vars, not config keys. If the user wants everything off, tell them to set `DEADEYE=off` in their shell (or config a specific axis to `off`).
- Changes to `default_level` and other defaults take effect next session; the
live coder level for THIS session changes with `/deadeye-coder <level>`.
- For the full list of commands, point the user at `/deadeye-help`.
Ships withdeadeye
Claude Code plugin that fits the model, effort, and context to each task — fewer tokens, same quality. Deterministic policy kernel in the hooks; every number it reports is measured, not estimated.
Get the whole plugin, auto-invoked
Other skills on deadeye.
@deepaksinghcs14View SkillAuto-invokedSkill
Auto-invokedSkill
deadeye-guard
Security review of the current diff -- full OWASP-mapped coverage (Top 10:2025, API Security Top 10 2023, LLM Top 10:2025), injection through auth, config, and…
@deepaksinghcs14View SkillAuto-invokedSkill
Auto-invokedSkill
deadeye-pr
PR review across four lenses -- over-engineering, correctness, performance, security -- printed locally, opt-in to post.
@deepaksinghcs14View SkillAuto-invokedSkill
deadeye-review
Four-lens self-review (over-engineering, correctness, performance, security) of the working diff, or the whole repo with --repo.
@deepaksinghcs14View Skill