claude-code-plugin-ref…
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.
Delegates execution to eight CLIs (Gemini, Qwen, MiniMax, GLM, Muse, Codex, OpenCode, Glimmer). Use for execution tasks. Do not use for secrets.
$ npx -y skills add athola/claude-night-market --skill delegation-core --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/delegation-coreContext preview
The summary Claude sees to decide when to auto-load this skill.
Delegates execution to eight CLIs (Gemini, Qwen, MiniMax, GLM, Muse, Codex, OpenCode, Glimmer). Use for execution tasks. Do not use for secrets.
name: delegation-core description: Delegates execution to eight CLIs (Gemini, Qwen, MiniMax, GLM, Muse, Codex, OpenCode, Glimmer). Use for execution tasks. Do not use for secrets. alwaysApply: false category: delegation-framework tags: - delegation - external-llm - gemini - qwen - minimax - glm - muse - codex - opencode - task-management - quality-control dependencies: - leyline:quota-management - leyline:usage-logging - leyline:service-registry - leyline:error-patterns - leyline:authentication-patterns tools: [] usage_patterns: - task-assessment - delegation-planning - quality-validation - integration-workflows complexity: intermediate model_hint: standard estimated_tokens: 600 progressive_loading: true modules: - modules/provider-onboarding.md - modules/task-assessment.md - modules/cost-estimation.md - modules/handoff-patterns.md - modules/troubleshooting.md references: - leyline/skills/quota-management/SKILL.md - leyline/skills/usage-logging/SKILL.md - leyline/skills/error-patterns/SKILL.md - leyline/skills/authentication-patterns/SKILL.md - leyline/skills/service-registry/SKILL.md - references/execution-modes.md
A method for deciding when and how to delegate tasks to external LLM services. Core principle: **delegate execution, retain high-level reasoning**.
**Delegation is on. Declining it is the step that takes a decision.**
Any conjure operation, mission phase, or workflow that reaches eligible work delegates it without being asked. Eligible means the work is execution rather than reasoning, which the philosophy below defines and `modules/task-assessment.md` classifies. An operator who wants delegation off says so once, in one of the two places under Declining Delegation.
This inverts the earlier framing, which listed the occasions on which to delegate and so made delegation something a caller had to remember. The occasions were correct and are now the exception list instead.
Delegation stops at the boundary the philosophy draws. Keep the work local when any of these hold:
should not leave the machine.
The first is the standing exception and covers most of what Claude does. The rest are the red flags `modules/task-assessment.md` already lists.
Two switches, environment over file.
| Scope | How | Effect | |-------|-----|--------| | One run | `CONJURE_DELEGATION=off` | No provider is probed or spawned | | One machine | `"enabled": false` in `~/.claude/hooks/delegation/config.json` | Same, until the key changes |
`CONJURE_DELEGATION` accepts `off`, `0`, `false`, `no` and their opposites, in any case. Setting it to an on spelling re-enables delegation that the config file turned off, so the narrower scope wins. A disabled delegator returns a result whose `fallback_reason` is `delegation_disabled` and spawns nothing, so opting out costs nothing.
`smart_delegate` works down the registry order and returns the first real answer. A provider that is missing, unauthenticated, failing, or answering with an empty stdout is recorded and the chain moves on.
When it reaches the end, it returns a result with `fallback_reason` set to `providers_exhausted` and an `attempts` trail naming what each provider did. **That result is the instruction to do the work locally.** Read it, say which providers were tried and why none answered, and then do the task yourself. Do not treat it as an error to report and stop on: a machine with no CLI installed is the ordinary case for this default, not a fault.
When the operator wants providers answering rather than falling back, `modules/provider-onboarding.md` carries the per-provider steps and the failure shapes that do not look like authentication problems. Start with `make -C plugins/conjure delegate-doctor`.
**Delegate execution, retain reasoning.** Claude handles architecture, strategy, design, and review. External LLMs perform data processing, pattern extraction, bulk operations, and summarization.
1. **Task Assessment**: Classify task by complexity and context size. 2. **Suitability Evaluation**: Check prerequisites and service fit. 3. **Handoff Planning**: Formulate request and document plan. 4. **Execution & Integration**: Run delegation, validate, and integrate results.
| Complexity | Context | Recommendation | |------------|---------|----------------| | High | Any | Keep local | | Low | Large | Delegate | | Low | Small | Either |
**High Complexity**: Architecture, design decisions, trade-offs, creative problem solving.
**Low Complexity**: Pattern counting, bulk extr
A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.
States load-bearing decisions, invariants, and weak points. Use when judging a design change. Do not use for gating; use night-market-change-control.
Rebuild the dev environment: uv, Python tiers, pins, traps. Use when onboarding or toolchain breaks. Do not use for daily commands; use night-market-operations.
Classify, gate, and review changes. Use when landing a PR, releasing, or amending rules. Do not use for failure triage; use night-market-debugging-playbook.
Search and record project memory (Discussions, journal, ADRs). Use before re-investigating anything. Do not use for settled battles; see failure-archaeology.
Bind loop 'done' to unfakeable gates. Use to harden egregore/herald loops or promote completion_integrity. Not for QA gates; use night-market-validation-and-qa.