Other

schedule-management

Local schedule management for adding events, tracking deadlines, generating reminders, and detecting time conflicts when users need offline scheduling with optional popup notifications.

87100Total Score
Core Capability
88 / 100
Functional Suitability
11 / 12
Reliability
10 / 12
Performance & Context
8 / 8
Agent Usability
14 / 16
Human Usability
8 / 8
Security
10 / 12
Maintainability
10 / 12
Agent-Specific
17 / 20
Medical Task
15 / 20 Passed
86You need lightweight, offline/local-only schedule management without any cloud sync
3/4
86You want to add meetings/events and store them in a simple local data directory
3/4
86Add and store events locally in events.jsonl
3/4
86List and filter events by time range
3/4
86End-to-end case for Add and store events locally in events.jsonl
3/4

Veto GatesRequired pass for any deployment consideration

Skill Veto✓ All 4 gates passed
✓
Operational Stability
System remains stable across varied inputs and edge cases
PASS
✓
Structural Consistency
Output structure conforms to expected skill contract format
PASS
✓
Result Determinism
Equivalent inputs produce semantically equivalent outputs
PASS
✓
System Security
No prompt injection, data leakage, or unsafe tool use detected
PASS

Core Capability88 / 100 — 8 Categories

Functional Suitability
The archived deduction in functional suitability traces back to: Improve stress-case output rigor. Stress and boundary scenarios show weaker consistency
11 / 12
92%
Reliability
Related legacy finding for schedule-management: Improve stress-case output rigor. Stress and boundary scenarios show weaker consistency
10 / 12
83%
Performance & Context
Performance context reached full score in the archived evaluation.
8 / 8
100%
Agent Usability
The legacy audit deducted points for schedule-management in agent usability.
14 / 16
88%
Human Usability
The legacy audit gave full marks to human usability for this package.
8 / 8
100%
Security
The archived evaluation left some headroom for schedule-management under security.
10 / 12
83%
Maintainability
A modest deduction remained in maintainability for schedule-management in the archived review.
10 / 12
83%
Agent-Specific
Agent specific was softened by the legacy issue 'Stabilize executable path and fallback behavior'. Some inputs only reached PARTIAL due to execution gaps or weak boundary handling
17 / 20
85%
Core Capability Total88 / 100

Medical TaskExecution Average: 86 / 100 — Assertions: 15/20 Passed

86
Canonical
You need lightweight, offline/local-only schedule management without any cloud sync
3/4 ✓
86
Variant A
You want to add meetings/events and store them in a simple local data directory
3/4 ✓
86
Edge
Add and store events locally in events.jsonl
3/4 ✓
86
Variant B
List and filter events by time range
3/4 ✓
86
Stress
End-to-end case for Add and store events locally in events.jsonl
3/4 ✓
86
Canonical✅ Pass
You need lightweight, offline/local-only schedule management without any cloud sync

The main issue in this canonical run was: The script execution path completed successfully for the documented case.

Basic 33/40|Specialized 53/60|Total 86/100
✅A1The schedule-management output structure matches the documented deliverable
❌A2The script execution path completed successfully for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 3 / 4
86
Variant A✅ Pass
You want to add meetings/events and store them in a simple local data directory

This variant a case was mostly intact, but the archived review centered its concern on: The script execution path completed successfully for the documented case.

Basic 31/40|Specialized 55/60|Total 86/100
✅A1The schedule-management output structure matches the documented deliverable
❌A2The script execution path completed successfully for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 3 / 4
86
Edge✅ Pass
Add and store events locally in events.jsonl

The preserved weakness for Add and store events locally in events.jsonl was concentrated in one point: The script execution path completed successfully for the documented case.

Basic 30/40|Specialized 56/60|Total 86/100
✅A1The schedule-management output structure matches the documented deliverable
❌A2The script execution path completed successfully for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 3 / 4
86
Variant B✅ Pass
List and filter events by time range

The main issue in this variant b run was: The script execution path completed successfully for the documented case.

Basic 29/40|Specialized 57/60|Total 86/100
✅A1The schedule-management output structure matches the documented deliverable
❌A2The script execution path completed successfully for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 3 / 4
86
Stress✅ Pass
End-to-end case for Add and store events locally in events.jsonl

This stress case was mostly intact, but the archived review centered its concern on: The script execution path completed successfully for the documented case.

Basic 26/40|Specialized 60/60|Total 86/100
✅A1The schedule-management output structure matches the documented deliverable
❌A2The script execution path completed successfully for the documented case
✅A3The output stays fully within the documented skill boundary
✅A4The response quality is acceptable for the documented path
Pass rate: 3 / 4
Medical Task Total86 / 100

Key Strengths

  • Primary routing is Other with execution mode B
  • Static quality score is 88/100 and dynamic average is 71.6/100
  • Assertions and command execution outcomes are recorded per input for human review
  • Execution verification summary: Script verification 1/1; adjustment=5. schedule_tool.py: OK