메뉴
Tactic: Grade an ML/CS paper's reproducibility configuration reporting as complete, partial, or none after checking that clinical appraisal tools do not apply. Use when the question is whether the work can be rerun.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/yogsoth-ai/de-anthropocentric-research-engine --skill reforms-grading명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Strategy: Dialectic engine retuned for truth-seeking, not survival. A defender steelmans a claim into its MOST falsifiable form, a critic attacks to refute it, a judge classifies the exchange into BROKEN/CORROBORATED/UNFALSIFIABLE — the judge does NOT pick a winner or score persuasiveness. Methods: Irving debate (repurposed), Toulmin argumentation, Mayo severe testing.
Campaign: Logical extreme and boundary testing via reductio ad absurdum and edge-case analysis. Core question: Does this artifact collapse under logical limits and boundary conditions? Methods: Lakatos 1976, Dutilh Novaes 2016, BVA, Flyvbjerg Critical Case, Popper.
Campaign for mapping argument structures — extract claims, link evidence, assess strength, synthesize positions. Produces argument graphs in the wiki vault.
| name | reforms-grading |
| description | Tactic: Grade an ML/CS paper's reproducibility configuration reporting as complete, partial, or none after checking that clinical appraisal tools do not apply. Use when the question is whether the work can be rerun. |
| version | 1.0.0 |
| category | paper-reading |
| type | tactic |
| execution | tactic |
| input | paper_ref (string — title, arXiv ID, DOI, URL, or local .md/.txt/.pdf path) |
| output | 01-study-design-tool-gate.json and 02-engineering-config-grading.json under context/papers/<dir>/reforms-grading/ |
| sops | ["paper-fetch","study-design-tool-gate","engineering-config-grading"] |
| dependencies | {"sops":["paper-fetch","study-design-tool-gate","engineering-config-grading"]} |
not_found.study-design-tool-gate and write its verdict to
01-study-design-tool-gate.json.engineering-config-grading or returns not_applicable, proceed.engineering-config-grading, using that tool name when the gate
returned not_applicable, and write 02-engineering-config-grading.json.Record proposal_sop: true. Each justification must state what complete
reporting would look like before grading the paper. Report the gate verdict,
complete/partial/none counts, every none item, the unverified-proposal
caveat, and both paths.