cloning-project
Exports project instructions and knowledge files from the current Claude project. Use when users want to clone, copy, backup, or export a project's configuration and files.
What this skill does
# Cloning Project When users request to clone, copy, export, or backup their current project: ## Step 1: Verify Project Context Check if the user is in a project by looking for project-specific indicators: - Project instructions in the context window - Knowledge files mentioned in `<available_skills>` or similar sections - User explicitly stating they're in a project If not in a project, inform the user that this skill requires being inside a Claude project. ## Step 2: Gather Project Instructions Project instructions are typically found in the context window as XML or markdown content describing the project's purpose and configuration. Extract and save these instructions to a file. Create the instructions file: ```bash cat > /home/claude/project-instructions.md << 'INSTRUCTIONS' [Extracted project instructions content] INSTRUCTIONS ``` ## Step 3: Locate Knowledge Files Knowledge files are user-uploaded documents stored in `/mnt/user-data/uploads/`. List all files: ```bash ls -lh /mnt/user-data/uploads/ ``` If knowledge files exist, copy them to the working directory for bundling: ```bash cp /mnt/user-data/uploads/* /home/claude/project-export/ ``` ## Step 4: Create Export Bundle **If only project instructions exist (no knowledge files):** - Copy instructions directly to outputs: ```bash cp /home/claude/project-instructions.md /mnt/user-data/outputs/ ``` **If project has both instructions and knowledge files:** - Create an organized export directory: ```bash mkdir -p /home/claude/project-export cp /home/claude/project-instructions.md /home/claude/project-export/ cp /mnt/user-data/uploads/* /home/claude/project-export/ 2>/dev/null || true ``` - Create zip bundle: ```bash cd /home/claude zip -r /mnt/user-data/outputs/project-export.zip project-export/ ``` - Show bundle contents: ```bash unzip -l /mnt/user-data/outputs/project-export.zip ``` ## Step 5: Provide Files and Instructions to User Link the exported files: **For single instructions file:** ```markdown [Download project-instructions.md](computer:///mnt/user-data/outputs/project-instructions.md) ``` **For bundled export:** ```markdown [Download project-export.zip](computer:///mnt/user-data/outputs/project-export.zip) ``` Then provide clear setup instructions: ```markdown ## How to Import Into a New Project 1. **Create a new Claude project** (or open an existing one where you want to clone this configuration) 2. **Add project instructions:** - Open the new project's settings - Navigate to the "Instructions" section - Copy and paste the content from `project-instructions.md` - Save the instructions 3. **Upload knowledge files** (if applicable): - In the new project, go to the "Knowledge" section - Upload all files from the export (except project-instructions.md) - Files will become available as project knowledge Your project is now cloned with the same configuration and knowledge base. ``` ## Edge Cases **Empty project (no custom instructions or knowledge):** - Inform the user that the project has no custom configuration to export - Explain that projects by default only have access to Claude's base capabilities **Large knowledge bases:** - If the zip file exceeds reasonable size (~50MB), warn the user and suggest selective export - Provide individual file links as fallback **Corrupted or inaccessible files:** - Skip files that cannot be read - Report which files were successfully exported vs. skipped - Provide export anyway with available content ## Usage Examples **Trigger phrases:** - "Clone this project" - "Export my project configuration" - "How do I copy this project setup?" - "Backup my project" - "Save this project's settings"
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.