data-first-execution
Skill0 starsChanged 3 days agoMITView on GitHub
Data-first execution policy. Requires checking existing data, historical results, and execution records first, avoiding unjustified re-collection, recomputation, and re-execution.
In this repository17 other files it gives its agents.
- .cursor/rules/engineering-context.mdcCursor rule
- change-report-deliverySkill
- code-asset-inventorySkill
- data-audit-reproducibilitySkill
- 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
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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 13
Before performing any data analysis, statistics, collection, transformation, or business judgment, existing data and historical execution …
- Distinctive: line 45
When it was executed.
- Distinctive: line 95
Do the collection conditions allow it to be obtained?
- Distinctive: line 103
When data genuinely needs to be supplemented:
- Distinctive: line 111
Verify the merged result.
- Distinctive: line 117
Every significant data processing operation should record:
- Distinctive: line 127
When historical data changes, the difference between the old and new versions should be identifiable.
- Distinctive: line 144
Do not keep executing operations in order to appear productive.
≈ “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-First Execution Policy
I. Core Principle
Existing data takes priority over re-execution, and existing conclusions take priority over repeated computation.
Before performing any data analysis, statistics, collection, transformation, or business judgment, existing data and historical execution results must be checked first.
It is forbidden to use repeated execution in place of analysis and judgment.
II. Required Checks Before Execution
1. Inspect Existing Data
Check:
- Raw data files.
- Processed data files.
- Intermediate data files.
- Database records.
- Historical export files.
- Caches.
- Temporary data.
- Generated analysis results.
2. Inspect Historical Analysis
Confirm:
- Whether the same analysis has already been executed.
- Whether statistics results already exist.
- Whether analysis reports have already been generated.
- Whether directly reusable intermediate results exist.
- Whether the data version used by the historical results conforms to the current task.
3. Inspect Historical Execution Records
Confirm:
- Whether related tasks have been executed before.
- Which data was used.
- When it was executed.
- Whether it succeeded.
- Where the output files are.
- Whether there are failure or partial completion records.
4. Inspect Whether the Data Is Applicable
The existence of a file does not mean the data is usable.
Must check:
- Data source.
- Data version.
- Update time.
- Field structure.
- Data volume.
- Data completeness.
- Whether it conforms to the current analysis scope.
III. Execution Decision
| Current Situation | Correct Handling |
| Existing data is complete and applicable | Use it directly |
| Existing data is sufficient but not yet analyzed | Analyze based on existing data |
| Only partial data exists | Supplement only the missing portion |
| Historical results can be reused | Reuse them directly |
| Data structure has changed | Check the impact of the change, then decide |
| Data is outdated | State the basis for it being outdated, then decide whether to update |
| Data is corrupted | Locate the extent of corruption and repair locally where possible |
| Data does not match the current task | State the mismatch |
IV. Unjustified Repeated Execution Is Forbidden
Forbidden:
- Re-collecting without first checking existing data.
- Re-collecting all data when complete data already exists.
- Repeatedly recomputing analysis results without reason when they already exist.
- Re-running the entire pipeline to verify a single local issue.
- Repeatedly running the program merely because the result is uncertain.
- Repeatedly calling a successful interface without checking historical records.
- Assuming a program should be re-run merely because it is runnable.
V. Distinguish Missing Data from Being Outside the Collection Scope
The absence of a certain item in the data does not necessarily mean re-collection is required.
Must determine:
- Does the current task require that item to be included?
- Does the original collection scope cover it?
- Do the collection conditions allow it to be obtained?
- Did historical data genuinely omit it?
- Is the absence in the current data itself a valid result?
The collection scope must not be expanded merely to make the data look more complete.
VI. Incremental Execution Principle
When data genuinely needs to be supplemented:
- Clarify the existing data.
- Clarify the missing data.
- Clarify the reason for the absence.
- Clarify the supplementation operation.
- Execute only the necessary incremental task.
- Distinguish newly added data from historical data.
- Verify the merged result.
Existing data must not be overwritten without reason.
VII. Data Version Management
Every significant data processing operation should record:
- Data source.
- Data version or file hash.
- Data generation time.
- Data processing program version.
- Configuration used.
- Processing parameters.
- Final output version.
When historical data changes, the difference between the old and new versions should be identifiable.
VIII. Output Requirements
At the end of every data task, state:
- Which existing data was used.
- Which historical results were reused.
- Whether new collection was performed.
- Whether new computation was performed.
- Why these new operations were necessary.
- The actual execution scope.
- The final output location.
- Which conclusions still lack data support.
IX. Highest Principle
Do not keep executing operations in order to appear productive.
First understand the existing results, then determine what is genuinely missing, and finally execute the minimum necessary operation.
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.

