source-to-claim-map
Skill0 starsChanged 3 months agoMITView on GitHub
Build a traceable mapping between document claims and the sources or evidence intended to support them.
In this repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- abstract-reviewSkill
- literature-gapSkill
- methodology-reviewSkill
- paper-structureSkill
- results-discussion-alignmentSkill
- reviewer-responseSkill
- book-outlineSkill
- chapter-purposeSkill
- character-consistencySkill
- narrative-arcSkill
- pacing-checkSkill
- timeline-consistencySkill
- citation-accuracySkill
- citation-checkSkill
- citation-completenessSkill
- citation-generationSkill
- citation-relevanceSkill
- citation-styleSkill
- duplicate-reference-checkSkill
- reference-list-checkSkill
- source-claim-mappingSkill
- active-voiceSkill
- ambiguity-checkSkill
- clarity-checkSkill
- coherence-checkSkill
- concision-checkSkill
- grammar-checkSkill
- jargon-checkSkill
- parallelism-checkSkill
- passive-voiceSkill
- proofreadingSkill
- punctuation-checkSkill
- readability-checkSkill
- redundancy-checkSkill
- repetition-checkSkill
- spelling-checkSkill
- terminology-consistencySkill
- tone-checkSkill
- attribution-auditSkill
- claim-auditSkill
- final-document-auditSkill
- overclaiming-checkSkill
- plagiarism-risk-reviewSkill
- quotation-integritySkill
- self-plagiarism-riskSkill
- source-provenanceSkill
- chapter-structureSkill
- manuscript-consistencySkill
- manuscript-readinessSkill
- manuscript-structureSkill
- title-page-checkSkill
- cover-letterSkill
- ethics-disclosure-checkSkill
- journal-fitSkill
- peer-review-readinessSkill
- submission-requirementsSkill
- coherence-checkSkill
- completeness-checkSkill
- consistency-checkSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
Never infer support merely because a citation appears nearby.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Source-to-Claim Map
Extract atomic substantive claims and link each to one or more supporting sources when those sources are available. Record support type: direct, indirect, contextual, contradictory, or absent.
Never infer support merely because a citation appears nearby. Preserve source boundaries and identify claims that require human verification.
Return a structured mapping suitable for downstream citation and evidence audits.
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.