Agent skill

P4 Dam Workflows

by perforce in perforce/p4mcp-server

P4 DAM (Digital Asset Management) workflows — search, browse, tag, review, and manage digital assets via P4 MCP tools.

MITAuto-check passedAgent Workflows

Install P4 Dam Workflows

skills CLI
$ npx skills add perforce/p4mcp-server --skill p4-dam-workflows -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install perforce/p4mcp-server p4-dam-workflows --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
p4-dam-workflows
GitHub stars
122
Token cost
~4.1k tokens
SKILL.md length
1,472 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

P4 DAM (Digital Asset Management) workflows — search, browse, tag, review, and manage digital assets via P4 MCP tools.

  • Works in 8 steps: Search and filter assets → Fetch full metadata for a known asset → View a thumbnail or preview → …
  • Managing assets stored in P4 DAM
  • SKILL.md covers Prerequisites, Tool Reference, Response Fields and Common Workflows, plus 1 more section
  • Needs P4DAM_API_KEY and AUTH_TOKEN

What it does

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.

When your agent uses it

  • Managing assets stored in P4 DAM
  • Tasks that involve MCP servers

Example prompts

  • “/p4-dam-workflows”

Requirements

  • A credential in P4DAM_API_KEY
  • A credential in AUTH_TOKEN

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Search and filter assets
  2. Fetch full metadata for a known asset
  3. View a thumbnail or preview
  4. Create an asset bundle (helix_stream repo)
  5. Sync a bundle to local workspace
  6. Create a file review
  7. Transition a review to a new state
  8. Tag assets

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 these keys or tokens, usually read from environment variables:

    • P4DAM_API_KEY
    • AUTH_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k

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). 1,472 words, ~4,094 tokens.

