data-audit-reproducibility
Skill0 starsChanged 3 days agoMITView on GitHub
Raw data preservation, data source tracing, data processing audit, and historical execution reproducibility standard. Ensures humans can independently inspect the data and reproduce the results.
In this repository17 other files it gives its agents.
- .cursor/rules/engineering-context.mdcCursor rule
- change-report-deliverySkill
- code-asset-inventorySkill
- data-first-executionSkill
- documentation-structureSkill
- engineering-context-completenessSkill
- engineering-transparencySkill
- explicit-instruction-fidelitySkill
- interface-contractSkill
- language-expressionSkill
- production-loggingSkill
- repository-publication-hygieneSkill
- task-execution-governanceSkill
- technical-documentationSkill
- testing-verificationSkill
- unfinished-work-trackingSkill
- user-intent-prioritySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. About 0 are common, 16 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Every significant transformation is recorded.
- Distinctive: line 22
Every output can be traced back to its input source.
- Distinctive: line 28
When data processing is involved, the following process must be made explicit:
- Distinctive: line 70
Only a statistical summary must not be stored.
- Distinctive: line 71
Only Agent-summarized data must not be retained.
- Distinctive: line 79
If complete preservation is impossible due to storage, privacy, or data volume limits, the limits, the truncation range, and an alternative …
- Distinctive: line 103
Every piece of significant data should record at least:
- Distinctive: line 117
If the source is unclear, it must be marked as unknown.
- Distinctive: line 121
Every significant data transformation should record at least:
- Distinctive: line 155
Must be able to reconcile:
- Distinctive: line 159
When the actual business involves splitting, merging, or duplicate records, the counting criteria must be explicitly stated.
- Distinctive: line 167
If modification is necessary:
- Distinctive: line 194
When reproducing, prefer historical input data rather than re-collecting.
- Distinctive: line 196
If external services, models, or third-party data have already changed, it must be clearly stated that the historical environment cannot be …
- Distinctive: line 235
Must be able to answer:
- Distinctive: line 248
When these cannot be answered, do not claim the data processing has complete audit capability.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Data Audit and Reproducibility Standard
I. Core Principle
Data must be independently inspectable by humans.
An Agent's analysis result cannot substitute for raw data.
Final output must be traceable to real inputs and the actual processing steps.
Must guarantee:
- Raw data has an actual storage location.
- Raw data has not been overwritten by processing results.
- Every significant transformation is recorded.
- Every output can be traced back to its input source.
- Historical executions can be identified and reproduced.
- Humans can inspect the data without relying on the Agent's summaries.
II. Data Lifecycle
When data processing is involved, the following process must be made explicit:
Raw data ↓ Data parsing ↓ Data normalization ↓ Data filtering ↓ Data cleaning ↓ Data transformation ↓ Data analysis ↓ Final output
The actual process may differ, but it must faithfully reflect the steps the program really executes.
Processing steps must not be fabricated in order to match the illustrative flow.
III. Raw Data Preservation
Raw data must be stored separately from processing results.
The scope includes:
- Raw API responses.
- Web collection results.
- Raw JSON.
- Raw CSV.
- Raw HTML.
- Raw database exports.
- Raw files.
- User-provided raw data.
- Results returned by external tools.
Preservation requirements:
- Preserve the complete raw content as far as possible.
- Cleaned data must not overwrite raw data.
- Only a statistical summary must not be stored.
- Only Agent-summarized data must not be retained.
- Record the raw data storage location.
- Record the data generation time.
- Record the source.
- Record the file size.
- Record the data hash.
- Record whether the preservation is complete.
If complete preservation is impossible due to storage, privacy, or data volume limits, the limits, the truncation range, and an alternative storage location must be explicitly recorded.
Incomplete data must not be marked as complete data.
IV. Separation of Raw Data and Processed Data
The following directory organization is recommended; existing project directories may be used as they are:
data/ ├── raw/ │ └── raw inputs ├── intermediate/ │ └── intermediate processing results ├── processed/ │ └── cleaned and normalized results ├── output/ │ └── final output └── audit/ └── data processing records
Existing data must not be relocated repeatedly just to adopt this directory layout.
V. Data Source Records
Every piece of significant data should record at least:
- Data name.
- Data source.
- Source file or interface.
- Retrieval time.
- Retrieval batch.
- Generating module.
- Raw file location.
- File hash.
- Data format.
- Data version.
- Data scale.
If the source is unclear, it must be marked as unknown; the source must not be guessed.
VI. Data Transformation Records
Every significant data transformation should record at least:
- Execution ID.
- Input file.
- Input file hash.
- Output file.
- Output file hash.
- Executing function.
- Executing program version.
- Parameters used.
- Configuration used.
- Transformation rules.
- Input record count.
- Output record count.
- Excluded record count.
- Exclusion reasons.
- Execution time.
- Execution status.
It must be possible to explain how the input data became the output data.
VII. Data Count Reconciliation
Significant processing stages should record count changes.
For example:
Raw records: 1000 Parsed successfully: 980 Parse failures: 20 Retained after filtering: 650 Excluded by filtering: 330 Final output: 650
Must be able to reconcile:
Raw count = successfully processed count + failure count
When the actual business involves splitting, merging, or duplicate records, the counting criteria must be explicitly stated.
Data must not be fabricated in order to satisfy count equality.
VIII. Data Modification and Integrity Protection
Raw data is in principle stored read-only.
If modification is necessary:
- Retain the pre-modification version.
- Generate a new version.
- Record the reason for modification.
- Record the modifying program.
- Record the modification time.
- Record the before and after hashes.
A hash is used to check whether a file has changed; it does not mean the data content itself is correct.
IX. Historical Execution Reproduction
Significant executions must preserve sufficient reproduction information:
- run_id.
- Input data version.
- Input data hash.
- Code version or commit ID.
- Configuration file version.
- Runtime parameters.
- Dependency versions.
- Execution environment.
- Random seed (where applicable).
- External service version or response snapshot (where applicable).
- Output location.
When reproducing, prefer historical input data rather than re-collecting.
If external services, models, or third-party data have already changed, it must be clearly stated that the historical environment cannot be fully restored.
It must not be claimed that every execution can be reproduced one hundred percent.
X. Independent Human Audit
Humans must be able to directly inspect:
- Raw data.
- Data file structure.
- Real records.
- Processing parameters.
- Transformation rules.
- Filtering conditions.
- Excluded records.
- Final output.
- Execution logs.
- Data version and integrity information.
Humans must not be required to understand the data only through the Agent's explanation.
Provide direct access via CSV, JSON, database queries, or other means when necessary.
XI. Privacy and Security
Sensitive information must receive appropriate protection.
But the following must be distinguished:
- Fields that need masking.
- Fields that can be retained normally.
- Fields that must not be persisted.
- Fields that may only be retained for a short period.
Audit information for an entire event must not be deleted merely to protect a single sensitive field.
For content that cannot be saved, the necessary source, time, operation, and limitation notes must be retained.
XII. Acceptance Criteria
Must be able to answer:
- Where is the raw data?
- Where did the data come from?
- Is the raw data complete?
- Was the data modified?
- What processing did each step undergo?
- Which records were excluded?
- Why were they excluded?
- How was the final data generated?
- Which execution produced this result?
- Can it be re-executed using historical inputs?
When these cannot be answered, do not claim the data processing has complete audit capability.
XIII. Final Principle
Data is fact; the Agent's interpretation is opinion.
The fact itself must be preserved so that humans retain the ability to inspect and judge independently.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

