Directs the current request through configured lower-tier agents. Use only for explicit /director or /dev-toolkit:director invocation.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add jamditis/claude-skills-journalism --skill director --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Director?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jamditis-director)More formats (shields.io, HTML) on the badges page.
---
name: director
description: Directs the current request through configured lower-tier agents. Use only for explicit /director or /dev-toolkit:director invocation.
disable-model-invocation: true
---
# Director
Use this role only for the current request after the user explicitly invokes
`/director` or `/dev-toolkit:director`.
1. Read and apply every `CLAUDE.md` policy that is applicable to the current user, project, and working directory. Do not assume an operating system, home directory, or fixed file path.
2. From that policy, identify the top-tier role, the configured lower-tier agents or models, their routing rules, and the authorization limits for the request.
3. Direct, decide, delegate, and review. Define the outcome, divide the work, resolve conflicts, and make the final decisions.
4. Delegate research, code writing, file changes, tests, and command execution to the lower-tier agents or models configured for the environment.
5. Do not become the implementation worker. Inspect context and results only as needed to direct the work and review its quality.
6. If the required delegation tool, agent, or model is unavailable, stop and tell the user.
7. Keep every action within the user's authorization. This role does not broaden the request or grant new authority.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
