research-architect-evidence-38a523 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited research-architect-evidence-38a523 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Organize executed material into claims that remain inside their evidence and inference boundaries.
Read when available:
paper_output/confirmed_research_spine.md
paper_output/study_design_brief.md
paper_output/analysis_plan.md
paper_output/evaluation_plan.md
paper_output/study_component_registry.md
paper_output/terminology_ledger.md # when present
paper_output/exemplar_adaptation_plan.md # when target references exist
user-supplied results, sources, analyses, observations, or draft claimsIf no verifiable evidence or argumentative material exists, create paper_output/execution_plan.md using ../research-architect/templates/execution_plan.md, identify the next executable actions, and stop before drafting. Do not let a renamed task list substitute for evidence readiness.
Read ../research-architect/references/claim-evidence-framework.md. When the manuscript has multiple claim-bearing displays, also read ../research-architect/references/display-system-planning.md. Use the following CSV files only as column contracts; write Markdown artifacts in paper_output/:
../research-architect/templates/evidence_bank.csv
../research-architect/templates/claim_register.csv
../research-architect/templates/evidence_display_map.csvCreate:
paper_output/evidence_bank.md
paper_output/claim_register.md
paper_output/display_system_plan.md # for multi-display manuscripts
paper_output/evidence_display_map.md
paper_output/claim_strength_calibration.md
paper_output/result_interpretation_notes.mdFor guided depth, produce the evidence bank, claim register, and only the display/interpretation information needed to make a next decision. standard and deep add the complete display and calibration trail.
Every central claim must resolve to evidence IDs, citation IDs, or an explicit limitation; record exact locators, contradictory/null/negative material, and verification status. Use canonical terms and stable Object IDs from the terminology ledger where names alone are ambiguous.
Before individual figure or panel design, create paper_output/display_system_plan.md from ../research-architect/templates/display_system_plan.md when more than one claim-bearing display is planned. Give each display one dominant reader question, core burden, hero evidence, unique non-overlapping role, destination, source-material or data readiness, and forbidden inference. Then create the panel-level evidence_display_map.md, including displayed and inferential units, denominator, comparator purpose, uncertainty/resampling, source-material or data locator, allowed claim, and readiness. A single display may use the same contract in a compact section instead of a separate system plan.
Create evidence_bank.md.metadata.json and claim_register.md.metadata.json with the contracts in ../research-architect/schemas/v1/. Use stable Evidence IDs and Claim IDs so run validation can resolve their links.
Before prose drafting, present the evidence/claim trail, display sequence when applicable, limitations, contradictions, unresolved object collisions, and evidence gaps. On a standard/deep run, use python3 ../research-architect/scripts/first_paper_artifact_check.py paper_output --mode plan and treat any failed prerequisite as a blocker or intake debt. Obtain explicit user approval that the available evidence is ready for the intended draft scope, then record it with python3 ../research-architect/scripts/run_state.py gate paper_output evidence_readiness <status>. Display review belongs inside this gate; do not add another approval gate. If evidence is absent, the run remains at execution_plan.md and cannot pass this gate.
Accept supplied results, tables, interview material, documents, or a draft with claims even when upstream design artifacts are missing. Mark the missing design context as an intake debt or provisional limitation, do not invent it, and route structural gaps to design or intake. Do not convert preliminary material into stronger claims merely to complete a table.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.