원클릭으로
error-logging
Error logging protocol using append-only JSONL format (errors.jsonl).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Error logging protocol using append-only JSONL format (errors.jsonl).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Patterns for creating EDSL AgentLists from various sources: lists, CSV, Excel, DataFrame, and programmatic combinations.
Saving EDSL objects locally and publishing them to Coop (Expected Parrot's servers).
Templates for the standard EDSL study files: survey, scenarios, agents, models, and create_results.py.
Developer tool: find the most recent errors.jsonl from an agent run, diagnose root causes, and interactively patch the agent's instruction files to prevent recurrence.
Using FileStore to wrap files (images, PDFs, data) for use in EDSL survey scenarios.
Launching EDSL surveys for real human respondents via humanize, including scenario methods, Prolific integration, and retrieving responses.
| name | error-logging |
| description | Error logging protocol using append-only JSONL format (errors.jsonl). |
All errors, unexpected results, and surprises must be logged to errors.jsonl in the study root (never in a subdirectory like writeup/). The file is append-only JSONL — one JSON object per line.
Log before attempting any fix whenever you encounter:
The sequence is always: (1) log the error, (2) then fix it. Never fix first.
Append exactly one JSON object per error. Every line must be valid JSON.
{"timestamp": "2025-06-15T14:32:00Z", "summary": "Short description", "error": "exact error message or description", "context": "what you were doing", "command": "the exact command or code that failed — verbatim", "output": "the complete traceback or unexpected output — verbatim, never summarize", "fix_attempted": "what you tried", "outcome": "success or failure — update after fix"}
| Field | Description |
|---|---|
timestamp | ISO-8601 UTC timestamp |
summary | Brief one-line description |
error | The exact error message |
context | What you were trying to do |
command | The verbatim command or code that failed |
output | The complete raw traceback / stderr — never paraphrase or abbreviate |
fix_attempted | What you did to fix it |
outcome | "success" or "failure" — update after attempting the fix |
Use a single echo/printf to append one line:
echo '{"timestamp":"2025-06-15T14:32:00Z","summary":"ModuleNotFoundError for pandas","error":"ModuleNotFoundError: No module named '\''pandas'\''","context":"Running make data","command":"cd edsl_jobs && python create_results.py","output":"Traceback (most recent call last):\n File \"create_results.py\", line 2\n import pandas\nModuleNotFoundError: No module named '\''pandas'\''","fix_attempted":"pip install pandas","outcome":"success"}' >> errors.jsonl
Or use Python for complex output with special characters:
import json, datetime
entry = {
"timestamp": datetime.datetime.utcnow().isoformat() + "Z",
"summary": "Short description",
"error": "...",
"context": "...",
"command": "...",
"output": "...", # paste the full traceback here
"fix_attempted": "...",
"outcome": "pending"
}
with open("errors.jsonl", "a") as f:
f.write(json.dumps(entry) + "\n")
Before finishing a study, read errors.jsonl and confirm all encountered issues are captured. Check that every entry has a final outcome of "success" or document why it remains unresolved.