frappe-drive
SkillFiles & storageFrappe 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the frappe-drive skill
What this skill tells your AI
The instructions your AI receives, as published by dkm0315/frappe-agent in skills/frappe-drive/SKILL.md and read by ahel’s review.
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.
Signals
- GitHub stars
- 24
- Forks
- 4
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
frappe-drive- Source
- github.com/dkm0315/frappe-agent