MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
P4 DAM (Digital Asset Management) workflows — search, browse, tag, review, and manage digital assets via P4 MCP tools.
$ npx skills add perforce/p4mcp-server --skill p4-dam-workflows -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install perforce/p4mcp-server p4-dam-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-dam-workflows .claude/skills/p4-dam-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-dam-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-dam-workflows into .claude/skills/p4-dam-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-dam-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-dam-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-dam-workflows -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install perforce/p4mcp-server p4-dam-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-dam-workflows .agents/skills/p4-dam-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-dam-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-dam-workflows into .agents/skills/p4-dam-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-dam-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-dam-workflows -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install perforce/p4mcp-server p4-dam-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-dam-workflows .cursor/skills/p4-dam-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-dam-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-dam-workflows into .cursor/skills/p4-dam-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-dam-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-dam-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-dam-workflows -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install perforce/p4mcp-server p4-dam-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-dam-workflows .gemini/skills/p4-dam-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-dam-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-dam-workflows into .gemini/skills/p4-dam-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-dam-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-dam-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-dam-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-dam-workflows .github/skills/p4-dam-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-dam-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-dam-workflows into .github/skills/p4-dam-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-dam-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-dam-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-dam-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-dam-workflows .opencode/skills/p4-dam-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-dam-workflows" agent skill from https://github.com/perforce/p4mcp-server/tree/main/skills/p4-dam-workflows into .opencode/skills/p4-dam-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "p4-dam-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.
p4-dam-workflowsP4 DAM (Digital Asset Management) workflows — search, browse, tag, review, and manage digital assets via P4 MCP tools.
P4 Dam Workflows is an agent skill from perforce/p4mcp-server. P4 DAM (Digital Asset Management) workflows — search, browse, tag, review, and manage digital assets via P4 MCP tools. Use when discovering, searching, filtering, reviewing, or managing assets stored in P4 DAM.
Its SKILL.md is about 4.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.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit a8b284d. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
P4DAM_API_KEYAUTH_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
P4 Dam Workflows loads about 4.1k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 1,472 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.
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.
The full file from perforce/p4mcp-server at commit a8b284d, republished under its MIT licence (© perforce). 1,472 words, ~4,094 tokens.
.claude/skills/p4-dam-workflows/SKILL.md (or your agent's skills folder).P4.HTH.URL property set (points at the P4 DAM instance).P4DAM_API_KEY environment variable. Without a key, P4 DAM tools are not registered at all — a warning is logged at startup.--readonly.| Tool | Purpose |
|---|---|
query_p4dam_projects | List projects. Accepts search_term (matches name, short name, or description). |
query_p4dam_repositories | List repositories in a project. Accepts search_term (matches short name). |
query_p4dam_helix_classic_branches | List Helix Classic branches in a helix_classic repository. |
| Tool | Purpose |
|---|---|
query_p4dam_assets | Search assets by keyword/filters — use when you don't have a depot path yet. |
query_p4dam_asset | Fetch full metadata for a single known asset by depot path. |
fetch_p4dam_media | Fetch and render a thumbnail, preview, or file image. |
regenerate_p4dam_preview | Trigger async regeneration of thumbnail and preview for an asset revision. |
query_p4dam_assets filters: search_term, project_ids (UUIDs), repository_ids (UUIDs), path (wildcard depot path patterns, e.g. //depot/art/*.png), name (filename wildcard), tag, file_extension, exclude_file_extension, user, from_size / to_size (bytes), from_date / to_date (ISO 8601), all_revisions, max_results, offset.
query_p4dam_asset params: depot_path (required), identifier (changeset), project_id (short name or UUID), repository_id (UUID, or short name if project_id is also provided), include.
query_p4dam_asset include values:
commit, latest_commit, custom_attributes, weblinks, asset_bundle, asset_bundle_origin, parent_asset_bundles, helix_classic_branch_matches, stream_view_matches, spritefile_review, comments, all_commentsfile_count, scene_refsfetch_p4dam_media: Pass thumbnail_url, preview_url, sprite_url, or file_url from search/asset results. thumbnail_url, preview_url, and sprite_url are only present for image files (nil for non-image assets). Returns the image directly for visual display.
regenerate_p4dam_preview: Trigger P4Search to regenerate the thumbnail and preview for a specific asset revision. Params: depot_path (required), commit_id (changeset number, required). Returns accepted immediately — regeneration is async. Requires P4.P4Search.URL and P4.P4Search.AUTH_TOKEN on the P4 server.
| Tool | Purpose |
|---|---|
create_p4dam_asset_bundle | Create a named collection of depot files scoped for review. |
update_p4dam_asset_bundle | Update description, view_paths, or hero_file_path. |
delete_p4dam_asset_bundle | Delete an asset bundle (prompts for confirmation). |
sync_p4dam_asset_bundle | Sync bundle's depot files to local P4CLIENT workspace. |
Create flow: query_p4dam_projects → query_p4dam_repositories → (if helix_classic: query_p4dam_helix_classic_branches) → create_p4dam_asset_bundle.
| Tool | Purpose |
|---|---|
query_p4dam_file_reviews | List file reviews in a project. Filter by depot_path. |
query_p4dam_file_review | Fetch single review with full detail including download_url. |
create_p4dam_file_review | Create a file review (single-file or asset bundle). |
update_p4dam_file_review | Update state, name, view_paths, description, position. |
delete_p4dam_file_review | Delete a review (prompts for confirmation). |
query_p4dam_file_reviews include: weblinks.
| Tool | Purpose |
|---|---|
query_p4dam_workflows | List workflows. include accepts states, transition_rules, projects. |
query_p4dam_workflow | Fetch a single workflow by short name or UUID. |
query_p4dam_workflow_states | List states for a workflow (name, short_name, kind, color, position). |
State kinds: open (initial), review (under review), done (terminal).
| Tool | Purpose |
|---|---|
create_p4dam_comment | Post a comment on a file review, a file within a review, a committed file, or as a reply. |
create_p4dam_comment types and required fields:
type | Required | Use case |
|---|---|---|
file_review | project, repository, file_review | Comment on an asset bundle file review |
file_review_file | project, repository, file_review, path | Comment on a specific file inside a file review |
commit_file | project, repository, commit, path | Comment on a committed file or asset bundle without a review |
comment | comment | Reply to an existing comment |
path is a relative path within the repository (e.g. renders/hero.png), not a full depot path.
For commit_file on helix_stream repos: also pass stream_path. For helix_classic: also pass helix_classic_branch.
| Tool | Purpose |
|---|---|
query_p4dam_custom_attribute_templates | List available custom attribute templates for a project (name, type, allowed values). |
update_p4dam_asset_custom_attributes | Set or remove custom attribute values on one or more assets. |
Flow: query_p4dam_custom_attribute_templates(project_id=...) → pick template UUID → update_p4dam_asset_custom_attributes(paths=[...], create=[{uuid, value}]).
Attribute types: text (any string), single-select (one of available_values), multi-select (list of available_values), checkbox ("true" / "false").
| Tool | Purpose |
|---|---|
update_p4dam_asset_tags | Add/remove user tags and auto-tags on one or more assets in one call. |
Tag operations: create (add tags), delete (remove user tags), delete_auto (remove auto-generated tags). Supports individual files, specific revisions (identifier in path), recursive folders (//depot/folder/...), and propagatable for future revisions.
query_p4dam_assets — each result item| Field | Notes |
|---|---|
depot_path | Full depot path — pass to query_p4dam_asset or fetch_p4dam_media(file_url) |
name | Filename only |
commit | Changeset number |
rev | Revision number |
size | File size in bytes |
mime | MIME type (e.g. image/png) |
file_type | Perforce file type |
user | Last modifier username |
updated_at | ISO 8601 timestamp |
tags | User-applied tags (array of strings) |
auto_tags | Auto-generated tags (array of strings) |
blurhash | Present only for image files |
thumbnail_url | Pass to fetch_p4dam_media — image files only, nil otherwise |
preview_url | Pass to fetch_p4dam_media — image files only, nil otherwise |
file_url | Pass to fetch_p4dam_media for the raw file |
sprite | { sprite_url, metadata } — animation sprite sheet, image files only |
The response wrapper also contains total_count, more_results, and next_offset for pagination.
query_p4dam_asset — top-level fields| Field | Notes |
|---|---|
depot_path | Full depot path |
thumbnail_url | Pass to fetch_p4dam_media — present only for image files |
preview_url | Pass to fetch_p4dam_media — present only for image files |
file_url | Raw file download URL |
asset_bundle.uuid | Pass as bundle_id to update_p4dam_asset_bundle / delete_p4dam_asset_bundle |
asset_bundle.view_paths | Pass directly to sync_p4dam_asset_bundle |
asset_bundle.depot_path | Depot path of the .p4bundle file |
weblinks | Array of weblinks (included by default) |
custom_attributes | Custom metadata fields |
commit | Changeset object (included by default) |
latest_commit | Latest commit object (included by default) |
helix_classic_branch_matches | Matching Helix Classic branches (included by default) |
stream_view_matches | Matching stream views (included by default) |
query_p4dam_repositories — each result item| Field | Notes |
|---|---|
uuid | Pass as repository_id to other tools |
short_name | Pass as repository_id to other tools (also accepted) |
type | helix_stream or helix_classic — determines which additional param is required for bundles/reviews |
linked_streams | Array of stream paths — use stream value as stream_path when creating bundles/reviews for helix_stream repos |
default_identifier | Default branch/stream identifier |
query_p4dam_file_reviews — each result item| Field | Notes |
|---|---|
uuid | Pass as review_id to query_p4dam_file_review, update_p4dam_file_review, delete_p4dam_file_review |
name | Review name |
state | Current workflow state object (short_name, kind) |
depot_path | File or bundle being reviewed |
view_paths | Scope of the review |
asset_bundle | Linked asset bundle (if bundle review) |
thumbnail_url | Pass to fetch_p4dam_media — present only for image files |
preview_url | Pass to fetch_p4dam_media — present only for image files |
download_url | Bundle download URL — only present when asset_bundle is set |
creator | Creator account object |
query_p4dam_workflow_states — each result item| Field | Notes |
|---|---|
short_name | Pass as state when creating or updating a file review (not name) |
name | Human-readable display name |
kind | open, review, or done |
color | Hex color string |
position | Ordering within the workflow |
# By keyword (filename, tags, or custom attributes):
query_p4dam_assets(search_term="monocycle")
# Narrow by project or file type:
query_p4dam_assets(project_ids=["proj-uuid"], file_extension=["png", "svg"])
# By date range or size:
query_p4dam_assets(search_term="hero", from_date="2024-01-01", to_date="2024-12-31")
query_p4dam_assets(from_size=1048576, to_size=52428800) # 1 MB – 50 MB
# By depot path pattern:
query_p4dam_assets(path=["//depot/art/characters/..."])
query_p4dam_assets(path=["//depot/renders/*.png"])query_p4dam_asset(depot_path="//stream/images/logo.png")To include file_review, comments, or all_comments, pass project_id and repository_id. Find them in stream_view_matches or helix_classic_branch_matches from the initial result:
query_p4dam_asset(depot_path="//stream/images/logo.png", project_id="proj-uuid", repository_id="repo-uuid", include=["file_review", "all_comments"])# From query_p4dam_assets result:
fetch_p4dam_media(url=<result.thumbnail_url>)
# From query_p4dam_asset result (higher resolution):
fetch_p4dam_media(url=<result.preview_url>)query_p4dam_projects(search_term="characters")
query_p4dam_repositories(project_id="proj-uuid")
create_p4dam_asset_bundle(
depot_path="//stream/bundles/q3-chars.p4bundle",
project="proj-uuid",
repository="repo-uuid",
view_paths=["//stream/renders/...", "//stream/textures/..."],
stream_path="//stream/mainline",
description="Q3 character renders"
)# Get view_paths from asset_bundle section:
query_p4dam_asset(depot_path="//stream/bundles/q3-chars.p4bundle", include=["asset_bundle"])
sync_p4dam_asset_bundle(view_paths=<asset_bundle.view_paths>)# Discover the state short_name first:
query_p4dam_workflows(include=["states"])
create_p4dam_file_review(
project_id="my-project",
name="Q3 hero renders — art director pass",
depot_path="//stream/bundles/q3-chars.p4bundle",
view_paths=["//stream/renders/..."],
state="open"
)query_p4dam_workflow_states(workflow_id="default_workflow")
update_p4dam_file_review(project_id="my-project", review_id="review-uuid", state="in-review")# Tag a single file:
update_p4dam_asset_tags(paths=[{"path": "//stream/renders/hero.png"}], create=["hero", "q3-final"])
# Tag an entire folder recursively:
update_p4dam_asset_tags(paths=[{"path": "//stream/renders/..."}], create=["q3"])
# Remove a tag:
update_p4dam_asset_tags(paths=[{"path": "//stream/renders/hero.png"}], delete=["wip"])
# Propagate to future revisions:
update_p4dam_asset_tags(paths=[{"path": "//stream/renders/hero.png"}], create=["hero"], propagatable=true)query_p4dam_assets first to discover assets; switch to query_p4dam_asset for full metadata on a known depot path.query_p4dam_asset results, indicate which extra data can be fetched by re-calling with additional include values: comments (comments on the queried revision only), all_comments (comments across all revisions), file_count (number of files in a bundle), scene_refs (referenced files).all_revisions=false (default) in asset searches unless you need history — latest-only is faster.query_p4dam_asset results include thumbnail_url, preview_url, or sprite_url, the asset is an image — render it via fetch_p4dam_media. These fields are only present for image files.query_p4dam_asset returns commit, always show "Submitted on {date} by {author} (#{changeset})" followed by the commit description truncated to 512 characters. If latest_commit is present and differs from commit, also show "You're viewing changeset #{commit.number}, latest is #{latest_commit.number} from {date}".query_p4dam_asset returns a non-empty scene_refs, indicate that this file has referenced files, and list each by depot_path. Mark entries where exists is false as missing. Render thumbnail_url via fetch_p4dam_media if present.
Applies to both query_p4dam_assets and query_p4dam_asset.query_p4dam_asset returns custom_attributes, list them as "{name}: {value}", skipping entries where template.hidden is true.query_p4dam_asset returns weblinks, list them as markdown links: [{text}]({url}), falling back to the URL as text if text is blank.query_p4dam_asset returns file_reviews, show each as: "{name}" — state {state.short_name}, created by {creator}.query_p4dam_asset returns an asset_bundle object, indicate that this asset is an asset bundle.query_p4dam_asset returns an asset_bundle_origin object (but no asset_bundle), indicate that this is a .p4bundle file derived from a bundle at a different depot path (e.g. branched or integrated).query_p4dam_asset returns a parent_asset_bundles object, indicate that this asset is part of an asset bundle.project_id and repository_id accept either UUID or short name in all tools.stream_path is required when creating bundles or reviews. Find it in linked_streams from query_p4dam_repositories.helix_classic_branch is required. Use query_p4dam_helix_classic_branches to discover it.state field value is ignored by the backend — new reviews always start in the project's first open state.sync_p4dam_asset_bundle requires P4CLIENT to be set in the environment.helix_classic_branch_matches, list each entry as "{short_name} ({project.short_name} / {repository.short_name})", marking the default branch. Applies to both query_p4dam_assets and query_p4dam_asset.stream_view_matches, list each entry as "{stream_path} ({project.short_name} / {repository.short_name})".© perforce, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/p4-dam-workflows of perforce/p4mcp-server.
Open the folder on GitHubat commit a8b284d
P4 Dam 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 Dam Workflows this skillperforce/p4mcp-server | 122 | — | ~4.1k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 64 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Fastmcp Client CLIPrefectHQ/fastmcp | 28k | 1 repos | ~823 | Automated safety check: Pass | Apache-2.0 | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
PrefectHQ/fastmcp
Query and invoke tools on MCP servers using fastmcp list and fastmcp call.
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.
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
perforce/p4mcp-server
P4 changelist workflows — create, list, submit, shelve, unshelve, and manage changelists and shelved files via P4 MCP tools.
perforce/p4mcp-server
P4 code review workflows — discover, create, vote, comment, transition, and manage reviews via P4 MCP tools.
perforce/p4mcp-server
P4 file operations — query content, history, annotations, diffs, and modify files (add, edit, delete, move, sync, resolve) via P4 MCP tools.
perforce/p4mcp-server
P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools.
perforce/p4mcp-server
P4 workspace setup and management — create, configure, sync, and switch workspaces via P4 MCP tools.
Works with
Categories
P4 DAM (Digital Asset Management) workflows — search, browse, tag, review, and manage digital assets via P4 MCP tools. P4 Dam Workflows is an agent skill from perforce/p4mcp-server. P4 DAM (Digital Asset Management) workflows — search, browse, tag, review, and manage digital assets via P4 MCP tools.
P4 Dam Workflows fits situations like: managing assets stored in P4 DAM; tasks that involve MCP servers.
Run `npx skills add perforce/p4mcp-server --skill p4-dam-workflows -a claude-code`. Or copy the skill folder (skills/p4-dam-workflows in perforce/p4mcp-server) into .claude/skills/p4-dam-workflows in your project. Claude Code loads it when a task matches its description.
Run `npx skills add perforce/p4mcp-server --skill p4-dam-workflows -a codex`. Or copy the skill folder (skills/p4-dam-workflows in perforce/p4mcp-server) into .agents/skills/p4-dam-workflows in your project. Codex loads it when a task matches its description.
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-dam-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-dam-workflows, .gemini/skills/p4-dam-workflows, .github/skills/p4-dam-workflows and .opencode/skills/p4-dam-workflows in your project.
Going by SKILL.md and its folder, P4 Dam Workflows needs credentials named P4DAM_API_KEY and AUTH_TOKEN. Our summary lists: A credential in P4DAM_API_KEY; A credential in AUTH_TOKEN.
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.
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.
P4 Dam Workflows is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with P4 Dam Workflows: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Fastmcp Client CLI (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.