soia-pkm-clip-drive

soia-pkm-clip-drive

clip family'sCloud drive member: import existing materials (PDF, DOCX, etc.) from network drives/local into the vault. Unlike web scraping, it handleslocal/cloud drive files。

Client-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 off to organize for sorting

Client wants	Skill will do	Client can see
Complete the work covered by this skill	Read the user request, necessary context, and this skill's main workflow, and execute the minimal reliable steps	The client will see Obsidian/vault file changes, terminal logs, generated artifact paths, and a final receipt.
Missing dependencies, permissions, configuration, or key	Stop actions that require external state, and clearly state what is missing	Install commands, application addresses, configuration paths, or questions requiring client 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 client uses it

1. State the goal in natural language and provide the necessary inputs: files, URLs, repos, workspaces, proposals, vaults, or platform account status.
2. The Agent first determines whether this skill is triggered, then checks dependencies, configuration, permissions, and risky actions.
3. For actions that can be dry-run or previewed, provide a preview first; when deletion, overwriting, sending, publishing, or writing remote state is involved, seek client confirmation first.
4. After execution, verify the real output; do not substitute "looks successful" for evidence.
5. The final reply must give the client a visible summary: what was done, log summary, file changes, issues, and next steps.

Dependencies and installation

Install this skill (single skill):

npx skills add soia-team/soia-open-skills -g -a '*' -s soia-pkm-clip-drive -y

Configuration conventions:

~/.config/soia-skills/soia-open-skills/soia-pkm/soia-pkm-clip-drive/config.yml
SOIA_PKM_CLIP_DRIVE_CONFIG_FILE=<custom-config-path>

• If this skill does not need private configuration, you may skip creating config.yml。
• If an API key, cookie, session, provider home, or local path is needed, it can only go into a 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.
• Strong dependencies, optional dependencies, and third-party skill relationships must be based on this SKILL.md subsequent "dependencies / prerequisites / resources / boundaries" description; if it is not clearly written, first supplement the description or ask the client, 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 client see the process and results. Minimum receipt format:

完成：<一句话说明本次完成了什么>。

日志摘要：
- started: <检查到的输入/配置/依赖，不打印秘密值>
- processed: <数量或范围>
- created/updated: <数量或路径>
- skipped/failed: <数量和原因>

文件变化：
- <绝对路径或“未改动文件”>

验证：
- <运行过的检查、命令或人工核对点>

问题与下一步：
- <缺 key / 缺依赖 / 需要客户确认 / 建议下一条命令；没有则写“无”>

Processing

• 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

• Materials / reference 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 materials are usually large in volume and messy; rely on organize to categorize / build MOCs / deduplicate.

closed-loop position

★clip-drive(收) → organize（云盘资料尤其依赖整理） → distill → …。

---

receipt after completion

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 of the original document), explicitly mark it as "unverified" in the receipt; do not fabricate.

after executionmustoutput to the user (do not silently finish):

1. what was done — a one-sentence summary of the completed work.
2. file changes — list newly created / modified / moved files (full paths); if no files were changed, state "no files changed".
3. next steps — optional follow-up suggestions (such as the next skill to connect to).