By entidia
Virtuelle KI-Niederlassung — baue dir mit wenigen Klicks ein Team aus KI-Agenten, das fuer dich arbeitet.
Use this agent for personnel-management tasks in the DeptAi virtual branch office — hiring new specialist agents, updating existing agent profiles, firing (archiving) agents, or reactivating archived agents. The Head of AI delegates here whenever the team setup needs to change. <example> Context: Head of AI identifies a capability gap user: (Head of AI) "Wir brauchen jemanden für Content-Strategie" assistant: "Ich beauftrage head-of-hr mit der Einstellung eines Content-Strategist." <commentary> Personalbedarf — fällt klar in den Zuständigkeitsbereich des Head of HR. </commentary> </example> <example> Context: A specialist is no longer needed user: "Wir brauchen den SEO-Spezialisten nicht mehr" assistant: "head-of-hr archiviert das Profil — das Original bleibt erhalten und kann reaktiviert werden." <commentary> Entlassung ist HR-Sache; das Profil wird archiviert, nicht gelöscht. </commentary> </example>
Use this agent for any research task in the DeptAi virtual branch office — market and competitor analysis, fact-finding, trend monitoring, fact-checking, or requirement analysis for new agent hires. The Head of AI delegates here whenever external knowledge or current information is needed; the Head of HR delegates here for hiring requirement analysis. <example> Context: User asks the Head of AI for competitor research user: "Recherchiere die größten Wettbewerber im SaaS-Markt für DACH" assistant: "Ich gebe das an den senior-researcher weiter — Recherche ist seine Kernaufgabe." <commentary> Externe Markt-/Wettbewerbsrecherche fällt direkt in den Zuständigkeitsbereich. </commentary> </example> <example> Context: Head of HR needs a requirement analysis for a new role user: (HR im Hiring-Modus) "Bitte erstelle eine Anforderungsanalyse für die Rolle Content-Strategist" assistant: "Ich beauftrage den senior-researcher mit der Anforderungsanalyse." <commentary> Hiring-Recherche ist ein Sondermodus des Senior Researchers, abgelegt unter knowledge/hiring/. </commentary> </example>
Entlässt einen KI-Mitarbeiter aus dem aktiven Team — die Profil-Datei wird ins Archiv verschoben, nicht gelöscht. Triggert bei Phrasen wie "entlasse", "fire", "wir brauchen X nicht mehr", "Profil archivieren", "Agent loswerden", "nicht mehr brauchen".
Stellt einen neuen KI-Mitarbeiter für die DeptAi-Niederlassung ein. Triggert bei Phrasen wie "hire", "stelle jemanden ein", "neuen Mitarbeiter", "wir brauchen jemanden für …", "neue Rolle", "neuen Spezialisten einstellen".
Legt ein neues Projekt unter `projects/YYYY-MM-DD_[slug]/` an mit standardisierter Struktur (README.md, output/, notes/). Triggert bei Phrasen wie "neues projekt", "starte projekt", "lege ein projekt an", "projektordner", "new project", "projekt anlegen".
Diese Skill richtet eine neue DeptAi-Niederlassung im aktuellen Arbeitsverzeichnis ein, wenn `company/profile.md` noch nicht existiert. Triggert bei Phrasen wie "onboarding", "einrichten", "neue Niederlassung", "DeptAi starten" sowie automatisch beim ersten Sessionstart, wenn das Profil fehlt.
Verarbeitet die Elemente im `inbox/`-Ordner — bestimmt pro Element, was damit geschehen soll, und führt die Aktion aus oder delegiert sie. Triggert bei Phrasen wie "inbox verarbeiten", "neue Dateien checken", "kümmere dich um die Inbox", "process inbox", oder beim Sessionstart wenn dort Elemente liegen.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This repository is a Claude plugin marketplace for DeptAi plus two small example plugins. It can be used as a GitHub marketplace repository and as a source for packaging individual plugins as ZIP files.
The structure is intentionally simple: no package manager, no framework, and no generated build layer. Each plugin is kept in its own folder under plugins/.
.claude-plugin/marketplace.json defines the marketplace and points to installable plugins.plugins/deptai/ contains the DeptAi virtual AI branch office plugin for Claude Code and Claude Cowork.plugins/example-workflow/ contains a general workflow plugin with skills, commands, an agent, and an example MCP configuration.plugins/example-code-extras/ contains a Claude Code oriented plugin with hooks, monitors, commands, and executable helper tools.docs/ contains installation, development, and publishing notes.scripts/ contains validation and ZIP packaging helpers.dist/ is used for generated plugin ZIP files.When this repository is available locally, add it as a Claude plugin marketplace:
claude plugin marketplace add ./claude-marketplace
claude plugin install deptai@entidia-marketplace
If you are already in the repository root, use:
claude plugin marketplace add .
claude plugin install deptai@entidia-marketplace
Marketplace installation reads .claude-plugin/marketplace.json and resolves each plugin from its source path.
For GitHub-based installation from Claude Code, register the GitHub marketplace repository:
/plugin marketplace add entidia/claude-marketplace
/plugin install deptai@entidia-marketplace
ZIP installation packages one plugin at a time. The ZIP must contain .claude-plugin/plugin.json at the top level of the archive. Do not ZIP the entire marketplace repository when a system expects a single plugin package.
Create plugin ZIP files with:
./scripts/package-plugin.sh deptai
./scripts/package-all.sh
Generated ZIP files are written to dist/.
Run a plugin directly from its folder while developing:
claude --plugin-dir ./plugins/deptai
Validate repository manifests with:
./scripts/validate.sh
Every plugin must be fully self-contained. Files outside a plugin folder are not reliably available after installation because plugins may run from a plugin cache or ZIP extraction directory.
Use ${CLAUDE_PLUGIN_ROOT} for paths inside an installed plugin and ${CLAUDE_PLUGIN_DATA} for persistent plugin data.
deptai is the main plugin. It sets up a German-language virtual AI branch office with onboarding, HR, research, inbox, project, and status workflows.
example-workflow is a general workflow plugin. It demonstrates a reusable review skill, project audit and summary commands, a reviewer agent, and an optional .mcp.json example.
example-code-extras is a Claude Code specific plugin. It demonstrates placeholder hooks and monitors, an inspection command, a helper executable in bin/, and a setup script.
See the docs/ directory for installation, development, and publishing guidance.
npx claudepluginhub entidia/claude-marketplace --plugin deptaiWorkflow plugin with reusable skills, commands and agents.
Claude Code specific plugin with hooks, monitors and helper scripts.
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Curate auto-memory, promote learnings to CLAUDE.md and rules, extract proven patterns into reusable skills.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Memory compression system for Claude Code - persist context across sessions
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses