Individual skill
frappe-drive
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.
plugins/Dkm0315/frappe-agent/skills/frappe-drive/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,532
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,216 bytes
Read excerpt
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