Yes. Oyma allows you to create an unlimited library of custom prompt templates. You can define exact formatting rules, section headers, and output conventions using standard Markdown prompts.
Tailoring Synthesis to Your Organization
Standard corporate summaries rarely fit every team: engineering managers require granular Jira-ready task tickets, venture capitalists need founder valuation signals, and medical researchers need clinical protocol observations.
Oyma allows you to create an unlimited library of custom prompt templates.
Authoring a Custom Template
In Preferences > Summary Templates, you can define custom prompt instructions:
Analyze the meeting transcript and produce the following sections:
1. Executive Decision Log (Numbered list of irreversible decisions).
2. Blockers & Technical Debt (Specific engineering risks mentioned).
3. Jira Task Backlog (Formatted as "- [ ] [Owner]: [Action]").
Output in clean, valid CommonMark.
Your custom templates appear in the summary dropdown menu and execute seamlessly across both local Ollama models and cloud BYOK providers.
Utilizing Dynamic Template Variables
You can inject dynamic context variables into your prompt templates:
{{transcript}}: The complete verbatim speech-to-text transcript.{{note_title}}: The title of the current meeting document.{{date}}: Today’s date in YYYY-MM-DD format.{{attendees}}: List of participants detected or manually tagged in the note.
+-----------------------------------------------------------+
| Custom Template: [Sprint Retrospective] |
| |
| Prompt Instructions: |
| "Given the following transcript for {{note_title}}: |
| 1. What went well? |
| 2. What could be improved? |
| 3. Action items for next sprint." |
+-----------------------------------------------------------+
Sharing Templates Across Teams
Templates are saved as clean text files in your vault’s templates/prompts/ directory. You can share them with teammates via Git, ensuring your entire organization produces standardized, high-quality meeting minutes.
Prompt Engineering and Template Variables
Build powerful custom templates using flexible prompt variables:
{{transcript}}: Inserts the complete speech transcript.{{note_title}}: Inserts the active document title.{{date}}: Injects the current date.{{attendees}}: Pulls recognized participant names.
Save custom prompts as standard text files in your vault’s templates/prompts/ folder to share them across your team via Git.
Shareable Team Templates and Prompt Versioning
Custom prompt templates are saved as plain Markdown files in your vault. You can version-control and share them across your team with Git, ensuring consistent meeting documentation standards across your entire organization.
Templates support Markdown tables, task checkboxes, and custom heading hierarchies, allowing you to generate reports that match your organization’s exact formatting requirements.
Prompt Authoring Invariants and Testing Workflows
- Template Variables: Supports dynamic tags like
{{transcript}},{{note_title}},{{date}}, and{{attendees}}. - Storage Format: Stored as clean CommonMark files in your vault’s
templates/prompts/folder. - Team Collaboration: Version-control prompt templates with Git to ensure standardized meeting documentation.
- Provider Agnostic: Custom prompts execute identically on local Ollama models and cloud BYOK providers.
- Interactive Dry-Run: In Preferences, you can run candidate prompts against historical meeting transcripts to verify output schemas before saving.