share-config
Promote local config to a shared team config that can be committed to git.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- share-config
- description
- Promote local config to a shared team config that can be committed to git.
03 SKILL.md 正文
AgenTeam Share Config
Create a shared team config from your local config so collaborators can use the same pipeline, roles, and settings.
Process
1. Check Prerequisites
Verify .agenteam/config.yaml (or legacy agenteam.yaml) exists.
If not, tell the user: "No local config found. Run @ATeam init first."
2. Check for Existing Team Config
If .agenteam.team/config.yaml already exists:
- Tell the user: "Team config already exists at
.agenteam.team/config.yaml. Edit it directly to change team settings." - Stop. Do not overwrite.
3. Load and Strip Personal Fields
Load the current config. Strip ALL personal-allowlist fields from every role:
model(personal preference)reasoning_effort(personal preference)system_instructions(may contain personal addenda)nickname_candidates(personal display preference)mcp_servers(local/private tool wiring)skills_config(local/private skill wiring)
These fields are stripped because they should not become team policy.
The user can review and re-add team-relevant instructions manually.
Stripping model intentionally restores platform default inheritance for
collaborators and avoids sharing a pin that may be unavailable in their Codex
catalog.
4. Normalize Version
If version is not "2", set it to "2".
5. Write Team Config
mkdir -p .agenteam.team
Write the stripped config to .agenteam.team/config.yaml.
6. Summary
Print:
Team config created at .agenteam.team/config.yaml
What was stripped (personal-only fields):
- roles.*.model
- roles.*.reasoning_effort
- roles.*.system_instructions
- roles.*.nickname_candidates
- roles.*.mcp_servers
- roles.*.skills_config
Review it before committing. To customize:
- Team settings: edit .agenteam.team/config.yaml (tracked in git)
- Personal overrides: create .agenteam/config.yaml (gitignored)
Next steps:
git add .agenteam.team/
git commit -m "Add shared AgenTeam team config"
Notes
- The team config becomes the source of truth for pipeline, stages, gates, roles, and isolation.
- Personal overrides in
.agenteam/config.yamlcan only changemodel,reasoning_effort,system_instructions(append),nickname_candidates,mcp_servers, andskills_config. - The team can widen personal overrides with
allow_personal_overridein the team config.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.