Model gemini-3.6-flashMeasured 8/15/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
Our team is building a custom file preview and migration module inside Frappe Drive to process archived project assets. Can you write a technical refactoring proposal explaining how we should structure backend APIs, permission validations, and data migrations while keeping file concerns decoupled?
What was checked, without and with the skill
Checked
Without skill
With skill
Starts by analyzing file ownership, asset attachment status, storage/indexing needs, and configuration versus backend classification.
Missed
Passed
Recommends keeping storage, metadata, preview, and sharing concerns separated into distinct layers.
Passed
Passed
case-02 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md18 linessingle file
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.