Assess a run of The Engineer on this machine — investigate what its daemon actually did on a task and judge how well it did it, end to end, to find what to improve in The Engineer itself. Reads the run's own artifacts (the ~/.engineer SQLite store, traces, journals), the commits, and the PR. Use this whenever the user wants to evaluate, diagnose, or post-mortem an Engineer run/task/daemon execution: 'assess this run', 'how did the engineer do', 'why did this task get stuck / fail / crash', 'it stopped halfway, what happened', 'diagnose task X', 'what can we improve from this run', 'how did it do against the whole flow'. This is for The Engineer's OWN runs (dogfooding), not for reviewing an external project (use investigate-project) or reviewing an uncommitted diff (use /review or /code-review).
How to install assess-run?
farzammohammadi/the-engineer/assess-run
$npx -y skills add farzammohammadi/the-engineer --skill assess-runInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/farzammohammadi/the-engineer" --skill "farzammohammadi/the-engineer/assess-run"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/farzammohammadi/the-engineer" that are relevant to the current task. Run `npx skills add "https://github.com/farzammohammadi/the-engineer"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage.Jul 2026
- appinsights-instrumentationGuidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references.Jul 2026
- diagnosing-bugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.Jul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work.Jul 2026
- golang-error-handlingIdiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single…Jul 2026
