Home / internal / hermes-skills / voice-notes-to-daily-markdown.md

Skill: voice-notes-to-daily-markdown

Voice Notes to Daily Markdown

Overview

Use this when Zico is dictating short notes in Discord and wants them turned into a single daily public markdown page instead of being handled synchronously in-chat.

This workflow is optimized for high-throughput dictation: every note becomes queued work first, so the user can keep speaking without waiting for processing to finish.

When to Use

Use this skill when all or most of these are true: - The message is a voice note or an automatic microphone transcript. - The destination is a daily running log, not a one-off response. - The user may send several notes back-to-back. - The final output should be one public markdown per day.

Do not use this for: - Normal conversational requests that expect an immediate answer. - One-off transcription requests where no daily aggregation is wanted. - Private notes that should not be published.

Required Behavior for Zico

For the Rekordér workflow, the defaults are: - Treat voice-note-only messages as notes to capture. - Treat automatic microphone transcripts as valid source notes too. - Assume the dictation is primarily Czech, but may contain English technical terms. - Prefer a corrected Czech reading with embedded English technical expressions over literal noisy STT output. - Maintain exactly one public markdown per day. - Append notes incrementally into that daily file. - Order entries with newest first. - Show timestamp in Europe/Prague (CEST/CET). - Publish the result publicly on Hermes WWW by default. - Keep any internal mirror or working copy optional; the public daily markdown is the primary artifact. - For each note, create Kanban tasks first so the user can keep dictating.

Standard Workflow

  1. Capture the note timestamp in Europe/Prague.
  2. Normalize the transcript lightly.
  3. Fix obvious STT corruption.
  4. Preserve technical product names and anglicisms when they fit the Czech sentence.
  5. Do not over-edit unclear content into invented meaning.
  6. Create a writer Kanban task immediately.
  7. Board: use a healthy board with active dispatcher.
  8. If the preferred multi-agent board is unhealthy, use default rather than blocking the capture flow.
  9. Create a reviewer/fixup Kanban task as a dependency of the writer task.
  10. This is mandatory for Zico's task bundles.
  11. Writer task responsibilities:
  12. Update the public daily markdown.
  13. Avoid duplicates.
  14. Preserve newest-first ordering.
  15. Keep timestamps in CEST/CET.
  16. Publish/update the public Hermes WWW page for that day.
  17. If an internal mirror exists, keep it secondary and consistent.
  18. Reviewer task responsibilities:
  19. Verify the note is present.
  20. Verify only one public daily markdown exists for that date.
  21. Verify ordering and timestamp formatting.
  22. Verify the public URL returns success.
  23. Fix or block if something is wrong.
  24. Respond in chat with task IDs and concise status only.
  25. Keep the user free to dictate more notes immediately.

Daily Markdown Conventions

Recommended daily file pattern: - /home/vmubuntu/www/hermes/rekorder/YYYY-MM-DD.md

Recommended content shape:

# Rekordér — YYYY-MM-DD

Veřejný denní záznam hlasových poznámek z Discord vlákna **Rekordér**.

- Datum: YYYY-MM-DD
- Časové pásmo: Europe/Prague (CEST/CET)
- Řazení: nejnovější nahoře
- Aktualizováno: YYYY-MM-DD HH:MM:SS CEST

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

- Typ: hlasová poznámka / automatický transcript z mikrofonu
- Zdroj: Discord vlákno Rekordér

### Přepis

...text poznámky...

Transcript Cleanup Heuristics

Apply only low-risk corrections: - Convert obvious Czech STT damage into the intended Czech phrase when confidence is high. - Keep English technical names such as Dataverse, PowerShell, MacBook Pro, Mac mini, DMZ, Code with Claude when they clearly belong. - If a phrase is still ambiguous after cleanup, preserve a conservative wording instead of inventing specifics. - Treat odd word forms as likely Czech+English mixed dictation before assuming a different language.

Kanban Task Pattern

Create a pair of tasks per note:

  1. Writer task
  2. assignee: writer

  3. purpose: add/update the note in the daily markdown

  4. Reviewer task

  5. assignee: reviewer
  6. parent: writer task
  7. purpose: verification, fixup, URL check, final status wording

Use stable idempotency keys per note timestamp so retries do not create duplicates.

Pitfalls

  1. Handling the note synchronously before queueing it. Wrong for this workflow. Create tasks first so the user can continue dictating.

  2. Treating microphone transcript text as different from a voice note. For Rekordér, both are the same class of input.

  3. Creating more than one public markdown per day. The requirement is one daily page, incrementally updated.

  4. Keeping raw STT noise when the intended Czech+English meaning is obvious. Light normalization is part of the workflow.

  5. Over-correcting uncertain text into fabricated meaning. When uncertain, stay conservative.

  6. Forgetting the final verification/fixup task. Zico expects a verification stage, not just a producer task.

  7. Using an unhealthy board and silently assuming tasks will run. If a board dispatcher is unhealthy, switch to a working board and say so briefly.

Verification Checklist