copy-skill
Copy a skill from Product Forge to user or project level
What this skill does
# Copy Skill
Copy a skill from Product Forge plugins to your user-level (`~/.claude/`) or project-level (`.claude/`) directory.
## Usage
```bash
# 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 in `plugin:name` format
- `--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
1. **Scan Product Forge plugins cache** for all available skills:
```bash
ls ~/.claude/plugins/cache/product-forge-marketplace/*/skills/ 2>/dev/null
```
2. **For each plugin with skills**, list them with descriptions:
- Read `SKILL.md` frontmatter to get `name` and `description`
- Format as: `{plugin}:{skill-name} - {description}`
3. **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
1. **Parse arguments**:
- Extract `plugin` and `skill-name` from `<plugin>:<skill-name>` format
- Determine destination: `--user` or `--project` (default)
2. **Locate source skill**:
```bash
SOURCE=~/.claude/plugins/cache/product-forge-marketplace/{plugin}/skills/{skill-name}
```
- If not found, show error with available skills from that plugin
3. **Determine destination path**:
- `--project`: `.claude/{plugin}/skills/{skill-name}/`
- `--user`: `~/.claude/{plugin}/skills/{skill-name}/`
4. **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
```
5. **Create destination directory structure**:
```bash
mkdir -p {destination}
```
6. **Copy entire skill directory recursively**:
```bash
cp -r {source}/* {destination}/
```
7. **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
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.