clip family'sCloud drive member: import existing materials from cloud drives/local storage (PDF, DOCX, etc.) into the vault. Unlike web scraping, it handleslocal/cloud drive files。
Customer-readable description
What this skill can do
Batch-import existing cloud drive/local materials (PDF/Word/documents) into an Obsidian vault. Extract text, generate material notes, file them under the resource library or article excerpts, then hand them to organize for sorting
| The customer wants | The skill will do | The customer can see |
|---|---|---|
| Complete the work covered by this skill | Read the user request, necessary context, and this skill's main workflow, then execute the minimal reliable steps | The customer will see Obsidian/vault file changes, terminal logs, generated artifact paths, and the final receipt. |
| Missing dependencies, permissions, configuration, or keys | Stop actions that require external state and clearly state what is missing | Install commands, application addresses, configuration paths, or questions that need customer confirmation |
| Execution complete | Summarize successes, skips, failures, file changes, and verification results | A completion receipt that can be copied into a ticket/log |
How the customer uses it
- State the goal in natural language and provide the necessary inputs: files, URLs, repos, workspaces, proposals, vaults, or platform account status.
- The agent first determines whether this skill applies, then checks dependencies, configuration, permissions, and risky actions.
- For actions that can be dry-run or previewed, provide a preview first; for actions involving deletion, overwriting, sending, publishing, or writing remote state, seek customer confirmation first.
- After execution, verify the real output; do not substitute "looks successful" for evidence.
- The final reply must give the customer a visible summary: what was done, a log summary, file changes, issues, and next steps.
Dependencies and installation
Install this skill (single skill):
npx skills add soia-team/soia-open-pkm-clip-skills -g -a '*' -s soia-pkm-clip-drive -y
Configuration conventions:
~/.config/soia-skills/soia-pkm-clip-drive/config.yml
SOIA_PKM_CLIP_DRIVE_CONFIG_FILE=<custom-config-path>
- If this skill does not require private configuration, you may skip creating
config.yml。 - If an API key, cookie, session, provider home, or local path is required, it may only go into private
config.yml, the process environment, or the provider's own login state; it must not be written into the repository, vault body, or logs. - Hard dependencies, optional dependencies, and third-party skill relationships must be based on the "dependencies / prerequisites / resources / boundaries" description that follows this
SKILL.md; if it is not clearly written, add the description first or ask the customer, and do not guess. - Third-party skills may only declare dependencies and installation methods; do not directly modify third-party skill files.
Logs and completion receipt
Every execution must let the customer see the process and results. Minimum receipt format:
完成：<一句话说明本次完成了什么>。
日志摘要：
- started: <检查到的输入/配置/依赖，不打印秘密值>
- processed: <数量或范围>
- created/updated: <数量或路径>
- skipped/failed: <数量和原因>
文件变化：
- <绝对路径或“未改动文件”>
验证：
- <运行过的检查、命令或人工核对点>
问题与下一步：
- <缺 key / 缺依赖 / 需要客户确认 / 建议下一条命令；没有则写“无”>
Process
- Input: file path / directory (PDF, DOCX, TXT, Markdown)
- Extract:
pypdf/pdfplumber（PDF）、python-docx(Word) extract text; keep the original file until_附件/。 - Large batches: directory batch processing, each file → one note.
- Extraction and landing are currently performed manually by the agent according to the process in this section (a dedicated batch import script is to be added to this skill's
scripts/）。
Landing
- Reference / resource type →
<vault-resources-dir>/<主题>/; article type →<vault-articles-dir>/(determined by configuration or CLI parameters). - frontmatter：
tags:[资料]or[文章摘抄]、source: 云盘/pdf、original_path、captured_at、topics:[]。 - After importmust run
organize: cloud drive resources are usually large in volume and messy, so rely on organize to classify / build MOCs / deduplicate.
Closed-loop position
★clip-drive(收) → organize（云盘资料尤其依赖整理） → distill → …。
Completion receipt
Delivery order: first write the files to disk, then output the receipt below; do not reverse the order; for uncertain metadata (such as missing source information for the original document), explicitly mark it as "unverified" in the receipt; do not fabricate.
After executionmustoutput to the user (do not do it silently):
- What was done — summarize the completed work in one sentence.
- File changes — list newly created / modified / moved files (full paths); if no files were changed, state "no files changed".
- Next steps — optional follow-up suggestions (such as the next skill to connect to).