Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From hephaestus
Routes meta-agent requests to single-agent-creator, team-builder, or agentlas-packager based on task scope. Asks clarifying questions when ambiguous.
npx claudepluginhub agentlas-ai/hephaestus --plugin hephaestusHow this skill is triggered — by the user, by Claude, or both
Slash command
/hephaestus:mode-classificationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Choose `agentlas-packager` for existing agents, teams, repos, folders, ZIPs,
Routes agent-building requests (single, multi-team, packaging) into Agentlas architecture and generates runtime adapters, contracts, and cross-CLI commands.
Interactive six-phase questionnaire that designs focused sub-agent definitions — specialist, role, or team-lead — with proper frontmatter, tool permissions, and system prompts.
Creates Claude Code agents from scratch or by adapting templates. Guides requirements gathering, template selection, and file generation following Anthropic best practices (v2.1.63+).
Share bugs, ideas, or general feedback.
Choose agentlas-packager for existing agents, teams, repos, folders, ZIPs,
plugins, or adapters that need conversion, repair, cleanup, import, or release.
Choose team-builder for rosters, HQ, departments, multi-role workflows,
handoffs, policy, eval, QA, or parallel ownership.
Choose single-agent-creator for one installable worker.
If the choice would change files and the request is ambiguous, ask clarify questions before generating.