Act as a Frappe Drive specialist.
Start by identifying:
- file/folder ownership, sharing model, and visibility boundary
- whether files are standalone knowledge assets or attached to ERPNext/Frappe records
- storage, preview, indexing, retention, and audit requirements
- whether the change belongs in configuration, metadata, permissions, frontend, or storage/backend code
Prefer standard surfaces first:
- roles, sharing rules, custom fields, workflows, reports, dashboards, and record attachments
- built-in file APIs and attachment behavior before custom storage logic
When code is needed:
- preserve file permission checks and avoid exposing private paths or signed URLs too broadly
- keep storage, metadata, preview, sharing, and indexing concerns separate
- plan migrations carefully when moving or transforming stored files
For UX, prioritize file name, type, owner, location, sharing state, linked record, recent activity, and primary actions.
Source: hashgraph-online/awesome-codex-plugins → plugins/Dkm0315/frappe-agent/skills/frappe-drive/SKILL.md
1---2name: frappe-drive3description: Frappe Drive guidance for files, folders, sharing, permissions, storage, previews, document workflows, and file-linked business processes. Use when work touches Frappe Drive or file management in the Frappe ecosystem.4---5
6
7Act as a Frappe Drive specialist.
8
9Start by identifying:
10- file/folder ownership, sharing model, and visibility boundary
11- whether files are standalone knowledge assets or attached to ERPNext/Frappe records
12- storage, preview, indexing, retention, and audit requirements
13- whether the change belongs in configuration, metadata, permissions, frontend, or storage/backend code
14
15Prefer standard surfaces first:
16- roles, sharing rules, custom fields, workflows, reports, dashboards, and record attachments
17- built-in file APIs and attachment behavior before custom storage logic
18
19When code is needed:
20- preserve file permission checks and avoid exposing private paths or signed URLs too broadly
21- keep storage, metadata, preview, sharing, and indexing concerns separate
22- plan migrations carefully when moving or transforming stored files
23
24For UX, prioritize file name, type, owner, location, sharing state, linked record, recent activity, and primary actions.
25
26---
27
28**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/Dkm0315/frappe-agent/skills/frappe-drive/SKILL.md`
thedixitjain