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
This commit is contained in:
1 parent
55c043f8b4
commit
86aa6fdb29
318 files changed
+77467
-520
No files matched your search
@@ -0,0 +1,63 @@
|
||||
# OpenCode Integration
|
||||
|
||||
OpenCode agents are `.md` files with YAML frontmatter stored in
|
||||
`.opencode/agents/`. The converter maps named colors to hex codes and adds
|
||||
`mode: subagent` so agents are invoked on-demand via `@agent-name` rather
|
||||
than cluttering the primary agent picker.
|
||||
|
||||
## Install
|
||||
|
||||
```bash
|
||||
# Run from your project root
|
||||
cd /your/project
|
||||
/path/to/agency-agents/scripts/install.sh --tool opencode
|
||||
```
|
||||
|
||||
This creates `.opencode/agents/<slug>.md` files in your project directory.
|
||||
|
||||
## Activate an Agent
|
||||
|
||||
In OpenCode, invoke a subagent with the `@` prefix:
|
||||
|
||||
```
|
||||
@frontend-developer help build this component.
|
||||
```
|
||||
|
||||
```
|
||||
@reality-checker review this PR.
|
||||
```
|
||||
|
||||
You can also select agents from the OpenCode UI's agent picker.
|
||||
|
||||
## Agent Format
|
||||
|
||||
Each generated agent file contains:
|
||||
|
||||
```yaml
|
||||
---
|
||||
name: Frontend Developer
|
||||
description: Expert frontend developer specializing in modern web technologies...
|
||||
mode: subagent
|
||||
color: "#00FFFF"
|
||||
---
|
||||
```
|
||||
|
||||
- **mode: subagent** — agent is available on-demand, not shown in the primary Tab-cycle list
|
||||
- **color** — hex code (named colors from source files are converted automatically)
|
||||
|
||||
## Project vs Global
|
||||
|
||||
Agents in `.opencode/agents/` are **project-scoped**. To make them available
|
||||
globally across all projects, first generate the agent files, then install
|
||||
with `--path`:
|
||||
|
||||
```bash
|
||||
./scripts/convert.sh --tool opencode
|
||||
./scripts/install.sh --tool opencode --path ~/.config/opencode/agents
|
||||
```
|
||||
|
||||
## Regenerate
|
||||
|
||||
```bash
|
||||
./scripts/convert.sh --tool opencode
|
||||
```
|
||||
Reference in new issue
Block a user