메뉴
Compliance checklist template for studies. All items must be checked with evidence before marking a study complete.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/expectedparrot/vernon --skill study-checklist명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
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.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | study-checklist |
| description | Compliance checklist template for studies. All items must be checked with evidence before marking a study complete. |
Every study gets a checklist.md in its root directory. Create it when you start the study. Work through it as you go. You may NOT output [STUDY_COMPLETE] until every item is checked with evidence.
At study start, write this template to checklist.md:
# Study Checklist
## Setup
- [ ] Study structure created via `create_study_project.py`
- [ ] `git init` done, initial commit made
- [ ] README.md has PURPOSE, Author, Timestamp
## Data Integrity
- [ ] All survey data comes from actual EDSL runs (no mock/fake/synthetic data)
Evidence: <!-- e.g., data/results.json.gz, 312 rows, run at 2025-06-15T14:32Z -->
- [ ] Every number, table, and chart in the report traces to a file in `data/`
Evidence: <!-- list the source files -->
## Analysis
- [ ] All analysis scripts live in `analysis/` and run via `make`
Evidence: <!-- e.g., make PLOTS TABLES succeeds -->
- [ ] Plots written to `writeup/plots/`, tables to `writeup/tables/`
## Report
- [ ] `writeup/report.md` exists and is the single report file
- [ ] passes
[ ] reviewed — all issues resolved or documented
Create at study start. The checklist is one of the first files you write, right after scaffolding.
Update as you go. Check items off when they're done, filling in the evidence comment. Don't batch all checks at the end.
Evidence is mandatory. Each checked item must have a concrete reference — a filename, row count, timestamp, command output, or similar. Never check a box without evidence.
No mock data — ever. If a survey hasn't been run, run it. If it failed, fix it and re-run. If cost is a concern, reduce agent or scenario count. A report built on made-up data is worse than no report at all.
Completion gate. Before outputting [STUDY_COMPLETE], verify every box is checked. If any item is unchecked, finish it first.
Add study-specific items. If the study has unique requirements (e.g., subtree from a predecessor, specific computed objects), add checklist items for those.
A completed study must have all three:
writeup/report.mdOnly when all checklist items are checked AND all three deliverables exist, output [STUDY_COMPLETE].