zrwangems/dsh-zrwang-plugin / ars/skills/academic-pipeline
academic-pipeline
Flagged学术研究总编排:研究→写作→诚信检查→评审→返修→复审→终检→定稿的十阶段流水线,每阶段停在用户确认点,含材料护照与 7 类 AI 研究失败模式检查。Triggers: academic pipeline, research to paper, full paper workflow, end-to-end paper | 完整论文流程, 从研究到论文, 端到端写论文, 论文流水线。
_shared/contracts/passport/experiment_provenance_entry.schema.json
View on GitHub{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://github.com/Imbad0202/academic-research-skills/shared/contracts/passport/experiment_provenance_entry.schema.json",
"title": "Material Passport Experiment Provenance Entry",
"description": "One entry in Material Passport Schema 9 experiment_provenance[] aggregate (#260). Scholar-entered at intake (after Stage 1, or on entry after Stage 1; #925) — NOT writer-emitted. Records the intake + disclosure layer for an experiment the scholar ran EXTERNALLY and brought results back from. ARS does not run experiments, does not auto-fill provenance, and does not judge whether an experiment was correctly designed/run/statistically-adequate/reproducible by ARS (POSITIONING non-goals, carried verbatim into the integrity gate wording). The entry backs manuscript claims that cite it via claim_intent_manifest.planned_experiment_ids[]. Cross-array invariants EP-INV-1..EP-INV-4 (in-passport experiment_id uniqueness, planned_experiment_ids resolution, empirical-kind gating, declaration symmetry) are lint-enforced in scripts/check_claim_audit_consistency.py — JSON Schema cannot express cross-array integrity. Shape-only validation also available standalone via scripts/check_experiment_provenance.py. The nested repro_lock sub-shape re-declares (does NOT $ref) the inline-object design from shared/artifact_reproducibility_pattern.md; the canonical field set is single-sourced in scripts/repro_lock_validation.py and a drift test asserts the two copies stay in sync. See docs/design/2026-06-08-260-experiment-provenance-intake-spec.md.",
"type": "object",
"additionalProperties": false,
"required": [
"experiment_id",
"title",
"repro_lock",
"planned_vs_executed",
"negative_results",
"known_limitations"
],
"allOf": [
{
"title": "repro_lock_reason accompanies a null repro_lock and nothing else (#1049)",
"if": {
"required": ["repro_lock"],
"properties": { "repro_lock": { "type": "null" } }
},
"then": { "required": ["repro_lock_reason"] },
"else": { "not": { "required": ["repro_lock_reason"] } }
}
],
"properties": {
"experiment_id": {
"type": "string",
"minLength": 1,
"pattern": "^[A-Za-z0-9][A-Za-z0-9._-]*$",
"description": "Scholar-chosen identifier, flat within ONE Material Passport (a passport is one run). EP-INV-1 enforces in-passport uniqueness. Cross-passport consumers treat the durable key as (passport_hash, experiment_id). FROZEN at intake (D3 intake-freeze): once experiment_intake_declaration.status == experiments_declared is set, this is the stable key space writers reference via planned_experiment_ids. A post-intake rename is a re-intake event (re-run the manifest emitters), NOT a silent edit — EP-INV-2 FAILs a passport whose planned_experiment_ids dangle after a rename."
},
"title": {
"type": "string",
"minLength": 1,
"maxLength": 500,
"description": "Human-readable label for the experiment (e.g. 'Ablation: remove attention head pruning')."
},
"description": {
"type": "string",
"maxLength": 4000,
"description": "Optional free-form description of what the experiment tested and why."
},
"repro_lock": {
"type": ["object", "null"],
"additionalProperties": false,
"description": "Per-experiment reproducibility lock — the SAME inline-object shape as the passport-level repro_lock (shared/artifact_reproducibility_pattern.md), nested here so each experiment carries its own configuration trail. Re-declared (not $ref'd) because the source is an inline-prose object, not a schema file; the canonical required-field set is single-sourced in scripts/repro_lock_validation.py with a drift test. Documents configuration, NOT a deterministic replay guarantee. The KEY MUST be present. Its value is null when any of these fields has no honest value for the experiment, for example a survey, an analysis that used no LLM or ARS session, or a trained model with no ARS prompts to hash; repro_lock_reason then says why (#1049).",
"required": [
"schema_version",
"stochasticity_declaration",
"ars_version",
"model",
"prompts",
"materials",
"external_protocols",
"cross_model"
],
"properties": {
"schema_version": { "const": "1.0" },
"stochasticity_declaration": { "type": "string", "minLength": 1 },
"ars_version": { "type": "string", "minLength": 1 },
"model": {
"type": "object",
"additionalProperties": false,
"required": ["family", "id", "weight_stable"],
"properties": {
"family": { "type": "string", "minLength": 1 },
"id": { "type": "string", "minLength": 1 },
"weight_stable": { "type": "boolean" }
}
},
"prompts": {
"type": "object",
"additionalProperties": false,
"required": ["hash_timing", "skill_md_hash", "agents_bundle_hash"],
"properties": {
"hash_timing": { "const": "skill-load" },
"skill_md_hash": { "type": "string", "minLength": 1 },
"agents_bundle_hash": { "type": "string", "minLength": 1 }
}
},
"materials": {
"type": "object",
"additionalProperties": false,
"required": ["list_hash", "count"],
"properties": {
"list_hash": { "type": "string", "minLength": 1 },
"count": { "type": "integer", "minimum": 0 }
}
},
"external_protocols": {
"type": "object",
"additionalProperties": false,
"required": ["s2_api_protocol_version", "s2_snapshot_available"],
"properties": {
"s2_api_protocol_version": { "type": "string", "minLength": 1 },
"s2_snapshot_available": { "type": "boolean" }
}
},
"cross_model": {
"type": "object",
"additionalProperties": false,
"required": ["enabled", "secondary_model_id"],
"properties": {
"enabled": { "type": "boolean" },
"secondary_model_id": { "type": ["string", "null"] }
}
}
}
},
"repro_lock_reason": {
"type": "string",
"minLength": 1,
"maxLength": 2000,
"pattern": "\\S",
"description": "Why this experiment records no repro_lock, in the scholar's words, naming any real details such as the model id. Required when repro_lock is null, rejected when it is an object. Free text: it discloses the gap, does not prove the lock does not apply, and no script checks the details it names (#1049)."
},
"planned_vs_executed": {
"type": "array",
"minItems": 1,
"description": "Per-result-unit record of what the scholar PLANNED to measure vs what was actually EXECUTED. minItems 1 — an experiment_provenance entry with no planned_vs_executed unit is a degenerate declaration that backs no claim. The integrity gate (D6 check-2) reads executed:false + skip_reason and feeds the all-skipped derivation rule (every entry executed:false ⟹ a claim resting on this experiment is NOT_SUPPORTED_BY_PROVENANCE).",
"items": {
"type": "object",
"additionalProperties": false,
"required": ["planned", "executed"],
"properties": {
"planned": {
"type": "string",
"minLength": 1,
"description": "What the scholar planned to measure (e.g. 'F1 on held-out test set with head-pruning removed')."
},
"executed": {
"type": "boolean",
"description": "Whether this planned unit was actually run. executed:false MUST carry skip_reason (gate check, D6 check-2)."
},
"skip_reason": {
"type": "string",
"minLength": 1,
"description": "Required-by-gate when executed:false (D6 check-2, not a schema conditional so a malformed skip surfaces at the gate with full context). Why the planned unit was not run."
},
"result_file": {
"type": "string",
"minLength": 1,
"description": "Pointer to the scholar's reported result artifact (path/URI). The experiment_alignment_result.result_pointer points INTO this (e.g. result_file + metric) — experiment_id alone is too coarse for a claim like 'F1 improved 4.2%'."
},
"metric": {
"type": "string",
"minLength": 1,
"description": "Optional metric name the reported result reports (e.g. 'macro-F1')."
},
"value": {
"type": ["number", "string"],
"description": "Optional reported value for the metric (number or string)."
}
}
}
},
"negative_results": {
"type": "array",
"description": "Declared null/absent/contradicting findings. The KEY MUST be present (D6 check-0 absent-key rule, ported from #261 C3); an empty [] is well-formed and routes to the check-4 advisory. An ABSENT key is malformed → gate FAIL. A manuscript claim that contradicts a negative_results entry is NOT_SUPPORTED_BY_PROVENANCE (D4 derivation rule), not merely a disclosure advisory.",
"items": {
"type": "object",
"additionalProperties": false,
"required": ["description"],
"properties": {
"description": { "type": "string", "minLength": 1, "maxLength": 2000 },
"result_file": { "type": "string", "minLength": 1 }
}
}
},
"known_limitations": {
"type": "array",
"description": "Declared material limitations of the experiment. The KEY MUST be present (D6 check-0 absent-key rule); empty [] is well-formed and routes to the check-4 advisory; an ABSENT key is malformed → gate FAIL. Surfaced in Limitations prose (D6 check-4 advisory).",
"items": {
"type": "object",
"additionalProperties": false,
"required": ["description"],
"properties": {
"description": { "type": "string", "minLength": 1, "maxLength": 2000 }
}
}
}
}
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |