Home / internal / hermes-skills / daily-voice-note-publishing.md

Skill: daily-voice-note-publishing

Daily Voice Note Publishing

Overview

Use this skill when a user sends voice notes, or already-transcribed microphone text, and wants them accumulated into exactly one markdown document per day. The core pattern is append notes incrementally to a daily document, keep the document public if requested, and preserve a consistent ordering and timestamp scheme.

This skill is especially useful for chat-driven capture workflows where the user may send multiple short notes during the day and expects a live public record rather than separate files.

When to Use

Do not use this skill for: - one-off transcription requests with no daily aggregation requirement - private note capture where no publication target was requested - workflows that require one file per recording instead of one file per day

Workflow

  1. Confirm the publication target and aggregation rule.
  2. Verify whether “public markdown” means publishing to a public site such as Hermes WWW.

  3. Confirm whether there must be exactly one file per day.

  4. Treat voice and transcript inputs equivalently.

  5. If the message contains only a voice note, transcribe it.
  6. If the message already contains an automatic microphone transcript, treat that text as the note content without re-transcribing.

  7. If there is short accompanying text, treat it as note context rather than ignoring it.

  8. Use day-local aggregation.

  9. Store all notes for the same day in one markdown file.
  10. Create the file if it does not exist; otherwise update the existing file.

  11. Keep a stable per-day path so later notes update the same public URL.

  12. Timestamp every entry in the requested timezone.

  13. If the user specified a timezone, use it consistently for every note header.

  14. Record both date and time on each note entry.

  15. Order entries newest-first when requested.

  16. Insert the new note near the top of the daily file rather than appending to the bottom.

  17. Update the document-level “last updated” timestamp when the file changes.

  18. Publish and verify.

  19. Refresh any manifest/index used by the publishing system.
  20. Verify the public URL responds before reporting success.
# Recorder — YYYY-MM-DD

Public daily log of voice notes.

- Date: YYYY-MM-DD
- Timezone: Europe/Prague (CEST/CET)
- Ordering: newest first
- Updated: YYYY-MM-DD HH:MM:SS CEST

## YYYY-MM-DD HH:MM:SS CEST

- Type: voice note / automatic microphone transcript
- Source: <chat/thread>

### Transcript

<transcribed text>

Adapt the title and source labels to the user’s naming conventions.

Public Publishing Pattern

When the user wants public publication on Hermes WWW or a similar static/public markdown host:

Common Pitfalls

  1. Creating multiple files in one day. If the user asked for exactly one published markdown per day, always update the existing daily file instead of creating a new one per note.

  2. Treating auto-transcribed microphone text as ordinary chat. If the user says it is an automatic transcript from the mic, treat it as a note to publish, not as a normal instruction message.

  3. Appending in the wrong order. Some users want a chronological log, but this workflow may require newest-first. Confirm once, then preserve that ordering every time.

  4. Dropping short companion text. A short text next to a voice note may be part of the note context; do not ignore it by default.

  5. Reporting success before URL verification. After writing and publishing, verify that the public URL actually responds.

Supporting Files

Verification Checklist