Frappe LMS customization guidance for courses, batches, lessons, quizzes, assessments, enrollment, progress, certificates, portals, and learning workflows.
SkillScore82Maintained
Automatic
◆Tutoring & Education pack
Last verified 8/15/2026
What it changes
Passed 18 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill82%
Checks it passed that the model alone missed
Mandates preserving instructor permission and enrollment checks.
Classifies the proposed modification as a metadata or DocType change.
Mandates verifying enrollment and permission checks for learners and instructors.
and 6 more in the full report
6 fixed12 passed either way4 still failing0 broke
Pass-rate lift
+27 pp
Tokens
-4%
Agent turns
0%
Response time
-10%
Model gemini-3.6-flashMeasured 8/15/2026v118 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 institution needs a custom backend hook in Frappe LMS to process quiz results, track completion metrics across multiple batches, and generate certificates automatically. Can you provide a technical development strategy covering data model boundaries, permission checks, and recommended customization surfaces?
What was checked, without and with the skill
Checked
Without skill
With skill
Starts by identifying standard roles, lifecycles, requirements, and change classification.
Missed
Passed
Keeps progress, grading, and certificate issuance concerns separated in backend logic.
Passed
Passed
Mandates verifying enrollment and permission checks for learners and instructors.
Missed
Passed
case-03 · 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 LMS specialist.
Start by identifying:
learner, instructor, evaluator, and administrator roles
course, batch, lesson, quiz, assignment, assessment, and certificate lifecycle
enrollment, progress tracking, grading, completion, and notification requirements
whether the change is configuration, metadata, portal UX, reports, or code
Prefer standard LMS surfaces first:
course/batch configuration, custom fields, workflows, web forms, notifications, reports, dashboards, and certificate templates
portal and website customization before building a separate app
When code is required:
preserve enrollment and permission checks for learners and instructors
keep progress, grading, certificate issuance, and content publishing concerns separate
avoid storing assessment answers or private learner data in weakly protected custom fields
Design learning UX around next action: continue learning, pending assessment, instructor feedback, progress, deadline, and certificate state should be obvious.