How do I install the P4 Workspace Setup skill?

Run npx skillmds@latest add perforce/p4-workspace-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the P4 Workspace Setup skill do?

Workspace Setup & Management It is listed under Coding & Dev Tools on SkillMD.

Is P4 Workspace Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with P4 Workspace Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is P4 Workspace Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published P4 Workspace Setup?

perforce (@perforce) published this skill. Their other Agent Skills are listed on their SkillMD profile.

P4 Workspace Setup by perforce — Agent Skill

Name: P4 Workspace Setup
Author: perforce

File contents

Workspace Setup & Management

Use the query_workspaces and modify_workspaces tools to manage P4 client workspaces.

Querying Workspaces

Action	Purpose	Key Parameters
`list`	List workspaces with filters	`user`, `max_results`
`get`	Get full workspace spec	`workspace_name`
`type`	Check if workspace is stream or classic	`workspace_name`
`status`	Get workspace sync status	`workspace_name`

Modifying Workspaces

Action	Purpose	Key Parameters
`create`	Create a new workspace	`name`, `specs`
`update`	Update workspace spec fields	`name`, `specs`
`delete`	Delete a workspace (requires approval)	`name`
`switch`	Switch active workspace	`name`

Common Workflows

Create a stream workspace

query_streams → list to find available streams
modify_workspaces → create with specs containing the stream depot path
modify_files → sync to populate the workspace

Create a classic workspace

modify_workspaces → create with specs containing view mappings (depot-to-local paths)
modify_files → sync to populate the workspace

Check workspace state

query_workspaces → get to see the current spec
query_workspaces → type to check if it's stream-bound or classic
query_workspaces → status to see sync state (have vs head revisions)

Switch between workspaces

query_workspaces → list to see available workspaces
modify_workspaces → switch to set the active workspace

Best Practices

Use stream workspaces when working with P4 streams — they auto-configure the view mapping from the stream spec.
Set the workspace root to a directory that exists and is writable.
Use query_workspaces → status to check for out-of-date files before starting work.
Delete workspaces only when you're sure no pending changelists reference them.
Each workspace must have a unique name on the P4 server.

---name: p4-workspace-setupdescription: Workspace Setup & Management---# Workspace Setup & ManagementUse the `query_workspaces` and `modify_workspaces` tools to manage P4 client workspaces.## Querying Workspaces| Action | Purpose | Key Parameters ||--------|---------|----------------|| `list` | List workspaces with filters | `user`, `max_results` || `get` | Get full workspace spec | `workspace_name` || `type` | Check if workspace is stream or classic | `workspace_name` || `status` | Get workspace sync status | `workspace_name` |## Modifying Workspaces| Action | Purpose | Key Parameters ||--------|---------|----------------|| `create` | Create a new workspace | `name`, `specs` || `update` | Update workspace spec fields | `name`, `specs` || `delete` | Delete a workspace (requires approval) | `name` || `switch` | Switch active workspace | `name` |## Common Workflows### Create a stream workspace1. `query_streams` → `list` to find available streams2. `modify_workspaces` → `create` with `specs` containing the stream depot path3. `modify_files` → `sync` to populate the workspace### Create a classic workspace1. `modify_workspaces` → `create` with `specs` containing view mappings (depot-to-local paths)2. `modify_files` → `sync` to populate the workspace### Check workspace state1. `query_workspaces` → `get` to see the current spec2. `query_workspaces` → `type` to check if it's stream-bound or classic3. `query_workspaces` → `status` to see sync state (have vs head revisions)### Switch between workspaces1. `query_workspaces` → `list` to see available workspaces2. `modify_workspaces` → `switch` to set the active workspace## Best Practices- Use stream workspaces when working with P4 streams — they auto-configure the view mapping from the stream spec.- Set the workspace `root` to a directory that exists and is writable.- Use `query_workspaces` → `status` to check for out-of-date files before starting work.- Delete workspaces only when you're sure no pending changelists reference them.- Each workspace must have a unique name on the P4 server.

Frequently asked questions

P4 Workspace Setup