Home / nova-violet-role / rot-dtd-commander · GitHub

debug-like-expert-dtd SKILL.md skillA

debug-like-expert-dtd from nova-violet-role/rot-dtd-commander is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add nova-violet-role/rot-dtd-commander/debug-like-expert-dtd@git:20260916.b7506d7

Pins git:20260916.b7506d7 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: nova-violet-role/rot-dtd-commander
Path: src/skills/debug-like-expert-dtd/SKILL.md
Versions recorded: 4
Latest version: git:20260916.b7506d7, committed Sep 16, 2026
First version recorded: Sep 2, 2026
Size: 14,362 bytes
Repository stars: 3
License: AGPL-3.0

Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis. Carries its own DOCTYPE: a declared output grammar, a trust boundary and laws the checker enforces.

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

<!-- SPDX-License-Identifier: (AGPL-3.0-or-later OR EUPL-1.2) AND MIT -->
<!-- Copyright 2026 Saimonokuma. -->
<!-- Portions Copyright 2025 Lex Christopherson, MIT (taches-cc-resources); see NOTICE.md. -->
<!-- SPDX-FileCopyrightText: 2025 Lex Christopherson (taches-cc-resources, MIT) -->

<!DOCTYPE investigation [
  <!ENTITY % cc-core SYSTEM "../../../dtd/cc-core.dtd">
  %cc-core;
  <!ENTITY % cc-ask SYSTEM "../../../dtd/cc-ask.dtd">
  %cc-ask;
  <!ENTITY % cc-cache SYSTEM "../../../dtd/cc-cache.dtd">
  %cc-cache;
  <!ELEMENT investigation (symptom, evidence+, hypothesis+, root_cause, fix, verification)>
  <!ELEMENT symptom (#PCDATA)>
  <!ELEMENT evidence (#PCDATA)>
  <!ELEMENT hypothesis (prediction, test, verdict)>
  <!ELEMENT prediction (#PCDATA)>
  <!ELEMENT test (#PCDATA)>
  <!ELEMENT verdict (#PCDATA)>
  <!ELEMENT root_cause (#PCDATA)>
  <!ELEMENT fix (#PCDATA)>
  <!ELEMENT verification (#PCDATA)>
  <!ATTLIST evidence id ID #REQUIRED kind (log|repro|read|measurement) #REQUIRED>
  <!ATTLIST hypothesis id ID #REQUIRED supported_by IDREFS #IMPLIED>
  <!ATTLIST verdict result (confirmed|refuted|untested) #REQUIRED>
  <!ATTLIST root_cause hypothesis IDREF #REQUIRED>
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add nova-violet-role/rot-dtd-commander/debug-like-expert-dtd@sha256:c312904618cee480

The line at the top of this page pins the label git:20260916.b7506d7, 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_l2xjliwkojb3nfrz.svg)](https://markdownregistry.com/a/art_l2xjliwkojb3nfrz)

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

Versions

The registry has recorded 4 versions of this file, between Sep 2, 2026 and Sep 16, 2026, about one every 5 days.

version	committed	commit	size	audit
git:20260916.b7506d7 latest	2026-09-16	b7506d7	14,362 B	A	view · diff
git:20260907.f163678	2026-09-07	f163678	14,226 B	A	view · diff
git:20260902.622f086	2026-09-02	622f086	14,132 B	A	view · diff
git:20260902.0a9600a	2026-09-02	0a9600a	14,130 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 (14362 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

nova-violet-role/rot-dtd-commander · 3 stars · license AGPL-3.0 · pushed 2026-09-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_l2xjliwkojb3nfrz
GET https://markdownregistry.com/api/v1/resolve?ref=nova-violet-role/rot-dtd-commander/debug-like-expert-dtd
GET https://markdownregistry.com/api/v1/blob/c312904618cee480131d50d0019a5f8c18b46a0518695582181fa216e1248967

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 nova-violet-role/rot-dtd-commander

ai-slop-dtd SKILL.md skill

nova-violet-role/rot-dtd-commander · skills/ai-slop-dtd/SKILL.md · The AI_SLOP gate, the voice contract of every -dtd answer and, when the Adiutor is armed, of every answer, file, commit…