Skip to content

K-Dense-AI/scientific-agent-skills / skills/scientific-writing

scientific-writing

Verified

Drafts, revises, and audits scientific manuscripts or reports with explicit evidence provenance, reporting-guideline coverage, authorship accountability, confidentiality controls, and local consistency checks. Use for manuscript sections, references, declarations, tables, figures, or submission preparation when scientific accuracy and traceability matter.

references/evidence_workflow.md

View on GitHub
# Evidence and Provenance Workflow

## Core separation

Drafting and evidence verification are different activities.

- **Drafting** organizes language from already recorded evidence IDs. A draft may remain
  incomplete and uncertain.
- **Verification** requires an accountable human to open the source, confirm the exact
  support and locator, check bibliographic metadata, and record who verified it and
  when.
- A fluent sentence is not evidence. Search snippets, generated summaries, memory, and
  another paper's reference list are discovery aids, not verified support.

## Registries

The scaffold creates five linked records:

1. `source_manifest.json` assigns each source an `E` ID and records identifiers,
   location, confidentiality class, and verification state.
2. `claims.csv` assigns each claim a `C` ID, stores a hash rather than raw claim text,
   and maps the claim to one or more verified `E` IDs.
3. `consistency_manifest.json` binds numeric facts, methods, outcomes, analysis intent,
   units, denominators, sample sizes, and result locations.
4. `authorship.json` records human authorship criteria, CRediT roles, accountability,
   declarations, and AI use.
5. `reporting_coverage.json` records high-level coverage without scoring or certifying
   the manuscript.

These registries contain metadata, not full source documents. Do not paste unpublished
manuscripts, peer-review files, PHI, sensitive datasets, proprietary content, or source
documents into them.

## Claim markers

Append machine-readable markers to every factual or numeric assertion while drafting:

```text
[claim:C001] [evidence:E001,E002]
```

An alternative citation marker is `[@E001]`. Keep the claim and evidence markers on the
same physical line until the audit passes. Use exactly one claim marker per line.
Each line can express a composite claim only when its evidence supports every part.
A final publisher conversion may replace evidence IDs with rendered citations only
after preserving an auditable mapping.

## Verification procedure

For each source:

1. Open the authoritative source or record.
2. Confirm title, author or organization, publication state, year, and identifiers.
3. Record the exact supporting location, such as section, page, table, figure, or
   registry field.
4. Confirm that the source supports the claim's direction, population, intervention or
   exposure, outcome, time point, and uncertainty.
5. Record caveats, retractions, corrections, expressions of concern, or version status.
6. Mark the source verified only after a named human completes the check.

For each claim:

1. Classify it as factual, numeric, method, result, interpretive, or declaration.
2. Remove `[claim:C...]`, `[evidence:E...]`, and `[@E...]` markers from the
   entire physical line, collapse whitespace with `" ".join(text.split())`, then
   SHA-256 the UTF-8 bytes and store the lowercase hexadecimal digest in
   `claims.csv`. Preserve case, punctuation, and other Markdown syntax. The bundled
   `audit_claims.claim_text_hash` function implements this exact normalization.
3. Map it to verified evidence IDs.
4. Record uncertainty and whether the analysis was confirmatory, exploratory,
   descriptive, or not applicable.
5. Keep unsupported or conflicting claims out of submission-ready prose. If useful,
   retain them in a clearly marked unresolved-issues log.

## Drafting gates

Do not infer or complete missing:

- citations, identifiers, quotations, or source locators;
- data values, denominators, units, sample sizes, or statistical results;
- methods, protocol details, analysis decisions, or deviations;
- approvals, consent, registrations, author contributions, conflicts, funding, or
  availability statements.

Use explicit missing states. Preserve negative, null, adverse, unexpected, and
inconclusive findings. Never convert absence of evidence into evidence of no effect.

## Final audit

Run:

```bash
python3 scripts/validate_manifest.py source_manifest.json --kind source --require-verified
python3 scripts/audit_claims.py manuscript.md claims.csv source_manifest.json
python3 scripts/check_consistency.py consistency_manifest.json
python3 scripts/check_references.py source_manifest.json
```

Tool output contains IDs and line numbers, not manuscript or source text. A passing
machine audit supports review; it does not replace human scientific judgment.

The claim audit compares that digest with the current manuscript line and rejects
changed text or multiple claim markers on a line. Re-verify the evidence fit before
replacing an old digest. A matching hash detects text changes; it proves neither
scientific truth nor that a human performed the recorded verification. Hashes are
not encryption and do not anonymize predictable sensitive statements.

The lightweight audit skips headings, comment-start lines, and fenced code; numeric
text outside these regions must be tagged. It cannot identify every untagged
non-numeric assertion or inspect the contents of linked files. Review those manually.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall