cloning-project/SKILL.md
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.
npx skillsauth add oaustegard/claude-skills cloning-projectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When users request to clone, copy, export, or backup their current project:
Check if the user is in a project by looking for project-specific indicators:
<available_skills> or similar sectionsIf not in a project, inform the user that this skill requires being inside a Claude project.
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:
cat > /home/claude/project-instructions.md << 'INSTRUCTIONS'
[Extracted project instructions content]
INSTRUCTIONS
Knowledge files are user-uploaded documents stored in /mnt/user-data/uploads/. List all files:
ls -lh /mnt/user-data/uploads/
If knowledge files exist, copy them to the working directory for bundling:
cp /mnt/user-data/uploads/* /home/claude/project-export/
If only project instructions exist (no knowledge files):
cp /home/claude/project-instructions.md /mnt/user-data/outputs/
If project has both instructions and knowledge files:
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
cd /home/claude
zip -r /mnt/user-data/outputs/project-export.zip project-export/
unzip -l /mnt/user-data/outputs/project-export.zip
Link the exported files:
For single instructions file:
[Download project-instructions.md](computer:///mnt/user-data/outputs/project-instructions.md)
For bundled export:
[Download project-export.zip](computer:///mnt/user-data/outputs/project-export.zip)
Then provide clear setup instructions:
## 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.
Empty project (no custom instructions or knowledge):
Large knowledge bases:
Corrupted or inaccessible files:
Trigger phrases:
development
--- name: verifying-claims description: Check that a document's claims about code are actually true by reading the prose, the code, and the tests and reporting (or fixing) where they disagree. Use whenever the user wants to verify a README, guide, spec, or docstring still matches the code; whenever they mention documentation drift, doc-code sync, "is this still accurate", stale docs, or keeping docs/tests/code consistent; before publishing or merging a docs change; or as a periodic doc-accuracy
tools
Query, filter, and transform Markdown structurally with mq — a jq-like CLI for Markdown. Use to extract headings/sections/code-blocks/links from .md files, build a table of contents, pull code blocks of a given language, slice or reshape LLM prompt/output Markdown, or batch-transform docs. Triggers on "extract sections from this markdown", "get all the code blocks", "jq for markdown", "mq", or any structural query over Markdown that grep/Read can't do cleanly.
development
Composes single-file HTML artifacts (PR review writeups, status reports, incident postmortems, slide decks, design systems, prototypes, flowcharts, module maps, feature explainers, kanban boards, prompt tuners) from a small JSON spec instead of hand-written HTML/CSS/JS. Use when the user asks to "compare options side-by-side", requests an HTML version of a report or review or deck, asks for a flowchart, status update, postmortem, design system reference, interactive prototype, custom editor — or explicitly says "HTML artifact", "single HTML file", "self-contained HTML". Skip for ad-hoc HTML snippets (forms, emails, embedded widgets) where there's no template fit.
development
DAG workflow runner that encodes control flow in code, not prose. Use when a procedure has 3+ steps with branching, retries, or validation that must be enforced — gates as `when=`, edge contracts as `validate=`, predicate loops as `retry_until=`. The runner owns the graph; the LLM provides leaves. Also covers parallel execution, checkpoint resume, detached side-effects.