Home / incarnamind / incarnamind · GitHub

chronology SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

chronology from incarnamind/incarnamind is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add incarnamind/incarnamind/chronology@git:20261029.a0889b5

Pins git:20261029.a0889b5 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: incarnamind/incarnamind
Path: resources/skills/chronology/SKILL.md
Versions recorded: 3
Latest version: git:20261029.a0889b5, committed Oct 29, 2026
First version recorded: Oct 26, 2026
Size: 3,813 bytes
Repository stars: 848
License: Apache-2.0

Builds a dated chronology of the events in the record, in order, with every event cited. Use when the User asks for a chronology, a timeline of a matter, or the key dates and events from the Documents.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Chronology

Build a chronology of the events in the record, in date order, each event cited to the Document and place that shows it.

## Which Documents

- The record is every Document in the Question's Search scope: agreements, correspondence, notices, minutes, filings, orders and statements.
- If the Question names a matter, a party or a period, use it to choose the events; don't stop at one Document when the record has more.
- A file's own dates, such as the date it was created or last changed, are not events in the record: never use them as an event's date.

## Gather the material first

Search the Documents before writing anything (search_documents searches only the Documents in the Question's Search scope):

- Search for dates and the words that carry them: "dated", "on", "by", "before", "after", "effective", "served", "filed", "issued", "notified", "expires", "deadline".
- Search for the events themselves: the agreement, each notice, delivery, payment, meeting, order, filing, hearing and termination.
- Search with the Documents' own dates and names after the first results, and make several searches at once where you can.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add incarnamind/incarnamind/chronology@sha256:a6401f44410c07bf

The line at the top of this page pins the label git:20261029.a0889b5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_qyhgef35usjdnq2i.svg)](https://markdownregistry.com/a/art_qyhgef35usjdnq2i)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 3 versions of this file, between Oct 26, 2026 and Oct 29, 2026, about one every day.

version	committed	commit	size	audit
git:20261029.a0889b5 latest	2026-10-29	a0889b5	3,813 B	A	view · diff
git:20261026.756fe80	2026-10-26	756fe80	3,971 B	A	view · diff
git:20261026.62c57af	2026-10-26	62c57af	3,971 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (3813 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

incarnamind/incarnamind · 848 stars · license Apache-2.0 · pushed 2026-11-01 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_qyhgef35usjdnq2i
GET https://markdownregistry.com/api/v1/resolve?ref=incarnamind/incarnamind/chronology
GET https://markdownregistry.com/api/v1/blob/a6401f44410c07bf315d170557b1414b10c2554084dc1c4d4c3fd16a66e90f5f

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from incarnamind/incarnamind

AGENTS.md AGENTS.md file

incarnamind/incarnamind · AGENTS.md

git:20261026.9ba2bac · audit A · 848 stars

CLAUDE.md CLAUDE.md file

incarnamind/incarnamind · CLAUDE.md

git:20261010.877de92 · audit A · 848 stars

cim-red-flags SKILL.md skill

incarnamind/incarnamind · resources/skills/cim-red-flags/SKILL.md · Checks a confidential information memorandum against the data room and lists each claim the Documents don't support or…