Auto-generated tile from GitHub (10 skills)
92
94%
Does it follow best practices?
Impact
92%
1.16xAverage score across 44 eval scenarios
Advisory
Suggest reviewing before use
{
"context": "Tests whether the agent uses async-cache-dedupe for async caching with request deduplication, p-limit or p-map for controlled concurrency, a static factory function instead of an async constructor, named exports, env-schema or Zod for environment validation, and avoids NODE_ENV.",
"type": "weighted_checklist",
"checklist": [
{
"name": "async-cache-dedupe usage",
"description": "Uses the async-cache-dedupe package (not a plain Map, lru-cache, or node-cache) for caching the async upstream fetch",
"max_score": 15
},
{
"name": "Cache TTL configured",
"description": "The async-cache-dedupe cache is configured with a numeric ttl value (seconds)",
"max_score": 10
},
{
"name": "p-limit or p-map usage",
"description": "Uses p-limit or p-map to cap the number of concurrent upstream calls (not Promise.all without a limit)",
"max_score": 15
},
{
"name": "Factory function pattern",
"description": "The service class or object is created via a static async factory method or a standalone async factory function (not via `new` with async logic in the constructor)",
"max_score": 10
},
{
"name": "Named exports",
"description": "The module uses named exports (export function / export class / export const) rather than a default export for the primary service",
"max_score": 10
},
{
"name": "Env-schema or Zod validation",
"description": "Environment variables are validated using env-schema (with TypeBox) or Zod before use, rather than reading process.env directly without validation",
"max_score": 10
},
{
"name": "No NODE_ENV branching",
"description": "Does NOT use process.env.NODE_ENV to conditionally change behavior; uses dedicated named environment variables (e.g. LOG_LEVEL, CACHE_TTL) for each concern",
"max_score": 10
},
{
"name": "No swallowed errors",
"description": "No catch block that silently ignores errors (empty catch, catch with only a comment, or catch that reassigns to undefined/null without logging or rethrowing)",
"max_score": 10
},
{
"name": "Error cause chain",
"description": "When wrapping a lower-level error in a higher-level one, passes the original error via the { cause: originalError } option",
"max_score": 10
}
]
}evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
scenario-44
skills
documentation
fastify
init
linting-neostandard-eslint9
node
nodejs-core
rules
oauth
octocat
snipgrapher