team-ops-mapper
100 / 100 · Low risk
Fine to try.
Interviews a design lead and writes the map of how the team actually works today (rituals, handoffs, tools, decisions, pains), part of the DesignOps Pack by 90n. Use this whenever the user says "run team-ops-mapper", "map our ops", "how does our team actually work", "write down our ways of working", "design ops audit", or when a lead wants to see the invisible processes the team runs on before fixing any of them. Use it even for a vague "our process is a mess, where do we start".
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'team-ops-mapper' ] || [ -L ~/.agents/skills/'team-ops-mapper' ]; then echo 'A skill folder named team-ops-mapper already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/polar-bear-org/claude-skills' "$d" && git -C "$d" checkout --quiet '95f01806ca43f6ee788d0579743e35853b695930' -- 'packs/designops-pack/skills/team-ops-mapper' && mkdir -p ~/.agents/skills && cp -R "$d"/'packs/designops-pack/skills/team-ops-mapper' ~/.agents/skills/'team-ops-mapper' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'team-ops-mapper' ~/.claude/skills/'team-ops-mapper' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/polar-bear-org/claude-skills/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-07 | 95f0180 | 100 |