skills/Telos/DashboardTemplate is referenced by nothing in the shipped tree — intended, or orphaned by the Packs removal?

[tzioup]

Structured for machine parsing: claims are atomic, each carries the command that verifies it. Every command runs against a full clone of this repo. Reproduction at the bottom.

Summary

LifeOS/install/skills/Telos/DashboardTemplate is a 58-file Next.js app in the install payload. It is copied to <config>/skills/Telos/DashboardTemplate by the main install, and no file in the shipped tree names it — not SKILL.md, not a workflow, not a tool — and per full-history search, none ever did.

I'm stating the reference relationship, not "nothing invokes it": invocation could in principle happen dynamically from SKILL.md prose, which a string search can't see. What's verifiable is that the name appears in no other file.

Its sibling in the same skill, ReportTemplate, differs by exactly one line: Telos/Workflows/WriteReport.md:612 names it (in a ## Maintenance font-copy note — not an invocation, but it does put the template in a live workflow file). DashboardTemplate has no equivalent anywhere. Meanwhile Telos/SKILL.md § Building Dashboards tells the agent to build a Next.js dashboard from scratch — with design tokens matching the template on all seven values and a stack that doesn't match it.

I want to be careful about why it looks orphaned, because the history has a twist that a surface read gets wrong (I did, first pass).

The history, since it's easy to misread

There were two distribution channels, and the name appears in the docs of the one that was removed:

• A per-skill Packs channel (Packs/Telos/), each pack a standalone AI-installable capability with its own src/ copy of the template and its own INSTALL.md/README.md/VERIFY.md.
• The monolith channel (install/skills/Telos/DashboardTemplate), the copy shipped by the full-system install.

36119d2 (2026-07-03, "drop per-skill Packs — skill-only distribution") removed the Packs channel and moved to shipping as one self-contained skill bundle. That deleted the pack docs — which were the only files that named the template.

The trap: those pack docs were inventory manifests, not wiring. Packs/Telos/INSTALL.md:363 listed src/DashboardTemplate/ as "Complete Next.js dashboard app" among the pack's contents; it never tied the template to a workflow. So dropping the packs removed the template's documentation, not any reference from executable skill files — because it never had one.

Claims and verification

git clone https://github.com/danielmiessler/LifeOS && cd LifeOS

C1 — across the repo's entire history, every non-template file that ever contained DashboardTemplate is a Packs manifest or a retired routing-doc example; none wired it to execute, and none survive at HEAD.

git log --all -S'DashboardTemplate' --format='' --name-only | sort -u | grep -v 'DashboardTemplate/'
# .pai-protected.json
# Packs/pai-telos-skill/README.md
# Packs/Telos/INSTALL.md      <- inventory manifest
# Packs/Telos/README.md
# Packs/Telos/VERIFY.md

The kebab form adds exactly one more, also non-wiring and also retired:

git log --all -S'dashboard-template' --format='' --name-only | sort -u | grep -v 'DashboardTemplate/' | grep SKILL-STRUCTURE
# .claude/skills/CORE/SKILL-STRUCTURE-AND-ROUTING.md
# → line 677: "Embedded applications (e.g., `dashboard-template/`)"  — an illustrative example
# CORE is not present at HEAD.

C2 — SKILL.md and the Telos workflows have never, in any revision, named the template. The -S'DashboardTemplate' and -S'Telos/DashboardTemplate' pickaxes return zero SKILL.md/Workflows/ files.

git log --all -S'Telos/DashboardTemplate' --name-only --format='' | sort -u | grep -iE 'SKILL.md|Workflows'
# (empty)

C3 — the sibling ReportTemplate is at least named in a workflow file, which is what makes DashboardTemplate's total absence an inconsistency rather than a convention. (The mention is a maintenance note, not an invocation — I'm not claiming ReportTemplate is "wired," only that it appears in an executable skill file where DashboardTemplate appears in none.)

grep -n ReportTemplate LifeOS/install/skills/Telos/Workflows/WriteReport.md
# 612: cp ~/Projects/[your-site]/public/fonts/*.woff2 ~/.claude/skills/Telos/ReportTemplate/public/fonts/

C4 — Telos/SKILL.md:235-240 instructs building a dashboard from scratch, no mention of the template that ships beside it. Design tokens match on all seven values; stack does not.

token	SKILL.md:253-261	App/globals.css
--background	#ffffff	#ffffff
--primary	#2e7de9	#2e7de9
--accent	#9854f1	#9854f1
--destructive	#f52a65	#f52a65
--success	#33b579	#33b579
--warning	#f0a020	#f0a020
--foreground	#1a1b26	#1a1b26

	SKILL.md:241-247	package.json
Next.js	14	^15.5.16
Aceternity UI	listed	0 occurrences in the tree

C5 — the template's own README documents an install path that doesn't exist.

grep -n 'cp -r' LifeOS/install/skills/Telos/DashboardTemplate/README.md
# cp -r ~/.claude/skills/telos/dashboard-template /path/to/your/project   (no such path ships)

Scope of the claim

• C1/C2 are claims about this repository's history. A reference from something outside the public release would not appear here.
• I make no claim about whether leaving the template unwired is intentional.
• I have not tested whether the from-scratch path in SKILL.md produces a working dashboard.

The question

Now that distribution is monolith-only, which is intended?

1. The template is the deliverable's starting point — then § Building Dashboards should point at it (like WriteReport.md points at ReportTemplate), its README install path needs fixing, and the stack lines (Next 14, Aceternity) need updating to match what ships.
2. The from-scratch instructions are the deliverable — then the template is unreferenced weight and could be removed.

Either is a small change. Worth deciding before the build fixes in the companion issue, since under (2) those are moot.

Reproduction

git clone https://github.com/danielmiessler/LifeOS && cd LifeOS
git log --all -S'DashboardTemplate' --format='' --name-only | sort -u | grep -v 'DashboardTemplate/'
git log --all -S'Telos/DashboardTemplate' --name-only --format='' | sort -u | grep -iE 'SKILL.md|Workflows'   # empty
grep -n ReportTemplate LifeOS/install/skills/Telos/Workflows/WriteReport.md
sed -n '235,262p' LifeOS/install/skills/Telos/SKILL.md

[tzioup]

The two concrete build failures in this template and its sibling are filed separately, per one-fix-per-issue: #1556 (DashboardTemplate case-collision + tsconfig) and #1557 (ReportTemplate <ORG_NAME> JSX parse). If the answer to this issue is "remove DashboardTemplate", #1556 becomes moot.

[danielmiessler]

Decision made: keep it and wire it. SKILL.md's Building Dashboards section now points at DashboardTemplate/ as the starting scaffold (same treatment ReportTemplate gets), and its README copy path is fixed to the real location. Together with the build fixes in #1556 it's now a working, referenced starting point. Thanks for the history analysis that framed the decision cleanly.