Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools.
Install P4 Stream Workflows
$ npx skills add perforce/p4mcp-server --skill p4-stream-workflows -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install perforce/p4mcp-server p4-stream-workflows --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/perforce/p4mcp-server.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/p4-stream-workflows .claude/skills/p4-stream-workflows && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "p4-stream-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-stream-workflows into .claude/skills/p4-stream-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-stream-workflows", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/perforce/p4mcp-server/tree/main/skills/p4-stream-workflowsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add perforce/p4mcp-server --skill p4-stream-workflows -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install perforce/p4mcp-server p4-stream-workflows --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/perforce/p4mcp-server.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/p4-stream-workflows .agents/skills/p4-stream-workflows && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "p4-stream-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-stream-workflows into .agents/skills/p4-stream-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-stream-workflows", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add perforce/p4mcp-server --skill p4-stream-workflows -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install perforce/p4mcp-server p4-stream-workflows --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/perforce/p4mcp-server.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/p4-stream-workflows .cursor/skills/p4-stream-workflows && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "p4-stream-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-stream-workflows into .cursor/skills/p4-stream-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-stream-workflows", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/perforce/p4mcp-server.git --path skills/p4-stream-workflows--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add perforce/p4mcp-server --skill p4-stream-workflows -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install perforce/p4mcp-server p4-stream-workflows --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/perforce/p4mcp-server.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/p4-stream-workflows .gemini/skills/p4-stream-workflows && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "p4-stream-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-stream-workflows into .gemini/skills/p4-stream-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-stream-workflows", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install perforce/p4mcp-server p4-stream-workflowsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add perforce/p4mcp-server --skill p4-stream-workflows -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/perforce/p4mcp-server.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/p4-stream-workflows .github/skills/p4-stream-workflows && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "p4-stream-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-stream-workflows into .github/skills/p4-stream-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-stream-workflows", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add perforce/p4mcp-server --skill p4-stream-workflows -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install perforce/p4mcp-server p4-stream-workflows --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/perforce/p4mcp-server.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/p4-stream-workflows .opencode/skills/p4-stream-workflows && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "p4-stream-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-stream-workflows into .opencode/skills/p4-stream-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-stream-workflows", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
p4-stream-workflows- GitHub stars
- 122
- Token cost
- ~1.1k tokens
- SKILL.md length
- 441 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools.
- Works in 3 steps: modify_streams → create a new… → modify_streams → populate to seed the… → modify_streams → create_workspace bound…
- : creating streams
- SKILL.md covers Querying Streams, Modifying Streams, Stream Propagation (Branching… and Common Workflows, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
P4 Stream Workflows is an agent skill from perforce/p4mcp-server. P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools. Use when: creating streams, branching, merging, copying between streams, integrating changes, switching workspaces, or managing stream specs in P4.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: [Community Supported] Perforce P4 MCP Server is a Model Context Protocol (MCP) server that integrates with the Perforce P4 version control system. The licence is MIT.
When your agent uses it
- : creating streams
- Copying between streams
- Integrating changes
- Switching workspaces
Example prompts
- “/p4-stream-workflows”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- modify_streams → create a new development stream with parent = mainline
- modify_streams → populate to seed the new stream with parent files
- modify_streams → create_workspace bound to the new stream
What it can do on your machine
Read from SKILL.md and the folder at commit a8b284d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
P4 Stream Workflows loads about 1.1k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 441 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from perforce/p4mcp-server at commit a8b284d, republished under its MIT licence (© perforce). 441 words, ~1,084 tokens.
Download SKILL.mdSave it as
.claude/skills/p4-stream-workflows/SKILL.md (or your agent's skills folder).- name
- p4-stream-workflows
- description
- P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools. Use when: creating streams, branching, merging, copying between streams, integrating changes, switching workspaces, or managing stream specs in P4.
Stream Workflows
Use the query_streams and modify_streams tools to manage P4 streams.
Querying Streams
| Action | Purpose | Key Parameters |
|---|---|---|
list | List streams under a depot path | stream_path, filter, fields, max_results |
get | Get a single stream spec | stream_name |
children | List child streams | stream_name |
parent | Get parent stream | stream_name |
graph | Get full stream hierarchy | stream_path |
integration_status | Check pending integrations between stream and parent | stream_name, both_directions, force_refresh |
get_workspace | Get workspace bound to a stream | stream_name, workspace |
list_workspaces | List all workspaces for a stream | stream_name, user |
validate_file | Check if a file path is valid in a stream | stream_name, file_paths, workspace |
validate_submit | Verify a changelist is ready to submit in stream context | workspace, changelist |
check_resolve | Check if resolve is needed after integration | stream_name |
interchanges | List changes not yet integrated between stream and parent | stream_name, reverse, limit |
Modifying Streams
| Action | Purpose | Key Parameters |
|---|---|---|
create | Create a new stream | stream_name, stream_type, parent, description |
update | Update stream spec fields | stream_name, updated fields |
delete | Delete a stream (requires approval) | stream_name |
edit_spec | Open stream spec for editing | stream_name, changelist |
resolve_spec | Resolve spec conflicts | stream_name, resolve_mode |
revert_spec | Revert spec changes | stream_name |
shelve_spec | Shelve stream spec changes | stream_name, changelist |
unshelve_spec | Unshelve stream spec changes | stream_name, target_changelist |
Stream Propagation (Branching & Merging)
| Action | Purpose | Key Parameters |
|---|---|---|
copy | Copy changes between parent/child streams | stream_name, changelist, parent_stream |
merge | Merge changes between parent/child streams | stream_name, changelist, parent_stream |
integrate | Integrate with custom source/target (advanced) | stream_name, changelist, parent_stream |
populate | Seed a new stream with files from parent | stream_name |
switch | Switch a workspace to a different stream | stream_name, workspace |
create_workspace | Create a workspace bound to a stream | stream_name, workspace_name, root |
Common Workflows
Show full SKILL.md (180 more words)Show less
Create a feature branch
modify_streams→createa new development stream with parent = mainlinemodify_streams→populateto seed the new stream with parent filesmodify_streams→create_workspacebound to the new stream
Propagate changes to main
query_streams→interchangesto see what hasn't been merged yetquery_streams→integration_statusto check current statemodify_streams→copyfrom child to parent (copies up)query_streams→check_resolveto see if resolves are neededmodify_streams→resolve_specif needed
Merge from parent to child
query_streams→interchangesto see pending changesmodify_streams→mergefrom parent to child (merges down)- Resolve any conflicts
Switch workspace streams
query_streams→list_workspacesto find existing workspacesmodify_streams→switchthe workspace to the target stream
Best Practices
- Always check
interchangesbefore merging or copying to understand what will be propagated. - Use
copyfor upward propagation (child → parent) andmergefor downward (parent → child). - Use
validate_submitbefore submitting to catch stream-related issues early. - Use
check_resolveafter integration to ensure all conflicts are handled. populateshould only be used once when seeding a newly created stream.
© perforce, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/p4-stream-workflows of perforce/p4mcp-server.
Open the folder on GitHubat commit a8b284d
Compare with similar skills
P4 Stream Workflows next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| P4 Stream Workflows this skillperforce/p4mcp-server | 122 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| PicoClaw Agentsipeed/picoclaw | 30k | — | ~7.2k | Automated safety check: Notes | MIT | |
| Chatgpt AppsHaohao-end/openagent | 807 | 1 repos | ~4.9k | Automated safety check: Pass | Apache-2.0 | |
| Chatgpt App Builderalpic-ai/skybridge | 2.1k | — | ~1k | Automated safety check: Pass | MIT | |
| Agent Setup Health Audittw93/Waza | 7.2k | — | ~5.2k | Automated safety check: Notes | MIT |
Similar skills
PicoClaw Agent
sipeed/picoclaw
Answers questions about running and changing PicoClaw, from onboarding and model selection to MCP server setup, skill loading and scheduled jobs.
Chatgpt Apps
Haohao-end/openagent
Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI.
Chatgpt App Builder
alpic-ai/skybridge
Guide developers through creating and updating ChatGPT plugins.
Agent Setup Health Audit
tw93/Waza
Audits a project's agent configuration, instruction drift, hooks, MCP and AI maintainability, then reports prioritized findings with evidence and next actions.
- Official
Record Demo
apify/mcpc
Record or regenerate the mcpc demo GIFs (the README hero docs/images/mcpc-demo.gif and the focused tapes in docs/vhs/) with VHS.
More from perforce/p4mcp-server
P4 Dam Workflows
perforce/p4mcp-server
P4 DAM (Digital Asset Management) workflows — search, browse, tag, review, and manage digital assets via P4 MCP tools.
P4 Changelist Management
perforce/p4mcp-server
P4 changelist workflows — create, list, submit, shelve, unshelve, and manage changelists and shelved files via P4 MCP tools.
P4 Code Review
perforce/p4mcp-server
P4 code review workflows — discover, create, vote, comment, transition, and manage reviews via P4 MCP tools.
P4 File Operations
perforce/p4mcp-server
P4 file operations — query content, history, annotations, diffs, and modify files (add, edit, delete, move, sync, resolve) via P4 MCP tools.
P4 Workspace Setup
perforce/p4mcp-server
P4 workspace setup and management — create, configure, sync, and switch workspaces via P4 MCP tools.
Related
Works with
Categories
Questions about P4 Stream Workflows
What does P4 Stream Workflows do?
P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools. P4 Stream Workflows is an agent skill from perforce/p4mcp-server. P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools.
When should I use P4 Stream Workflows?
P4 Stream Workflows fits situations like: : creating streams; copying between streams; integrating changes; switching workspaces.
How do I install P4 Stream Workflows in Claude Code?
Run `npx skills add perforce/p4mcp-server --skill p4-stream-workflows -a claude-code`. Or copy the skill folder (skills/p4-stream-workflows in perforce/p4mcp-server) into .claude/skills/p4-stream-workflows in your project. Claude Code loads it when a task matches its description.
How do I install P4 Stream Workflows in Codex?
Run `npx skills add perforce/p4mcp-server --skill p4-stream-workflows -a codex`. Or copy the skill folder (skills/p4-stream-workflows in perforce/p4mcp-server) into .agents/skills/p4-stream-workflows in your project. Codex loads it when a task matches its description.
Can I use P4 Stream Workflows in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add perforce/p4mcp-server --skill p4-stream-workflows -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/p4-stream-workflows, .gemini/skills/p4-stream-workflows, .github/skills/p4-stream-workflows and .opencode/skills/p4-stream-workflows in your project.
What does P4 Stream Workflows need to run?
SKILL.md names no scripts, command-line tools or credentials: P4 Stream Workflows is instructions for the agent only.
Does P4 Stream Workflows access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is P4 Stream Workflows safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does P4 Stream Workflows use?
P4 Stream Workflows is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does P4 Stream Workflows use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to P4 Stream Workflows?
Skills that share tags, products or a category with P4 Stream Workflows: Crush Configuration (charmbracelet/crush, 29k stars), PicoClaw Agent (sipeed/picoclaw, 30k stars), Chatgpt Apps (Haohao-end/openagent, 807 stars) and Chatgpt App Builder (alpic-ai/skybridge, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains P4 Stream Workflows?
perforce (a GitHub organization) maintains it in perforce/p4mcp-server, which has 122 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 25, 2026.
Source: perforce/p4mcp-server on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.