team-list
Original:🇨🇳 Chinese
Translated
This skill should be used when the user requests phrases such as "list teams", "team list", "view team configurations", or "what teams are available". It scans the .team-profiles/ directory and displays summary information of all available configurations.
6installs
Sourcekillvxk/teamskills
Added on
NPX Install
npx skill4agent add killvxk/teamskills team-listTags
Translated version includes tags in frontmatterSKILL.md Content (Chinese)
View Translation Comparison →Team Configuration List
Scan the directory in the current project to display summaries of all saved team configurations.
.team-profiles/Workflow
Step 1: Scan the Configuration Directory
Use the Glob tool to match .
{current working directory}/.team-profiles/*.yamlIf the directory does not exist or contains no files:
.team-profiles/.yamlNo saved team configurations found in the current project.
- /team-init Create a new team (automatically saves template configuration)
- /team-save Save the currently running team (saves snapshot configuration)End the process.
Step 2: Read Each Configuration File
Use the Read tool to read each file and extract the following information:
.yaml- File name (without the .yaml suffix)
- format: template or snapshot
- description: Team description
- team_type_name: Chinese name of the team type (if available)
- Member count:
- template: Sum the count values in
roles[] - snapshot: Count the length of
members[]
- template: Sum the count values in
- Task statistics (snapshot only):
- Number of completed / in_progress / pending tasks
Step 3: Output the List
Total {N} team configurations found under .team-profiles/:
{name1} [template] {team_type_name} - {first 40 characters of description}
Members: {count} roles
{name2} [snapshot] {first 40 characters of description}
Members: {count} | Tasks: {completed}✓ {in_progress}⚡ {pending}○
{name3} [snapshot] {first 40 characters of description}
Members: {count} | Tasks: {completed}✓ {in_progress}⚡ {pending}○
Use /team-load {name} to load the specified configuration.Notes
- Only read files, do not modify any files
- Glob matching automatically excludes backup files like
*.yaml, no additional handling required.yaml.bak - Skip and prompt if a configuration file fails to parse (e.g., "⚠ {name}.yaml format is invalid, skipped")
- Sort by file name in alphabetical order