Download SKILL.mdSave it as .claude/skills/p4-dam-workflows/SKILL.md (or your agent's skills folder).
name
p4-dam-workflows
description
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.

P4 DAM Workflows

Prerequisites

  • The P4 server must have the P4.HTH.URL property set (points at the P4 DAM instance).
  • The server must be started with a P4 DAM API key via the P4DAM_API_KEY environment variable. Without a key, P4 DAM tools are not registered at all — a warning is logged at startup.
  • Write tools (create, update, delete, sync) require the server to be started without --readonly.

Tool Reference

Discovery & Navigation
ToolPurpose
query_p4dam_projectsList projects. Accepts search_term (matches name, short name, or description).
query_p4dam_repositoriesList repositories in a project. Accepts search_term (matches short name).
query_p4dam_helix_classic_branchesList Helix Classic branches in a helix_classic repository.
ToolPurpose
query_p4dam_assetsSearch assets by keyword/filters — use when you don't have a depot path yet.
query_p4dam_assetFetch full metadata for a single known asset by depot path.
fetch_p4dam_mediaFetch and render a thumbnail, preview, or file image.
regenerate_p4dam_previewTrigger 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:

  • Default set: commit, latest_commit, custom_attributes, weblinks, asset_bundle, asset_bundle_origin, parent_asset_bundles, helix_classic_branch_matches, stream_view_matches, sprite
  • Require project/repository/stream or branch context: file_review, comments, all_comments
  • Extras: file_count, scene_refs

fetch_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.

Asset Bundles
ToolPurpose
create_p4dam_asset_bundleCreate a named collection of depot files scoped for review.
update_p4dam_asset_bundleUpdate description, view_paths, or hero_file_path.
delete_p4dam_asset_bundleDelete an asset bundle (prompts for confirmation).
sync_p4dam_asset_bundleSync 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.

File Reviews
ToolPurpose
query_p4dam_file_reviewsList file reviews in a project. Filter by depot_path.
query_p4dam_file_reviewFetch single review with full detail including download_url.
create_p4dam_file_reviewCreate a file review (single-file or asset bundle).
update_p4dam_file_reviewUpdate state, name, view_paths, description, position.
delete_p4dam_file_reviewDelete a review (prompts for confirmation).

query_p4dam_file_reviews include: weblinks.

Workflows
ToolPurpose
query_p4dam_workflowsList workflows. include accepts states, transition_rules, projects.
query_p4dam_workflowFetch a single workflow by short name or UUID.
query_p4dam_workflow_statesList states for a workflow (name, short_name, kind, color, position).

State kinds: open (initial), review (under review), done (terminal).

Comments
ToolPurpose
create_p4dam_commentPost 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:

typeRequiredUse case
file_reviewproject, repository, file_reviewComment on an asset bundle file review
file_review_fileproject, repository, file_review, pathComment on a specific file inside a file review
commit_fileproject, repository, commit, pathComment on a committed file or asset bundle without a review
commentcommentReply 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.

Custom Attributes
ToolPurpose
query_p4dam_custom_attribute_templatesList available custom attribute templates for a project (name, type, allowed values).
update_p4dam_asset_custom_attributesSet 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").

Tags
ToolPurpose
update_p4dam_asset_tagsAdd/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.


Response Fields

query_p4dam_assets — each result item
FieldNotes
depot_pathFull depot path — pass to query_p4dam_asset or fetch_p4dam_media(file_url)
nameFilename only
commitChangeset number
revRevision number
sizeFile size in bytes
mimeMIME type (e.g. image/png)
file_typePerforce file type
userLast modifier username
updated_atISO 8601 timestamp
tagsUser-applied tags (array of strings)
auto_tagsAuto-generated tags (array of strings)
blurhashPresent only for image files
thumbnail_urlPass to fetch_p4dam_media — image files only, nil otherwise
preview_urlPass to fetch_p4dam_media — image files only, nil otherwise
file_urlPass 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
FieldNotes
depot_pathFull depot path
thumbnail_urlPass to fetch_p4dam_media — present only for image files
preview_urlPass to fetch_p4dam_media — present only for image files
file_urlRaw file download URL
asset_bundle.uuidPass as bundle_id to update_p4dam_asset_bundle / delete_p4dam_asset_bundle
asset_bundle.view_pathsPass directly to sync_p4dam_asset_bundle
asset_bundle.depot_pathDepot path of the .p4bundle file
weblinksArray of weblinks (included by default)
custom_attributesCustom metadata fields
commitChangeset object (included by default)
latest_commitLatest commit object (included by default)
helix_classic_branch_matchesMatching Helix Classic branches (included by default)
stream_view_matchesMatching stream views (included by default)
query_p4dam_repositories — each result item
FieldNotes
uuidPass as repository_id to other tools
short_namePass as repository_id to other tools (also accepted)
typehelix_stream or helix_classic — determines which additional param is required for bundles/reviews
linked_streamsArray of stream paths — use stream value as stream_path when creating bundles/reviews for helix_stream repos
default_identifierDefault branch/stream identifier
Show full SKILL.md (573 more words)Show less
query_p4dam_file_reviews — each result item
FieldNotes
uuidPass as review_id to query_p4dam_file_review, update_p4dam_file_review, delete_p4dam_file_review
nameReview name
stateCurrent workflow state object (short_name, kind)
depot_pathFile or bundle being reviewed
view_pathsScope of the review
asset_bundleLinked asset bundle (if bundle review)
thumbnail_urlPass to fetch_p4dam_media — present only for image files
preview_urlPass to fetch_p4dam_media — present only for image files
download_urlBundle download URL — only present when asset_bundle is set
creatorCreator account object
query_p4dam_workflow_states — each result item
FieldNotes
short_namePass as state when creating or updating a file review (not name)
nameHuman-readable display name
kindopen, review, or done
colorHex color string
positionOrdering within the workflow

Common Workflows

1. Search and filter assets
# 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"])
2. Fetch full metadata for a known asset
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"])
3. View a thumbnail or preview
# 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>)
4. Create an asset bundle (helix_stream repo)
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"
)
5. Sync a bundle to local workspace
# 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>)
6. Create a file review
# 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"
)
7. Transition a review to a new state
query_p4dam_workflow_states(workflow_id="default_workflow")
update_p4dam_file_review(project_id="my-project", review_id="review-uuid", state="in-review")
8. Tag assets
# 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)

