agentleFS
bestdeejay-designbestdeejay-design/agent-skills/skills/chronos/SKILL.md

chronos

Skill6 starsChanged 3 months agoMITView on GitHub

Documentation Timekeeper — 5 AI agents (Chronos, Censor, Dewey, Veles, Canon) for documentation integrity. Checks: duplicates, broken links, missing required docs, orphans, classification (L1-L6), stale dates. Use when: "check documentation", "docs audit", "audit docs", "docs integrity", "find duplicates in docs", "broken links", "stale documentation", "classify docs", "documentation health", "orphan docs", "validate docs", "doc quality", "docs lint", "chronos".

  • Installs packages

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create .chronos.yml in project root:

    line 159
  2. Distinctive:

    Every Chronos run must pass:

    line 193
  3. Very specific:

    Do not use for a single narrow check when censor, dewey, or veles is sufficient.

    line 207

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Chronos — Documentation Timekeeper

5 AI agents for documentation integrity. Each agent is a focused skill invoked by the Chronos orchestrator.

What it does

Chronos audits project documentation for:

  • Duplicates — documents with high similarity (Censor)
  • Broken links — references to non-existent files (Censor)
  • Missing required docs — mandatory files per classification level (Dewey)
  • Orphans — documents with no inbound references (Dewey)
  • Classification — document type: L1 Contracts → L6 Auxiliary (Dewey + Canon)
  • Stale data — dates older than threshold (Veles)

Agents

AgentRoleTrigger
ChronosOrchestrator — runs the full Pantheonchronos --preset full
CensorFact-checker — duplicates + broken linkschronos --preset minimal
DeweyClassifier — L1-L6 taxonomy + missing/orphanschronos --preset standard
VelesStatistician — staleness, metrics, trendschronos --preset full
CanonTruth-keeper — cross-ref validation against contractschronos --preset standard

Usage

# Basic audit (duplicates + links only)
chronos --path .

# Standard: check + classify (Censor + Dewey + Canon)
chronos --path . --preset standard

# Full Pantheon: all 5 agents
chronos --path . --preset full

# JSON output for CI
chronos --path . --output json --output-file report.json

# Fail on critical findings
chronos --path . --fail-on critical

# Single agent
chronos --path . --agent censor

Presets

PresetAgentsUse case
minimalCensorQuick CI gate — duplicates + broken links
standardCensor + Dewey + CanonPR validation — check + classify + cross-ref
fullAll 5 agentsRelease audit — complete integrity + staleness

Document Hierarchy (L1–L6)

L1: Contracts        — Machine truth (OpenAPI, AsyncAPI, JSON Schema)
L2: Product Canon    — Human truth (VISION, PRD, ROADMAP, FEATURES)
L3: Engineering Canon— Implementation truth (ARCHITECTURE, ADR, SAGA)
L4: Derived          — Synthesized (REFERENCE, TEST_CASES, DEV_GUIDE)
L5: Artifacts        — Generated (API docs, changelogs, diagrams)
L6: Auxiliary        — Supporting (README, CONTRIBUTING, templates)

Each level has required files. Dewey enforces presence; Canon validates L1→L3 consistency.

Output Format

# Docs Audit Report

**Project:** /path/to/project
**Total docs:** 24
**Preset:** standard

| Severity | Count |
|----------|-------|
| Critical | 1 |
| Warning  | 3 |
| Info     | 2 |
| **Total**| **6** |

### CRITICAL

**File:** docs/API.md:42
**Issue:** Endpoint GET /users documented as Deprecated, but contract shows Active.
**Fix:** Update docs/API.md to match OpenAPI contract.

### WARNING

**File:** docs/ARCHITECTURE.md
**Issue:** Orphan document — no inbound references from L2/L3.
**Fix:** Link from PRD or add to REFERENCE.md.

### INFO

**File:** docs/DEV_GUIDE.md
**Issue:** Last updated 2024-01-15 (stale >180 days).
**Fix:** Review and update or archive.

Triggers

  • check documentation / docs audit / audit docs
  • docs integrity / documentation health
  • find duplicates in docs / duplicate docs
  • broken links / broken references
  • stale documentation / outdated docs
  • classify docs / document classification
  • orphan docs / unreferenced documents
  • validate docs / doc quality / docs lint
  • chronos

Installation

pip install chronos

Or run directly:

python -m chronos --path .

Project Structure

skills/chronos/
├── SKILL.md              # This file
├── src/chronos/          # Python package
│   ├── cli.py            # CLI entry point
│   ├── agents/           # base, censor, dewey, veles, chronos, canon
│   └── core/             # document reader and report renderer
├── tests/                # pytest tests for agents and core
├── docs/                 # package architecture, PRD, and vision
├── references/           # taxonomy, agent, and CLI contracts
└── pyproject.toml

Configuration

Create .chronos.yml in project root:

path: "."
preset: "standard"
fail_on: "warning"
output: "markdown"
thresholds:
  duplicate_similarity: 0.85
  stale_days: 180
  required_levels:
    L1: ["contracts/openapi.yaml"]
    L2: ["VISION.md", "PRD.md", "ROADMAP.md"]
    L3: ["ARCHITECTURE.md", "ADR/"]
    L4: ["REFERENCE.md"]
    L6: ["README.md", "CONTRIBUTING.md"]
ignore:
  - "node_modules/**"
  - ".git/**"
  - "dist/**"

CI Integration

# .github/workflows/docs-audit.yml
- name: Chronos Docs Audit
  run: |
    pip install chronos
    chronos --path . --preset standard --fail-on warning --output json --output-file chronos-report.json

Verification Gates

Every Chronos run must pass:

  1. Structural — output is valid Markdown/JSON
  2. Content QA — each finding has file:line, issue, fix
  3. Reproducibility — same input → same output (deterministic hashing)

References

  • references/CLASSIFICATION.md — L1-L6 taxonomy details
  • references/AGENTS.md — Agent prompt templates
  • references/CONFIG.md — Full config schema

Boundaries

  • Do not use for a single narrow check when censor, dewey, or veles is sufficient.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.