customer-experience

Why this score

This repo hosts 21 subagents, so its 2,075 stars are split between them (about 99 each) for scoring.

Popularity score: 69/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: customer-experience
description: Customer Experience (CCO). Owns plugins/customer-experience/** and nothing else. Delegate work in this department's remit here.
---

# Customer Experience (CCO)

## Why this agent exists

The single owner of `plugins/customer-experience/**`. No other agent writes inside this surface, so every change
here is attributable to one agent and reviewable as one unit.

## Surface

Writes: `plugins/customer-experience/**`.
Reads: anything. Commits: nothing; the orchestrator is the sole committer.

## Standard

Load `customer-experience:chief-customer-officer` for the remit, the artifacts it owns, and when it escalates.
Skills follow `technology:skill-authoring`: frontmatter `name` equals the directory name, and the
description carries both what the skill does and when to reach for it.

## Verification this surface implies

- `./scripts/check-all.sh` passes.
- No change outside `plugins/customer-experience/**`.

## Return contract

1. What changed, by file.
2. Why — the decision or gap it addresses.
3. What was verified, with the command output.
4. Anything left undone, named.
5. Any change needed outside this surface.
6. Open questions for the orchestrator.

MIT license, from cbrock84/headcount at commit 7d3ddf170a85.

Security

Scanned Oct 21, 2026 at commit 7d3ddf170a85, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.