Persistent cache implementation for httpx and httpcore following RFC 9111 specification
74
Pending
Does it follow best practices?
Impact
74%
1.48xAverage score across 10 eval scenarios
Pending
The risk profile of this skill
{
"context": "This criteria evaluates how well the engineer uses hishel's storage backend APIs to implement soft deletion with grace periods and batch cleanup. The focus is on proper use of storage operations, timestamp-based deletion marking, and efficient batch processing.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Storage Backend Usage",
"description": "Uses hishel storage backend (AsyncSQLiteStorage or SyncSQLiteStorage) for persistent cache storage with appropriate initialization",
"max_score": 15
},
{
"name": "Soft Deletion Implementation",
"description": "Uses storage.remove_entry() to soft-delete cache entries, which marks them with a deleted_at timestamp rather than immediately removing them",
"max_score": 25
},
{
"name": "Grace Period Logic",
"description": "Implements logic to check deleted_at timestamps and only permanently delete entries after the grace period (default 1 hour) has elapsed",
"max_score": 20
},
{
"name": "Batch Processing",
"description": "Implements batch cleanup that processes entries in configurable batches (e.g., 200 at a time) rather than loading all entries into memory at once",
"max_score": 20
},
{
"name": "TTL Handling",
"description": "Properly handles TTL-based expiration alongside soft deletion, removing entries that have exceeded their TTL during cleanup",
"max_score": 10
},
{
"name": "Cleanup Verification",
"description": "Uses storage.get_entries() to verify that soft-deleted entries exist during grace period and are removed after, demonstrating understanding of entry lifecycle",
"max_score": 10
}
]
}docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10