aiskillstore/marketplace / skills/92bilal26/assessment-builder
assessment-builder
VerifiedCreates assessments with varied question types (MCQ, code-completion, debugging, projects) aligned to learning objectives with meaningful distractors based on common misconceptions. Activate when educators design quizzes, exams, or tests measuring understanding; need questions at appropriate cognitive levels (Bloom's taxonomy); want balanced cognitive distribution (60%+ non-recall); or require rubrics for open-ended questions. Generates MCQs with diagnostic distractors, code-writing prompts, debugging challenges, and project-based assessments targeting deep understanding.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.5 KB |
| reference/blooms-assessment-alignment.md | markdown | 6.6 KB |
| reference/distractor-design.md | markdown | 6.6 KB |
| reference/question-types.md | markdown | 7.0 KB |
| reference/rubric-guidelines.md | markdown | 7.4 KB |
| scripts/validate-assessment.pyexecutable | script | 7.4 KB |
| templates/assessment-template.yml | config | 1.8 KB |
| templates/rubric-template.yml | config | 4.0 KB |
templates/rubric-template.yml
View on GitHubassignment_title: ""
total_points: 100
passing_score: 60
criteria:
- name: "Correctness / Functionality"
weight: 40 # Percentage of total grade
description: "Does the code produce correct output?"
levels:
excellent:
points: 40
description: "Works correctly for all test cases including edge cases. Produces expected output for normal inputs, empty inputs, and boundary conditions."
good:
points: 30
description: "Works correctly for standard test cases. May have minor issues with 1-2 edge cases but core functionality is sound."
fair:
points: 20
description: "Works for simple cases but fails on several edge cases or complex inputs. Core logic is present but incomplete."
poor:
points: 10
description: "Significant errors prevent correct output. May not run or produces incorrect results for most inputs."
- name: "Code Quality / Readability"
weight: 25
description: "Is the code clear, well-structured, and maintainable?"
levels:
excellent:
points: 25
description: "Clear, descriptive variable and function names. Logical organization. Well-commented where helpful. Includes docstrings."
good:
points: 19
description: "Generally readable with mostly clear names. Minor structure issues. Has docstring but comments could be improved."
fair:
points: 13
description: "Some confusing names (x, y) or unclear structure. Missing docstring or insufficient comments."
poor:
points: 6
description: "Poor naming throughout. Confusing logic flow. No documentation. Very hard to understand."
- name: "Efficiency / Algorithm Choice"
weight: 20
description: "Does the solution use appropriate algorithms and data structures?"
levels:
excellent:
points: 20
description: "Optimal approach with appropriate time/space complexity. Uses best data structures for the problem."
good:
points: 15
description: "Reasonable approach with minor inefficiencies. Could be improved but acceptable for problem scale."
fair:
points: 10
description: "Inefficient approach (e.g., nested loops where hash table would work). Noticeably slow for larger inputs."
poor:
points: 5
description: "Very inefficient algorithm or inappropriate data structures. Would not scale."
- name: "Error Handling"
weight: 10
description: "Does the code handle edge cases and invalid inputs?"
levels:
excellent:
points: 10
description: "Handles all edge cases: empty inputs, None, invalid types, boundary conditions. Fails gracefully with clear messages."
good:
points: 7
description: "Handles most common edge cases (empty inputs, basic validation). May miss 1-2 edge cases."
fair:
points: 5
description: "Minimal error handling. Handles one or two obvious cases but crashes on others."
poor:
points: 2
description: "No error handling. Crashes or produces incorrect results on edge cases."
- name: "Python Style / Best Practices"
weight: 5
description: "Does the code follow Python conventions and best practices?"
levels:
excellent:
points: 5
description: "Follows PEP 8 conventions. Uses Pythonic idioms (list comprehensions, context managers, etc.). Appropriate use of built-ins."
good:
points: 4
description: "Generally follows Python conventions. Minor style issues or missed opportunities for Pythonic patterns."
fair:
points: 3
description: "Several style violations. Non-Pythonic code (e.g., range(len()) instead of enumerate)."
poor:
points: 1
description: "Ignores Python conventions. Code looks like it was translated from another language."
feedback_template: |
Criterion: Score (Level)
[Specific feedback with examples from student work]
[Suggestions for improvement]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |