Team (team-*)v1.0.0

team-eo-attr

Skills and tools for the EO Attributes team — weekly operational/stability review for employee-organization-service attributes and validation-service

by Thomas DidierjeanView on GitHub ↗
eoemployee-organizationattributesvalidation-serviceops-reviewoperational-reviewdatadogteam

EO Attributes Plugin

Skills and tools for the EO Attributes team (team:attributes / PTECH_EO_ATTRIBUTES), covering employee-organization-service (attributes) and validation-service.

Owned by the Employee Organization (EO) team.

Installation

claude plugin install team-eo-attr@personio-claude-code-marketplace

Prerequisites

  • Datadog MCP (claude.ai Datadog) authenticated via /mcp — SLOs, metrics, monitors, events, E2E tests.
  • Atlassian MCP authenticated via /mcp — reads the Operational excellence epic and its child tickets, and publishes the report to Confluence.
  • gh CLI authenticated (gh auth status) — verifies what actually shipped behind each ticket.
  • Personio VPN — for the SDLC security metrics endpoint (Security section). Optional; the section is skipped with a note if unreachable.

What does this plugin do?

/eo-attributes-ops-review Skill

Produces the weekly operational review data pack for the Attributes team and publishes it to Confluence as a draft page in the EO Attributes Ops Review folder. Scope is employee-organization-service (attributes only) + validation-service, env:prod, team:attributes. The primary window is the last 7 days, compared against 30 days (SLOs) and the prior 3 weeks (alerts).

# Run for the week ending today
/eo-attributes-ops-review

# Or for an explicit range
/eo-attributes-ops-review "March 29 to April 4"

What the skill does:

  1. Prerequisites & connectivity — gates Datadog MCP, Atlassian MCP, gh, and (optionally) the SDLC security endpoint before gathering any data.
  2. Gather data — SLOs (7d vs 30d), monitor status, alert events (7d vs prior 3 weeks), error-tracking issues, incidents, security findings (team:attributes), and E2E tests (e2e_test_owner:attributes, last 24h).
  3. Read the previous review — diffs against last week's findings and action items.
  4. Drill into slow/failing endpoints — breaks red SLOs down by resource_name/status to a 1–2 sentence root cause.
  5. Cross-reference the Operational excellence epic — verifies every cited ticket against its merged GitHub PRs (Jira Done ≠ shipped fix), recording the shipping date and folding each ticket into its finding's own section (no standalone cross-reference section).
  6. Publish — assembles the report (everything linked: dashboard, tickets, PRs, error-tracking issues, incidents) and creates/updates a draft Confluence page titled YYYY-MM-DD EO Attributes Ops Review under the EO Attributes Ops Review folder, then shares the link.

Exact queries live in the skill's QUERIES.md; the output format and publishing steps live in confluence-publisher.md.

Authorization

  • Read-only data gathering: all metrics use read MCP calls, gh search, and a read-only curl to the SDLC metrics endpoint.
  • Reports findings only — never creates or edits Jira tickets.
  • The only write is the Confluence page, created as a draft for the user to review and publish manually.