Copy a skill from Product Forge to user or project level
67
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Copy a skill from Product Forge plugins to your user-level (~/.claude/) or project-level (.claude/) directory.
# 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<plugin>:<skill-name> - The skill to copy in plugin:name format--user - Copy to ~/.claude/{plugin}/skills/{name}/--project - Copy to .claude/{plugin}/skills/{name}/ (default)Skills are copied as entire directories, including:
SKILL.md - The main skill definitionExample: parallel-agents skill contains both SKILL.md and agent-skills-mapping.yaml.
# Project-level (default)
.claude/
└── product-design/
└── skills/
└── python-style/
└── SKILL.md
# User-level (--user)
~/.claude/
└── product-design/
└── skills/
└── python-style/
└── SKILL.mdWhen the user runs this command:
Scan Product Forge plugins cache for all available skills:
ls ~/.claude/plugins/cache/product-forge-marketplace/*/skills/ 2>/dev/nullFor each plugin with skills, list them with descriptions:
SKILL.md frontmatter to get name and description{plugin}:{skill-name} - {description}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]Parse arguments:
plugin and skill-name from <plugin>:<skill-name> format--user or --project (default)Locate source skill:
SOURCE=~/.claude/plugins/cache/product-forge-marketplace/{plugin}/skills/{skill-name}Determine destination path:
--project: .claude/{plugin}/skills/{skill-name}/--user: ~/.claude/{plugin}/skills/{skill-name}/Check if destination exists:
Skill '{skill-name}' already exists at {destination}.
Options:
- Overwrite: Replace existing skill
- Rename: Save as {skill-name}-copy
- Cancel: Abort operationCreate destination directory structure:
mkdir -p {destination}Copy entire skill directory recursively:
cp -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.0ebe7ae
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.