ZacharyZhang-NY
86aa6fdb29
Skills no longer come from the user's ~/.agents library - most users have none, and the CEO branch that compiled the entire catalogue into its prompt overflowed the model context (1.1MB) and failed every CEO run. - Bundle "built-in skills/" with the app (extraResources) and stage it at startup into <profile>/builtin-skills as one dir-per-skill copy - both bundle shapes (SKILL.md dirs and flat category .md files) normalize into the same importable layout - Import the staged catalogue per org at startup and inside onboarding, so the CEO's first run already carries it - Forced house style: resolveRuntimeSnapshot unions the humanizer skill into every agent's runtime (CEO included) as a resolution rule - no binding row to forget, delete, or bypass; revoke_skill refuses it - CEO staffs hires with skills: hire_agent accepts a skills array, grant_skill/revoke_skill adjust later, list_skills now shows descriptions from skill frontmatter - Kill the c_suite compile-all branch; everyone resolves bindings-only, capped at 200k chars with omissions named in the prompt - Remove the Skills settings page and its import/sync/test IPC surface; drop ~/.agents discovery and the AGENTCOMPANY_NEW_SKILLS_ROOT seam in favor of AGENTCOMPANY_NEW_BUILTIN_SKILLS_DIR - Tests: staging/import/forced-resolution/cap units, real-bundle CI check, e2e asserts the tab is gone and the catalogue self-imports
Hermes Agency Agents Router Plugin
Generated by scripts/convert.sh --tool hermes.
This integration installs one Hermes plugin named agency-agents-router instead
of adding 232+ generated skills to skills.external_dirs. Hermes sees a
small fixed tool surface at startup, while the complete Agency roster is
stored on disk in data/agents.json and searched/loaded lazily.
Generated agent count: 232
Tools exposed to Hermes
agency_agents_search— find matching specialists by query/division.agency_agents_inspect— inspect one specialist's metadata or full body.agency_agents_load— compose one specialist prompt for the current task.agency_agents_delegate— delegate through Hermesdelegate_taskwhen available.
Specialist usage instruction for Hermes
When a Hermes project needs Agency specialists, explicitly ask Hermes to use
the agency-agents-router plugin/router and load only the specialists needed for
the current phase. Do not ask Hermes to install or preload the full Agency
roster as skills.
Recommended project instruction:
Use the agency-agents-router plugin. Search the Agency roster for the right
specialists, then load or delegate only the specific agents needed for each
part of the project. For multi-discipline projects, use multiple selected
specialists across the project, but keep routing lazy: do not preload the
full Agency roster and do not add agency-agents to skills.external_dirs.
Example:
For this Data Swami build, use the agency-agents-router plugin to pick
relevant Agency specialists. Search first, then delegate to selected agents
such as frontend, backend, UX, QA, data engineering, and product strategy as
needed. Load/delegate each specialist on demand rather than loading all
Agency agents at startup.
Install
./scripts/convert.sh --tool hermes
./scripts/install.sh --tool hermes
The installer copies the generated plugin to:
${HERMES_HOME:-~/.hermes}/plugins/agency-agents-router
It then enables agency-agents-router under plugins.enabled in the Hermes
config. It does not write to skills.external_dirs.