Agent skill
copy-skill
Copy a skill from Product Forge to user or project level
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/copy-skill
SKILL.md
Copy Skill
Copy a skill from Product Forge plugins to your user-level (~/.claude/) or project-level (.claude/) directory.
Usage
# List available skills
/copy-skill
# Copy to project (default)
/copy-skill product-design:python-style
# Copy to user level
/copy-skill product-design:python-style --user
# Explicit project level
/copy-skill git-workflow:commit-patterns --project
Arguments
<plugin>:<skill-name>- The skill to copy inplugin:nameformat--user- Copy to~/.claude/{plugin}/skills/{name}/--project- Copy to.claude/{plugin}/skills/{name}/(default)
What Gets Copied
Skills are copied as entire directories, including:
SKILL.md- The main skill definition- Any additional files (scripts/, references/, *.yaml, etc.)
Example: parallel-agents skill contains both SKILL.md and agent-skills-mapping.yaml.
Directory Structure
# Project-level (default)
.claude/
└── product-design/
└── skills/
└── python-style/
└── SKILL.md
# User-level (--user)
~/.claude/
└── product-design/
└── skills/
└── python-style/
└── SKILL.md
Execution Instructions
When the user runs this command:
No Arguments - List Available Skills
-
Scan Product Forge plugins cache for all available skills:
bashls ~/.claude/plugins/cache/product-forge-marketplace/*/skills/ 2>/dev/null -
For each plugin with skills, list them with descriptions:
- Read
SKILL.mdfrontmatter to getnameanddescription - Format as:
{plugin}:{skill-name} - {description}
- Read
-
Display formatted list:
Available skills from Product Forge: product-design: python-style - Python coding style and PEP standards prd-management - Automatic PRD lifecycle management parallel-agents - Multi-agent orchestration patterns ... git-workflow: commit-patterns - Git commit best practices ... Usage: /copy-skill <plugin>:<skill-name> [--user | --project]
With Arguments - Copy Skill
-
Parse arguments:
- Extract
pluginandskill-namefrom<plugin>:<skill-name>format - Determine destination:
--useror--project(default)
- Extract
-
Locate source skill:
bashSOURCE=~/.claude/plugins/cache/product-forge-marketplace/{plugin}/skills/{skill-name}- If not found, show error with available skills from that plugin
-
Determine destination path:
--project:.claude/{plugin}/skills/{skill-name}/--user:~/.claude/{plugin}/skills/{skill-name}/
-
Check if destination exists:
- If exists, use AskUserQuestion to prompt:
Skill '{skill-name}' already exists at {destination}. Options: - Overwrite: Replace existing skill - Rename: Save as {skill-name}-copy - Cancel: Abort operation
- If exists, use AskUserQuestion to prompt:
-
Create destination directory structure:
bashmkdir -p {destination} -
Copy entire skill directory recursively:
bashcp -r {source}/* {destination}/ -
Confirm success:
Skill copied successfully! Source: ~/.claude/plugins/cache/product-forge-marketplace/{plugin}/skills/{skill-name}/ Destination: {destination} Files copied: - SKILL.md - [any additional files] The skill is now available in your {project|user} configuration.
Error Handling
- Plugin not found: Show list of available plugins
- Skill not found: Show list of skills in that plugin
- Invalid format: Show usage example with correct format
- Copy failed: Show error and suggest checking permissions
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?