Best Practices

  • Use query_p4dam_assets first to discover assets; switch to query_p4dam_asset for full metadata on a known depot path.
  • After showing 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).
  • Leave all_revisions=false (default) in asset searches unless you need history — latest-only is faster.
  • When 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.
  • When 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}".
  • When 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.
  • When query_p4dam_asset returns custom_attributes, list them as "{name}: {value}", skipping entries where template.hidden is true.
  • When query_p4dam_asset returns weblinks, list them as markdown links: [{text}]({url}), falling back to the URL as text if text is blank.
  • When query_p4dam_asset returns file_reviews, show each as: "{name}" — state {state.short_name}, created by {creator}.
  • When query_p4dam_asset returns an asset_bundle object, indicate that this asset is an asset bundle.
  • When 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).
  • When 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.
  • For helix_stream repos, stream_path is required when creating bundles or reviews. Find it in linked_streams from query_p4dam_repositories.
  • For helix_classic repos, helix_classic_branch is required. Use query_p4dam_helix_classic_branches to discover it.
  • When creating a file review, the 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.
  • When results include a non-empty 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.
  • When results include a non-empty 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

Files

Just SKILL.md in skills/p4-dam-workflows of perforce/p4mcp-server.

Open the folder on GitHubat commit a8b284d

Compare with similar skills

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.

P4 Dam Workflows compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
P4 Dam Workflows this skillperforce/p4mcp-server122—~4.1kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Fastmcp Client CLIPrefectHQ/fastmcp28k1 repos~823Automated safety check: PassApache-2.0
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    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.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    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.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Fastmcp Client CLI

    PrefectHQ/fastmcp

    Query and invoke tools on MCP servers using fastmcp list and fastmcp call.

    28k GitHub starsUsed in 1 repo~823 tokens
    Agent WorkflowsAuto-check passed
  • 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.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Context Mode Output Sandbox

    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.

    26k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from perforce/p4mcp-server

  • P4 Changelist Management

    perforce/p4mcp-server

    P4 changelist workflows — create, list, submit, shelve, unshelve, and manage changelists and shelved files via P4 MCP tools.

    122 GitHub stars~848 tokensUpdated 12 days ago
    Auto-check passed
  • P4 Code Review

    perforce/p4mcp-server

    P4 code review workflows — discover, create, vote, comment, transition, and manage reviews via P4 MCP tools.

    122 GitHub stars~1.1k tokensUpdated 12 days ago
    Auto-check passed
  • 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.

    122 GitHub stars~930 tokensUpdated 12 days ago
    Auto-check passed
  • P4 Stream Workflows

    perforce/p4mcp-server

    P4 stream workflows — creation, branching, merging, copying, integration, switching, and spec management via P4 MCP tools.

    122 GitHub stars~1.1k tokensUpdated 12 days ago
    Auto-check passed
  • P4 Workspace Setup

    perforce/p4mcp-server

    P4 workspace setup and management — create, configure, sync, and switch workspaces via P4 MCP tools.

    122 GitHub stars~581 tokensUpdated 12 days ago
    Auto-check passed

Categories

Questions about P4 Dam Workflows

What does P4 Dam Workflows do?

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.

When should I use P4 Dam Workflows?

P4 Dam Workflows fits situations like: managing assets stored in P4 DAM; tasks that involve MCP servers.

How do I install P4 Dam Workflows in Claude Code?

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.

How do I install P4 Dam Workflows in Codex?

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.

Can I use P4 Dam 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-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.

What does P4 Dam Workflows need to run?

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.

Does P4 Dam 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 Dam 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 Dam Workflows use?

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.

How many tokens does P4 Dam Workflows use?

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.

What are the alternatives to P4 Dam Workflows?

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.

Who maintains P4 Dam 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.