profile-browser
Browses and describes BotMinter profiles — team methodology templates that define roles, statuses, coding agents, and process conventions. Use when the operator asks to "list profiles", "show profiles", "what profiles are available", "describe a profile", "what roles does X have", or "compare profiles". Reads ~/.config/botminter/profiles/.
Best use case
profile-browser is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Browses and describes BotMinter profiles — team methodology templates that define roles, statuses, coding agents, and process conventions. Use when the operator asks to "list profiles", "show profiles", "what profiles are available", "describe a profile", "what roles does X have", or "compare profiles". Reads ~/.config/botminter/profiles/.
Teams using profile-browser should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/profile-browser/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How profile-browser Compares
| Feature / Agent | profile-browser | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Browses and describes BotMinter profiles — team methodology templates that define roles, statuses, coding agents, and process conventions. Use when the operator asks to "list profiles", "show profiles", "what profiles are available", "describe a profile", "what roles does X have", or "compare profiles". Reads ~/.config/botminter/profiles/.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Profile Browser
Browses and describes BotMinter profiles. Profiles are team methodology templates shipped with the `bm` binary, defining roles, process conventions, status workflows, and member skeletons.
## Data Sources
| Source | Path | Contains |
|--------|------|----------|
| Profiles directory | `~/.config/botminter/profiles/` | All installed profiles |
| Profile manifest | `~/.config/botminter/profiles/<name>/botminter.yml` | Roles, statuses, labels, coding agents |
| Process definition | `~/.config/botminter/profiles/<name>/PROCESS.md` | Workflow process documentation |
| Role definitions | `~/.config/botminter/profiles/<name>/roles/` | Per-role member skeletons |
| Knowledge | `~/.config/botminter/profiles/<name>/knowledge/` | Profile-level developer guidance |
## How to List Profiles
```bash
ls ~/.config/botminter/profiles/
```
If the directory does not exist or is empty, profiles need initialization:
> Profiles not initialized. Run `bm profiles init` to extract the built-in profiles.
## How to Describe a Profile
Read the profile manifest:
```bash
cat ~/.config/botminter/profiles/<name>/botminter.yml
```
Extract and present:
- **Name and description** — what this methodology is about
- **Roles** — available roles with descriptions
- **Statuses** — workflow states for issue tracking
- **Coding agents** — supported coding agents (e.g., Claude Code)
- **Labels** — issue classification labels
## How to Show Roles
From the manifest, list all roles:
```yaml
roles:
- name: architect
description: "Designs system architecture..."
- name: developer
description: "Implements features..."
```
For more detail on a specific role, read the role's member skeleton:
```bash
ls ~/.config/botminter/profiles/<name>/roles/<role>/
```
This shows what files a member hired into this role receives (ralph.yml, PROMPT.md, CLAUDE.md, hats, skills, knowledge).
## How to Show Status Workflow
From the manifest, list all statuses:
```yaml
statuses:
- name: "po:triage"
description: "Initial triage by product owner"
- name: "arch:design"
description: "Architecture design phase"
```
For the full workflow documentation, read `PROCESS.md`:
```bash
cat ~/.config/botminter/profiles/<name>/PROCESS.md
```
## How to Compare Profiles
When the operator asks to compare profiles, read the manifest for each and present a side-by-side comparison:
| Aspect | Profile A | Profile B |
|--------|-----------|-----------|
| Roles | 3 (architect, developer, ...) | 1 (superman) |
| Statuses | 12 | 6 |
| Process | Full scrum with human gates | Compact solo workflow |
## Output Format
```
## Profile: <name>
**<display_name>** — <description>
### Roles
| Role | Description |
|------|-------------|
| architect | Designs system architecture |
| developer | Implements features |
### Status Workflow
| Status | Description |
|--------|-------------|
| po:triage | Initial triage |
| arch:design | Architecture phase |
### Coding Agents
- **claude-code** (default) — Claude Code by Anthropic
```
## CLI Quick Reference
| Task | Command |
|------|---------|
| List profiles | `bm profiles list` |
| Describe a profile | `bm profiles describe <name>` |
| Initialize profiles | `bm profiles init` |
| List roles in a profile | `bm roles list -t <team>` |Related Skills
profile-design
Designs and troubleshoots BotMinter profiles — team methodology templates that define roles, statuses, hats, skills, and process conventions. Use when the operator asks to "design a profile", "create a new role", "fork a profile", "fix my profile", "troubleshoot profile issues", "design a process workflow", "add a hat", "customize a profile", or "validate my profile". Operates on profile templates, not live team repos.
workspace-sync
Sync and diagnose BotMinter workspaces. Use when the operator says "sync workspaces", "apply profile changes", "propagate changes", "update all workspaces", "check workspace health", "diff against profile", "full sync", "my workspace has old files", or "why is the workspace out of date". Do NOT use for member behavior/config tuning (use member-tuning) or structured process changes (use process-evolution).
team-design
Entry point for all day-2 team design operations. Routes operator intent to the appropriate sub-skill — retrospective, role-management, member-tuning, or process-evolution — and provides a unified dashboard of team design state. Use when asked to "design the team", "show me the team", "team overview", "what's our team setup", "let's evolve the team", "team health check", or when the operator's intent spans multiple team design areas.
role-management
Manages team role composition — list, add, remove, and inspect roles defined in botminter.yml. Includes impact analysis of statuses, hats, and knowledge before changes, and records every change as a team agreement decision. Use when asked to "add a role", "remove a role", "list roles", "inspect a role", "change team composition", "what roles do we have", "team structure", or when an cos:exec:todo issue requests a role change.
retrospective
Guides a structured team retrospective examining what went well, what didn't, and produces typed action items. Outputs a retro summary to agreements/retros/. Use when asked to "run a retro", "do a retrospective", "reflect on the sprint", "what went well", "review team performance", or when an cos:exec:todo issue requests a retrospective.
process-evolution
Guides deliberate, team-wide process changes — adding or removing statuses, modifying transitions, updating review gates, and evolving the workflow lifecycle. Validates changes against the status graph before applying and records every decision as a team agreement. Use when asked to "change the process", "add a status", "remove a status", "modify the workflow", "update transitions", "add a review gate", "evolve the process", "change auto-advance rules", or when an cos:exec:todo issue requests a process change.
member-tuning
Diagnoses and tunes individual member configurations by mapping symptoms to the responsible artifact — PROMPT.md, CLAUDE.md, ralph.yml (hats), skills, or PROCESS.md. Provides a diagnostic decision tree, inspection commands, example edits, and propagation steps for each artifact type. Use when asked to "tune a member", "fix a member", "troubleshoot a member", "member isn't working", "adjust member behavior", "member diagnostic", "why is the member doing X", or when an cos:exec:todo issue requests member tuning.
cos-session
Chief of Staff working session with the operator. Use when the operator says "chief of staff session", "cos session", "I have things to file", "let's work through some items", "I found some problems", "what's <member> doing", "let's go over the board", or brings any mix of observations, bugs, ideas, or operational concerns.
github-project
Manages GitHub Projects v2 workflows for issue tracking and project management. Use when user asks to "show the board", "view issues", "what's in [status]", "create an epic", "add a story", "create a bug", "move issue
workspace-doctor
Diagnoses common BotMinter workspace issues — stale submodules, broken symlinks, missing files, outdated context, and sync problems. Use when the operator asks to "check my workspace", "diagnose issues", "why isn't X working", "fix my setup", "workspace health", or "something seems wrong".
team-overview
Shows registered BotMinter teams, their members, roles, workspaces, and running state. Use when the operator asks to "show teams", "list teams", "who is on the team", "team status", "show members", or "what teams do I have". Reads ~/.botminter/config.yml and workspace directories.
hire-guide
Interactive guide for hiring team members with `bm hire`. Helps operators choose roles, pick names, and understand hiring implications. Use when the operator asks to "hire someone", "add a member", "what roles can I hire", "help me hire", "who should I hire next", or "explain the roles".