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

veles

Skill6 starsChanged 3 months agoMITView on GitHub

Documentation statistician — finds orphan documents (no inbound references), computes documentation metrics, detects dead zones (folders unlinked from main docs), validates link hierarchy L1→L2→L3→L4. Use when: "find orphans", "orphan docs", "unreferenced documents", "documentation stats", "doc metrics", "dead zones", "link hierarchy", "veles".

1 other project uses a version of this.

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/link fact-checking.

    line 77

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

Veles — Statistician

Finds orphan documents, computes documentation metrics, detects dead zones, validates link hierarchy.

What it does

  • Orphans — documents with zero inbound references from other docs
  • Statistics — file count, word count, level distribution, link count
  • Dead zones — folders with no references from main documentation tree
  • Hierarchy validation — enforces L1→L2→L3→L4 reference direction

Link Hierarchy

L1 (Contracts) → L2 (Product Canon) → L3 (Engineering Canon) → L4 (Derived)

Upper levels reference lower levels. Veles flags violations (e.g., L3 referencing L1 directly).

Usage

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

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

Output Format

[nit] orphan: CONTRIBUTING.md — no inbound references from other documents
[info] stats: 12 documents, 4500 words, 3 levels, 28 links
[warning] hierarchy_violation: docs/ADR/001.md (L3) references contracts/openapi.yaml (L1) directly
[info] dead_zone: docs/legacy/ — no references from L1-L4

Metrics Computed

MetricDescription
total_filesMarkdown files scanned
total_wordsAggregate word count
level_distributionCount per L1-L6
link_countTotal internal links
orphan_countDocuments with 0 inbound links
dead_zone_countUnreferenced folders

Triggers

  • find orphans / orphan docs / unreferenced documents
  • documentation stats / doc metrics / documentation statistics
  • dead zones / unlinked folders
  • link hierarchy / reference hierarchy
  • veles

Integration

Loaded by Chronos as part of full preset only.

Boundaries

  • Do not use for duplicate/link fact-checking; use censor.

Evidence and completion gate

Ground recommendations in the supplied repository or brief. State assumptions, missing inputs, and unresolved risks. Return a concrete artifact or checklist with an owner/action for each open item, then verify that the result answers the requested goal rather than merely repeating the framework.

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