argument-selfloop

Solid

Build a final, machine-readable argument snapshot from current H3 sections and refresh section fingerprints before merge. **Trigger**: argument snapshot, section ledger, consistency contract, final section manifest, 论证快照, 一致性契约. **Use when**: section-level mutations are complete and the merge needs a current argument ledger plus content hashes.

Code & Development 506 stars 39 forks Updated today

Install

View on GitHub

Quality Score: 81/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
0
Description 5%
100

Skill Content

# Argument Snapshot Create the final C5 snapshot consumed by merge and later audit. Despite the historical Skill name, the current implementation is not an autonomous rewrite loop. It reads the final H3 files, assigns bounded structural move labels, writes a compact consistency contract, refreshes section hashes, and fails when required prose is absent or too thin. ## Position In The Workflow ```text section writing -> style and numeric hygiene -> logic polish -> paragraph compaction -> argument snapshot -> optional transitions -> merge ``` Running the snapshot after every section mutator prevents the ledger and manifest from describing an earlier draft. ## Inputs - `sections/` - `outline/outline.yml` - `queries.md` - `output/PARAGRAPH_CURATION_REPORT.md` ## Outputs - `output/ARGUMENT_SELFLOOP_TODO.md` - `output/SECTION_ARGUMENT_SUMMARIES.jsonl` - `output/ARGUMENT_SKELETON.md` - refreshed `sections/sections_manifest.jsonl` `SECTION_ARGUMENT_SUMMARIES.jsonl` contains one record per expected H3 and one record per paragraph. Current move labels are deterministic signals drawn from: ```text setup, thesis, contrast, evidence, evaluation, limitation, synthesis, takeaway ``` They make section shape inspectable; they do not prove that an argument is scientifically valid. `ARGUMENT_SKELETON.md` contains a `## Consistency Contract` and a chapter-level map. It is a writer-facing audit artifact, never reader-facing paper content. ## PASS Contract - every expected H3 exists;...

Details

Author
WILLOSCAR
Repository
WILLOSCAR/research-units-pipeline-skills
Created
8 months ago
Last Updated
today
Language
Python
License
None

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

evidence-selfloop

Evidence self-loop for surveys: read evidence bindings + evidence packs, then write an actionable upstream TODO plan (which stage/skill to fix) before writing more prose. **Trigger**: evidence self-loop, evidence loop, evidence gaps, binding gaps, blocking_missing, 证据自循环, 证据缺口回路.

506 Updated today
WILLOSCAR
AI & Automation Solid

argument-governance

Build and audit the manuscript or research-project argument system across intended use, gaps, claims, data, results, experiment roles, contributions, innovation evidence, limitations, and contribution focus. Use when a paper, thesis chapter, review article, or research project needs an explicit argument map, evidence-fit or over/under-balance checks, analysis admission, contribution prioritisation, innovation-evidence checks, or a decision about whether the current emphasis should change; also use for Chinese requests such as 梳理研究项目、研究主线、贡献侧重、创新证据、结果是否支撑论点、主实验与辅助分析、内容或证据是否过多或过少.

38 Updated 3 days ago
yha9806
Testing & QA Listed

snapshot

Task-state snapshots for session handoff. Write a resumable snapshot when wrapping up, restore from it when picking the work back up, trusting its decisions and re-checking its facts. Use when the user says 打个快照 / 交接 / 收尾下次接着做 / 换个会话继续 / 上次做到哪了 / 快没上下文了先记下进度 / snapshot this task / handoff / wrap up this session / pick up where we left off. Do not trigger for jest/vitest test snapshots, VM/database/filesystem snapshots, compressing the current conversation (that is /compact), remembering long-term preferences (that is platform memory), or deliverables addressed to humans (design docs, onboarding docs).

0 Updated 2 weeks ago
liustack