agentleFS
Sign inStart free
bestdeejay-designbestdeejay-design/agent-skills/skills/dewey/SKILL.md

dewey

Skill6 starsChanged 3 months agoMITView on GitHub

Document classifier — assigns L1-L6 taxonomy level to each document, enforces required docs per level, detects missing required documents. Use when: "classify docs", "document classification", "missing docs", "required documents", "document taxonomy", "dewey".

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Do not use for duplicate detection, links, or orphan statistics.

    line 73

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

Dewey — Classifier

Assigns taxonomy level (L1-L6) to each document, enforces required documents per project level.

Document Hierarchy (L1–L6)

LevelTypeExamples
L1Contractscontracts/openapi/*.yaml, contracts/asyncapi/*.yaml
L2Product Canondocs/VISION.md, docs/PRD.md, docs/ROADMAP.md, docs/FEATURES.md
L3Engineering Canondocs/ARCHITECTURE.md, docs/ADR/, docs/SAGA/, docs/TEST_CASES.md
L4Deriveddocs/REFERENCE.md, docs/DEV_GUIDE.md, docs/STATUS.md
L5ArtifactsGenerated files (API docs, changelogs, diagrams)
L6AuxiliaryREADME.md, CONTRIBUTING.md, LICENSE, templates

What it does

  • Classifies every document by type and level
  • Determines project maturity level (L1-L3 based on required docs present)
  • Validates required documents exist for detected level

Usage

# Via Chronos orchestrator
chronos --path . --preset standard

# Direct invocation
python -m chronos.agents.dewey --path .

Output Format

[warning] missing: Required L2 document missing — docs/ROADMAP.md
[info] classified: docs/ARCHITECTURE.md → L3 Engineering Canon
[info] project_level: L2 (Product Canon) — 3/4 required docs present

Required Documents per Level

LevelRequired
L1At least 1 contract file (OpenAPI/AsyncAPI/JSON Schema)
L2VISION.md, PRD.md, ROADMAP.md
L3ARCHITECTURE.md, ADR/ directory

Triggers

  • classify docs / document classification
  • missing docs / required documents
  • document taxonomy / doc hierarchy
  • dewey

Integration

Loaded by Chronos as part of standard and full presets.

Boundaries

  • Do not use for duplicate detection, links, or orphan statistics; use censor or veles.

Procedure and output contract

Classify by normalized repository-relative path, report the matched rule, and show the detected maturity level before checking required documents. Required-document findings are warnings until the project declares a stricter policy. Unknown files must be reported as unknown rather than forced into a taxonomy level.

Verification

A useful report includes every document's classification, the rule or pattern that matched it, required documents considered, and a deterministic summary. Review false positives for custom repository layouts before creating files.

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.

Check your setup, free