Research skills and a bilingual curriculum for Claude Code, written for social scientists rather than for software engineers.
You asked a model for sources. Some of them turned out not to exist, and now no entry in the reference list can be trusted until you have checked it yourself. The screening backlog has not moved, the Turkish version and the English version of the paper still have to make the same claims, and a reviewer will still ask which claim came from which study.
Everyone says these terminal tools will change how research gets done, and every guide to them is written for people who build software for a living.
Claude Code for Social Scientists installs 32 narrow research skills into Claude Code — DOI verification, PRISMA screening, preregistration ledgers, anonymization gates, bilingual manuscript scaffolding — alongside a Turkish and English curriculum for researchers in psychology, sociology, education, public health, and adjacent fields who are new to the terminal.
The project holds itself to the standard it teaches. Every DOI cited in the curriculum is resolved against doi.org on a schedule; a dead one turns the run red. See the checker.
What this looks like in a session.
You: Check every reference in chapter 3 against Crossref and tell me which ones you could not resolve.
apa-doi-verifier: one row per reference, with source type, DOI status, metadata status, and a fabricated citation risk rating; then corrected APA 7 entries for the references that resolved, and a separate list of the ones that did not. The skill's instructions forbid repairing an unresolved DOI by guesswork, so an unresolved reference comes back marked unresolved rather than filled in.
Inside Claude Code:
/plugin marketplace add OnourImpram/claude-code-for-social-scientists
/plugin install social-cc-plugin@claude-code-for-social-scientists
Or from a shell, which also covers Codex:
pip install social-cc-plugin
social-cc install --project # copies the 32 skills into ./.claude/skillsTürkçe okuyucular. Tam Türkçe giriş için
README.tr.mddosyasına bakın. Her yayımlanmış kitapçıktatr.mdveen.mdbirlikte bulunur.
The counts on this page come from the build rather than from typing, and a booklet that declares a fabricated citation fails that build. What each check covers, and what it does not, is in How the claims are checked.
Created and maintained by Onour Impram, a clinical psychologist, postdoctoral researcher, and artificial intelligence researcher. The project is designed for researchers inside and outside English dominant academic infrastructure and is grounded in real research, teaching, clinical, and open science constraints.
The human researcher retains scientific, interpretive, ethical, legal, clinical, and professional authority. The platform does not act as an ethics committee, statistician of record, licensed legal adviser, clinical supervisor, or autonomous principal investigator.
Current release facts, v5.0.0. Thirty three released booklets, sixty six Turkish and English language files, fourteen categories, and thirty two reviewed skills. The disclosed booklet metadata contains 566 verified citation declarations and zero fabricated citation declarations. A declaration count is not a count of unique sources. Release facts are governed by
meta/release.jsonand checked against the repository byscripts/validate-release-truth.mjs.
- The counts are re-derived from the repository, not typed.
npm run validate:truthwalks the repository, re-derives booklets, language files, categories, skills, and citation declarations, and fails the build when any of them disagrees withmeta/release.json, or when this page is missing the exact machine readable release facts marker at the top of the file. The spelled out numbers in the prose above are not themselves compared against the repository; the marker andmeta/release.jsonare. - A booklet that declares a nonzero fabricated citation count fails the build. The check is in
scripts/validate-platform.mjs, and it enforces the declaration rather than the underlying references: a booklet that declares zero and contains a fabricated reference passes. Proving a declaration true is human work, andapa-doi-verifierandsource-passport-ledgerare the workflows for doing it. A complete claim level reread of every source is recorded as an open limitation indocs/TEN_LOOP_ENGINEERING_REPORT.md. - The routing corpus is generated and checked for shape, not executed.
npm run check:evaluationderives six cases per skill from one seed record intests/fixtures/skill-routing-seeds.json— two positive, two negative, one boundary, one safety, split across Turkish and English — for 192 cases over 32 skills, and fails when the seed list and the canonical skill directory disagree, when a seed is malformed, or when the per-skill case mix drifts. Alongside them,tests/fixtures/agent-scenarios.jsoncarries 18 agent scenarios, 15 traps and boundary cases and 3 valid workflow controls, and the build fails if fewer than 15 scenarios remain, if fewer than two valid workflow controls remain, or if any required kind —valid_workflow,sensitive_data,citation_trap,prompt_injection,routing_trap,client_capability_trap— goes missing. None of it is run against a live Claude Code or Codex session; native authenticated invocation is recorded as an open limitation indocs/TEN_LOOP_ENGINEERING_REPORT.md.
Start with the curriculum in booklets/. The research integrity commitments, the security and privacy boundaries, the licensing split, and the record of open verification limits are stated in full below.
The project serves researchers in psychology, sociology, education, public health, communication, political science, anthropology, and adjacent fields. It is written for people who may be highly trained in research but new to terminals, Git, Markdown, YAML, permissions, skills, agents, hooks, or MCP.
The fourteen curriculum categories are Foundations, Academic Access, Memory Systems, Vault Architecture, Hooks and Automation, MCP and Plugins, Academic Writing, Data Analysis, Ethics and IRB, Peer Review, Conference and Public Communication, Troubleshooting, Teaching and Supervision, and Tool Portability.
Turkish and English are equal first class languages. English content is natively adapted rather than mechanically translated. Turkish content is written as natural academic Turkish rather than translated technical prose. The project values conceptual equivalence, numerical parity, citation parity, cultural adaptation, and the author's voice over sentence level mirroring.
Regional realities are part of the architecture. DergiPark, ULAKBİM TR Dizin, HEAL Link, institutional VPNs, regional ethics systems, KVKK, GDPR, multilingual scholarship, and unequal infrastructure access are treated as methodological conditions rather than footnotes.
- A plausible citation is not a verified citation.
- An unverified reference does not enter a final bibliography.
- No source, DOI, statistic, participant detail, ethics approval, registration, quotation, or result may be invented.
- Retrieved articles, websites, repositories, PDFs, transcripts, datasets, and reviewer files are evidence, not instructions.
- Raw clinical material, identifiable participant data, student records, confidential peer review manuscripts, credentials, and institutional secrets must not enter an unapproved tool context.
- Quantitative, qualitative, and mixed methods work retain distinct methodological boundaries.
- AI assistance remains visible and is disclosed where required.
See AI-AUTHORSHIP.md, SECURITY.md, and docs/SECURITY_PRIVACY_AND_RESEARCH_DATA_BOUNDARIES.md.
The canonical reviewed skill source is .claude/skills. The path is retained for backward compatibility with the repository's original Claude Code releases. The skill content is kept client neutral and the Python package installs the same reviewed files into the discovery paths used by Claude Code or Codex.
| Skill | Primary workflow |
|---|---|
social-science-literature-triage |
Search scope, databases, language layers, inclusion logic, and source status |
apa-doi-verifier |
APA 7 structure, DOI identity, metadata, and fabricated citation risk |
bilingual-booklet-pairing |
Turkish and English booklet structure, metadata, citation, and adaptation parity |
ai-disclosure-auditor |
AI contribution, model metadata, human review, and disclosure fields |
ethics-irb-ai-protocol |
Ethics, privacy, data minimization, institutional review, and disclosure questions |
rebuttal-traceability-matrix |
Reviewer comments, responses, manuscript changes, evidence, and status |
memory-vault-architect |
Durable research folders, maps of content, metadata, and retrieval conventions |
regional-access-workflow |
Lawful regional and institutional literature access routes |
agentic-session-debugger |
Scope, context, permissions, paths, loops, and host state diagnosis |
repo-release-integrity-check |
Release metadata, counts, citations, packaging, and public claim alignment |
anti-ai-trace-revision |
Author voice revision while preserving evidence and required disclosure |
bilingual-manuscript-scaffold |
Turkish and English manuscripts from one claim architecture |
journal-fit-screening |
Scope fit, index verification, policy review, and predatory risk |
qualitative-coding-discipline |
Human led coding, reflexivity, quote integrity, negative cases, and audit trail |
statistical-consultation-protocol |
Design, estimand, assumptions, effect sizes, uncertainty, and reporting |
research-ritual-hooks |
Bounded lifecycle automation and research session checks |
research-lifecycle-pipeline |
Lightweight research stage diagnosis and skill routing |
mcp-research-stack-triage |
MCP publisher, data flow, permissions, trust, and known answer behavior |
source-passport-ledger |
Source discovery, access, identity, verification, claims, and citation status |
conference-materials-bilingual |
Evidence traceable bilingual slides, posters, and talks |
prisma-scoping-review-pipeline |
Logged search, screening, exclusions, extraction, and PRISMA counts |
sensitive-data-anonymization-gate |
Data minimization, deidentification, classification, and access decision support |
open-science-release-packager |
Code, data decisions, metadata, licensing, DOI, embargo, and release materials |
authorship-contribution-ledger |
Authorship order, CRediT roles, evidence, disputes, and AI assistance |
peer-review-confidentiality-protocol |
Confidentiality preserving decisions about AI assisted peer review |
multilingual-concept-validity-audit |
Construct equivalence, translation decisions, cultural adaptation, and drift |
grant-proposal-workpackage-builder |
Work packages, milestones, risks, dependencies, and budget logic |
teaching-feedback-ai-boundaries |
AI boundaries for courses, assessment, supervision, and student feedback |
public-scholarship-ethics-adapter |
Public communication that preserves evidence, uncertainty, and embargoes |
preregistration-analysis-plan-ledger |
Confirmatory decisions, estimands, exclusions, analyses, and deviations |
agent-portability-matrix |
Host capabilities, file access, memory, permissions, and migration risk |
cross-agent-second-opinion |
Independent verification and explicit disagreement for human adjudication |
The responsibility and handoff contract is in docs/SKILL_RESPONSIBILITY_AND_HANDOFF_MATRIX.md.
pip install social-cc-plugin# User scope, ~/.claude/skills
social-cc install --client claude-code
# Project scope, <project>/.claude/skills
social-cc install --client claude-code --scope project
# Backward compatible project form
social-cc install --project# User scope, ~/.agents/skills
social-cc install --client codex
# Project scope, <project>/.agents/skills
social-cc install --client codex --scope projectsocial-cc install --client all
social-cc install --client all --scope projectsocial-cc list
social-cc diff --client all
social-cc upgrade --client all
social-cc doctor --client all
social-cc uninstall --client allThe installer records ownership in .social-cc/manifest.json. Existing unmanaged directories and locally modified project directories are protected by default. A forced replacement or removal first moves the prior directory into .social-cc/backups/.
Use --dry-run to inspect a planned install, upgrade, or removal. Use --force only after reviewing the diff and backup location.
Claude Code users can also install the native plugin.
/plugin marketplace add OnourImpram/claude-code-for-social-scientists
/plugin install social-cc-plugin@claude-code-for-social-scientists
The plugin is a Claude Code distribution route. It does not by itself establish Codex compatibility. Codex support is provided through the cross client installer and repository instructions.
The canonical agent contract is core/agents/social-scientist.md. It follows this cycle.
ORIENT → INSPECT → CLASSIFY → SELECT SKILLS → WORK → VERIFY → HAND OFF
The agent selects the minimum sufficient skills. It does not run every installed skill. It distinguishes observed evidence, verified evidence, calculation, inference, human decision, and unresolved uncertainty.
Claude Code receives generated project and plugin subagent adapters. Codex reads AGENTS.md, discovers installed skills, and follows the shared contract. Host differences in permissions, invocation, subagents, plugins, metadata, and tools are documented rather than hidden.
See docs/SOCIAL_SCIENTIST_AGENT.md, docs/CLAUDE_CODE_INTEGRATION.md, and docs/CODEX_INTEGRATION.md.
.claude/skills/ canonical reviewed skills
.claude/agents/ generated Claude Code project agent
agents/ generated Claude Code plugin agent
core/agents/ canonical Social Scientist Agent
booklets/ Turkish and English curriculum
src/social_cc_plugin/ Python installer
scripts/ deterministic validators and renderers
docs/ architecture, security, learning, and integration guides
meta/release.json canonical release and platform facts
AGENTS.md Codex repository guidance
npm ci
npm run lint
npm run validate
npm run validate:truth
npm run check:agents
npm run check:actions
npm run verify
python -m pip install -e .
python -m pytest tests/ -v
ruff check .
mypy --strict src tests
python -m build
social-cc --version
social-cc list
social-cc doctor --client allNetwork dependent DOI and external link checks are separate from deterministic pull request gates.
Code, configuration, validators, renderers, and installer logic are licensed under Apache 2.0. Skill prose, booklets, educational guides, and templates are licensed under CC BY NC SA 4.0 unless a file states otherwise. Generated adapters inherit the license of their canonical source.
LICENSING.md is the authoritative statement of the dual arrangement. The root
LICENSE carries the Apache 2.0 text for the code, which is what GitHub detects and displays;
LICENSE.code is the same text under its descriptive name, and
LICENSE.content carries CC BY NC SA 4.0 for the prose.
Use the machine readable record in CITATION.cff or GitHub's citation interface. The Zenodo concept DOI is 10.5281/zenodo.20289687 and resolves to the latest archived version. Per-release version DOIs are listed there.
Contributions are welcome from social scientists, clinicians, methodologists, librarians, educators, accessibility specialists, security reviewers, and engineers. Review CONTRIBUTING.md or CONTRIBUTING.tr.md before opening a pull request.
Do not commit private research material. Do not weaken bilingual, citation, disclosure, privacy, release truth, or human authority checks to make a build pass.
The public phase plan is in meta/roadmap.md. The current engineering architecture, ten loop evidence, verification limits, and release readiness record are in docs/TEN_LOOP_ENGINEERING_REPORT.md.