fix(skills): live-dashboard credits the human author and drops the product-name intro

Authoring standard 4 requires the human first in `author`; the skill was
drafted with Hermes so the tool was credited instead. The intro cited a
third-party product, which is allowed only in LICENSE/credit lines. Also
adds metadata.hermes.category and lowercases tags to match sibling
skills; docs page regenerated for this skill only.

Tests: the two prose tests asserted sentence literals (change-detectors);
they now assert structure — three Procedure phases, a "Done when" per step,
standard headings, and the tool wiring (cronjob/desktop_preview/[SILENT]).
This commit is contained in:
teknium1
2026-09-14 20:57:26 -07:00
committed by Teknium
parent 788601358d
commit b00ebf6210
3 changed files with 23 additions and 43 deletions

View File

@@ -2,12 +2,13 @@
name: live-dashboard
description: "Build self-updating dashboards from live sources."
version: 0.2.0
author: Hermes Agent
author: Teknium (teknium1), Hermes Agent
license: MIT
platforms: [linux, macos, windows]
metadata:
hermes:
tags: [Dashboards, Monitoring, Status, Automation, Reporting]
tags: [dashboards, monitoring, status, automation, reporting]
category: productivity
related_skills: [product-price-monitor, competitor-news-monitor, email-inbox-triage, google-workspace]
blueprint:
schedule: "0 8 * * *"
@@ -16,7 +17,7 @@ metadata:
# Live Dashboard
Turn one sentence — "make a dashboard for our visa applications, update it daily from the email threads and the case-status site" — into a persistent, self-refreshing status page. The user describes what they want to see; you define the data contract, build a self-contained HTML dashboard, verify one live refresh, then schedule the recurring tick. Inspired by Energy's (getenergy.com) natural-language live dashboards, adapted to Hermes's cron + connector architecture.
Turn one sentence — "make a dashboard for our visa applications, update it daily from the email threads and the case-status site" — into a persistent, self-refreshing status page. The user describes what they want to see; you define the data contract, build a self-contained HTML dashboard, verify one live refresh, then schedule the recurring tick.
Setup runs once in the foreground; the recurring refresh runs as a `cronjob` tick. Installing this skill offers a daily all-dashboards sweep via `/suggestions` (the frontmatter blueprint).