Skip to content

Rebrand (Part 2/2): update generated templates, skills, and docs #182

@placerda

Description

@placerda

Why

Part 2 of 2 of the rebrand from agentops-toolkitagentops-accelerator. Once the distribution rename in Part 1 lands, propagate the new name and the human brand ("AgentOps Toolkit" → "AgentOps Accelerator") through everything users read or regenerate: workflow templates, skills, and docs.

Without this, generated CI workflows in users' repos still say pip install agentops-toolkit[...], marketplace skill listings still say "AgentOps Toolkit", and every tutorial still trains the wrong brand.

Depends on

Part 1 (distribution + VSIX rename, #181) must merge first.

Changes

Generated workflow & pipeline templates (highest user impact — these ship to every project that runs agentops workflow generate):

  • src/agentops/templates/workflows/*.yml (8 files)
  • src/agentops/templates/pipelines/azuredevops/*.yml (8 files)
  • src/agentops/templates/agent-server/Dockerfile, README.md
  • src/agentops/templates/agent.yaml

Skills (synced copies — keep both in sync via the existing sync script):

  • src/agentops/templates/skills/**/SKILL.md (canonical)
  • plugins/agentops/skills/**/SKILL.md (VSIX-bundled)

Documentation + brand cascade ("AgentOps Toolkit" → "AgentOps Accelerator", agentops-toolkitagentops-accelerator):

  • README.md (title, badges, install commands)
  • AGENTS.md, CHANGELOG.md (new top entry calling out the rename + "regenerate workflows after upgrade")
  • .github/copilot-instructions.md
  • docs/tutorial-prompt-agent-quickstart.md, docs/tutorial-hosted-agent-quickstart.md, docs/tutorial-end-to-end.md
  • docs/release-process.md, docs/ci-github-actions.md, docs/foundry-evaluation-sdk-built-in-evaluators.md
  • .vscode/settings.json
  • All SKILL.md headers and template YAML comment headers that say "AgentOps Toolkit" in prose

Tests:

  • tests/unit/test_cicd.py (asserts generated templates contain pip install agentops-toolkit[...] — flip to the new name)

Note for downstream users

Existing generated workflows in users' repos still say pip install agentops-toolkit[...]. The tombstone release from Part 1 keeps them green until the user regenerates. The CHANGELOG entry must call out "run agentops workflow generate --force after upgrading" so users know to refresh.

Acceptance

  • All 16 workflow/pipeline templates updated.
  • Both SKILL.md copies updated; sync script run.
  • No remaining agentops-toolkit or "AgentOps Toolkit" in markdown/yaml outside CHANGELOG.md history.
  • python -m pytest tests/unit/test_cicd.py -q green.
  • Full suite green: python -m pytest tests/ -x -q.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions