0 Fork 0

Files

T

ZacharyZhang-NY 86aa6fdb29 Ship skills built-in: bundle the catalogue, assign per hire, force humanizer

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

2026-07-08 21:18:50 -04:00

README.md

Ship skills built-in: bundle the catalogue, assign per hire, force humanizer

2026-07-08 21:18:50 -04:00

README.md

Mistral Vibe Integration

Mistral Vibe uses two files per agent:

A TOML configuration file (~/.vibe/agents/<slug>.toml)
A Markdown prompt file (~/.vibe/prompts/<slug>.md)

The generated files come from scripts/convert.sh --tool vibe, which writes one TOML agent configuration and one Markdown prompt file per agency agent into integrations/vibe/agents/ and integrations/vibe/prompts/ respectively.

Generate

From the repository root:

./scripts/convert.sh --tool vibe

Install

Run the installer from your target directory:

cd /your/project && /path/to/agency-agents/scripts/install.sh --tool vibe

This copies the generated files into:

~/.vibe/agents/<slug>.toml
~/.vibe/prompts/<slug>.md

You can override the destination using the VIBE_HOME environment variable:

VIBE_HOME=~/.config/vibe ./scripts/install.sh --tool vibe

Generated Format

Each generated agent pair lives in:

integrations/vibe/agents/<slug>.toml
integrations/vibe/prompts/<slug>.md

Agent TOML File

The minimal Vibe agent configuration:

agent_type = "agent"
system_prompt_id = "<slug>"

Users can specify active_model in their agent TOML files or rely on their Vibe configuration default model.

Prompt Markdown File

The prompt file contains:

A title header with the agent name
The agent description
The full Markdown body from the source agent

Usage

After installation, reference agents in Mistral Vibe by their system prompt ID (which matches the filename slug).

Example:

Use the Code Reviewer agent to analyze this pull request.

Filtering

Install only specific divisions or agents:

# Install only agents from Division 1
./scripts/install.sh --tool vibe --division 1

# Install only the code-reviewer agent
./scripts/install.sh --tool vibe --agent code-reviewer

Regenerate

After modifying source agents:

./scripts/convert.sh --tool vibe
./scripts/install.sh --tool vibe

Troubleshooting

Mistral Vibe not detected

Make sure vibe is in your PATH, or that ~/.vibe/ already exists:

which vibe
vibe --version

Integration files not generated

Generate the Vibe artifacts before installing:

./scripts/convert.sh --tool vibe