Techies KPI — Plugins

1The two plugins, at a glance

Both live in one marketplace (techies) at the repo TechiesApp/techies-kpi-plugin. Install only the one(s) for your role.

2One-time: connect the marketplace

Do this once in Claude Code, then install whichever plugin you need.

/plugin marketplace add TechiesApp/techies-kpi-plugin
# then reload so it's available
/reload-plugins

3Staff plugin — techies-kpi Staff

Generate your weekly AI-Engineer Transformation Profile from your own Claude Code history and submit just the metrics.

Install

/plugin install techies-kpi@techies
/reload-plugins

One-time: your submit token

P&C gives you a token out-of-band. Add it to your shell profile (e.g. ~/.zshrc):

export TECHIES_KPI_TOKEN="…the token P&C gave you…"

Open a new terminal afterward. Never commit the token or paste it into code.

Use it — every Friday

Run /weekly-kpi. It reads your own ~/.claude history for the last 7 days, scores six dimensions 0–5, saves a local my-ai-profile-<date>.html you keep, and submits the metrics (six stages + two short notes).

4Manager plugin — techies-kpi-manager Manager

Review your team's furnished reports and file a monthly manager report. Managers only — gated by the kpi_manager allowlist (ask P&C for access).

Install

/plugin install techies-kpi-manager@techies
/reload-plugins

First-run sign-in (one time)

The manager plugin authenticates you by email (no shared token). Run a command — if you're not signed in, it prints the exact login command to run in your terminal:

! bash "${CLAUDE_PLUGIN_ROOT}/scripts/mgr-auth.sh" login

Enter your @techiesapp.io email → a 6-digit code is emailed to you → paste it. Your session is cached locally (~/.config/techies-kpi/, owner-only) and refreshes automatically. (Use the code, not the link — the link is for the dashboard.)

/monthly-team-review — the monthly review

Run monthly. It reads the team, helps you draft a per-developer coaching assessment + status + focus, asks you for the technical (GitHub) read, writes a local manager-report-<date>.json for you to edit, and submits it. Human judgment only — no numeric auto-score.

/team-status-range — on-demand snapshot

Read-only. See the team's status for any date range (nothing is furnished or submitted):

/team-status-range 2026-05-01 2026-05-31
# no dates given → defaults to the last 30 days
/team-status-range

5Keeping plugins updated

When P&C ships a new version, pull it in Claude Code:

/plugin marketplace update techies
/plugin update techies-kpi            # staff
/plugin update techies-kpi-manager    # manager
/reload-plugins

Tip: if a command prints a path with an old version number (e.g. 0.1.0), you're on a stale copy — update and re-run the command so it uses the new path.

6Troubleshooting

7How this is (and isn't) used

• Coaching, not a verdict. Reports feed growth and 1:1s; nothing auto-triggers an employment action.
• No raw-volume metric. Stages are developmental; prompt counts are never scored — shown only as a coarse adoption signal.
• Metadata, not transcripts. The staff plugin submits metrics; the manager plugin submits judgment. Neither sends prompt text.
• Managers ≠ open access. Team data is P&C-confidential; only allowlisted managers can read it, and only through the curated API.