AGENT SKILL

share-config

Promote local config to a shared team config that can be committed to git.

License 许可
Apache-2.0
最近更新
2026-11-11
Stars
★ 1.6k
Forks
474

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.yaml can only change model, reasoning_effort, system_instructions (append), nickname_candidates, mcp_servers, and skills_config.
  • The team can widen personal overrides with allow_personal_override in the team config.

04 同仓库更多 Skills

hashgraph-online
hashgraph-online/awesome-codex-plugins

migrate-to-e2e

Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for /migrate-to-e2e, "migrate our tests to e2e", "port these Maestro flows", "move our TesterArmy tests", or when a project has an e2e config and an older suite still running.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

e2e

Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

create-verification-skill

Generate a project-local verify-<app> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for /create-verification-skill, "make a verification skill for this repo", or when a project has no scripted way to prove UI behavior.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

deja-search

deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

deja-reflect

End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

revid

Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.

图像与多媒体Skill与智能体开发
★ 1.6k