Delegate tasks to external LLM services (Gemini, Qwen) with quota, logging, and error handling. Use when tasks exceed context window or need cheaper processing. Do not use when task requires reasoning by Claude.
Delegates tasks to external LLM services for high-volume or cost-effective processing while retaining strategic reasoning.
/plugin marketplace add athola/claude-night-market/plugin install conjure@claude-night-marketThis skill inherits all available tools. When active, it can use any tool Claude has access to.
modules/cost-estimation.mdmodules/handoff-patterns.mdmodules/task-assessment.mdmodules/troubleshooting.mdshared-shell-execution.mddelegation-core:task-assessed)delegation-core:delegation-suitability)delegation-core:handoff-planned)delegation-core:results-integrated)A method for deciding when and how to delegate tasks to external LLM services. Core principle: delegate execution, retain high-level reasoning.
Delegate execution, retain reasoning. Claude handles architecture, strategy, design, and review. External LLMs perform data processing, pattern extraction, bulk operations, and summarization.
| 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 extraction, boilerplate generation, summarization.
delegation-core:task-assessed)Classify the task:
modules/task-assessment.md for classification criteria.Exit Criteria: Task classified with complexity level, context size, and delegation recommendation.
delegation-core:delegation-suitability)Verify prerequisites:
modules/handoff-patterns.md for checklist.modules/cost-estimation.md.Exit Criteria: Service authenticated, quotas verified, cost justified.
delegation-core:handoff-planned)Create a delegation plan:
modules/handoff-patterns.md for request template.Exit Criteria: Delegation plan documented.
delegation-core:results-integrated)Execute and validate results:
Exit Criteria: Results validated and integrated, usage logged.
For MCP servers that don't support Dynamic Client Registration (e.g., Slack), pre-configured OAuth client credentials can be provided:
claude mcp add <server-name> --client-id <id> --client-secret <secret>
This enables delegation workflows through MCP servers that require pre-configured OAuth, expanding the range of external services available for task delegation.
As an alternative to manual OAuth setup, users can configure MCP servers directly in claude.ai at claude.ai/settings/connectors. These connectors are automatically available in Claude Code when logged in with a claude.ai account — no claude mcp add or credential management required. This provides a browser-based auth flow that may be simpler for services with complex OAuth requirements.
When delegating tasks that modify files to subagents, use isolation: worktree in the agent frontmatter to run each agent in a temporary git worktree. This prevents file conflicts when multiple delegated agents operate in parallel on overlapping paths. The worktree is auto-cleaned if no changes are made; preserved with commits if the agent produces changes.
# Agent frontmatter for isolated delegation
isolation: worktree
Conjure uses leyline infrastructure:
| Leyline Skill | Used For |
|---|---|
quota-management | Track service quotas and thresholds. |
usage-logging | Session-aware audit trails. |
service-registry | Unified service configuration. |
error-patterns | Consistent error handling. |
authentication-patterns | Auth verification. |
See modules/cost-estimation.md for leyline integration examples.
For detailed service workflows:
Skill(conjure:gemini-delegation): Gemini CLI specifics.Skill(conjure:qwen-delegation): Qwen MCP specifics.Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.