{
  "context": "This criteria evaluates how well the engineer utilizes py-cord's audit log API to fetch and display guild administrative actions. It focuses on proper use of the Guild.audit_logs() method, AuditLogEntry attributes, and interaction response patterns.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Audit log retrieval",
      "description": "Uses `guild.audit_logs()` or `ctx.guild.audit_logs()` to fetch audit log entries with appropriate limit parameter (e.g., limit=5)",
      "max_score": 25
    },
    {
      "name": "Async iteration",
      "description": "Properly iterates over audit log entries using `async for` to handle the AsyncIterator returned by audit_logs()",
      "max_score": 20
    },
    {
      "name": "Action type access",
      "description": "Accesses the `action` attribute of AuditLogEntry to determine the type of administrative action performed",
      "max_score": 15
    },
    {
      "name": "User attribution",
      "description": "Accesses the `user` attribute of AuditLogEntry to identify who performed the action",
      "max_score": 15
    },
    {
      "name": "Timestamp extraction",
      "description": "Accesses the `created_at` attribute of AuditLogEntry to get the timestamp of when the action occurred",
      "max_score": 10
    },
    {
      "name": "Reason handling",
      "description": "Accesses the `reason` attribute of AuditLogEntry and handles cases where it may be None",
      "max_score": 10
    },
    {
      "name": "Interaction response",
      "description": "Uses appropriate ApplicationContext response method (respond() or send_response()) to send the formatted audit log information back to the user",
      "max_score": 5
    }
  ]
}