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 initializes a snipgrapher config before rendering, uses named profiles, verifies output file existence after rendering, uses explicit output paths with extensions, uses --out-dir and --concurrency for batch rendering, and falls back to npx if snipgrapher is not in PATH. The scenario focuses on snipgrapher's workflow and configuration preferences.",
"type": "weighted_checklist",
"checklist": [
{
"name": "snipgrapher init first",
"description": "The script or instructions run `snipgrapher init` (or `npx --yes snipgrapher init`) before any render commands, establishing the config file before rendering.",
"max_score": 12
},
{
"name": "Named profile usage",
"description": "Render commands use a `--profile <name>` flag to reference a named profile (e.g., `--profile default` or `--profile social`), rather than only relying on inline style flags.",
"max_score": 10
},
{
"name": "Profile defined in config",
"description": "The `snipgrapher.config.json` (or equivalent config file) defines at least one named profile in a `profiles` object.",
"max_score": 10
},
{
"name": "Output verification step",
"description": "After at least one render command, the script includes `ls -lh <output-file>` (or equivalent) to verify the output file exists and has non-zero size.",
"max_score": 10
},
{
"name": "Explicit output path and extension",
"description": "All render commands include an explicit `-o <filename.ext>` flag with a file extension (e.g., `-o snippet.png`, `-o banner.svg`). No render commands rely on default output naming.",
"max_score": 8
},
{
"name": "Batch --out-dir flag",
"description": "The batch render command includes the `--out-dir <directory>` flag to specify the output directory.",
"max_score": 10
},
{
"name": "Batch --concurrency flag",
"description": "The batch render command includes a `--concurrency <N>` flag to control parallel rendering.",
"max_score": 8
},
{
"name": "npx fallback pattern",
"description": "The script uses `npx --yes snipgrapher` (not just `snipgrapher`) for at least one command, OR the script checks whether `snipgrapher` is in PATH and falls back to `npx --yes snipgrapher` when it is not.",
"max_score": 10
},
{
"name": "doctor validation step",
"description": "The script or instructions include `snipgrapher doctor` (or `npx --yes snipgrapher doctor`) as a validation step before rendering.",
"max_score": 8
},
{
"name": "Env var override documented",
"description": "The script, README, or config file documents or demonstrates using at least one snipgrapher environment variable (e.g., SNIPGRAPHER_THEME, SNIPGRAPHER_FORMAT, SNIPGRAPHER_PROFILE) for CI or environment-specific overrides.",
"max_score": 8
},
{
"name": "Shell script artifact",
"description": "The output includes a shell script that automates the rendering workflow, making it reproducible and inspectable by the grader.",
"max_score": 6
}
]
}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