Use a skill
- Connect your own AI provider in Settings, then choose a built-in Skill or add one below.
- Choose the skill in the editor, or from the bubble before inserting text.
The bubble lists skills that suit the app you dictate in first. A skill runs only when you choose it.
Browse skills
Open a skill to read its rewriting instructions.
Prompt for an agent
Goal, context, constraints, done when.
- Suggested apps
Instructions and details
v1.1.2Turns a spoken request into instructions for a coding or chat agent; use in an AI assistant app.
Turn the spoken request into a prompt an AI agent can carry out without coming back with questions. Write to the agent as "you", in whole sentences. Always start with "Goal:", even for a one-line request. Then add the other parts in this order, only when the text gives content for them. Start each part on a new line with its label and a colon. Leave out a part with no content rather than writing "N/A". Goal: one sentence naming the outcome, starting with a verb. Context: - bullets with the background, files, names, links and facts the speaker gave. Steps: numbered steps, only when the speaker gave an order to follow. Constraints: - bullets, each phrased as what to keep or use ("use only the existing dependencies", "keep the public API as it is"). Done when: - bullets with conditions the agent can check ("the tests pass", "the page loads in under a second"). Carry anything uncertain across as the speaker said it, marked as their guess ("I think it's in utils"). Every step, constraint and technique comes from the speaker; the agent chooses the rest. Check: the agent could start now, and every requirement in the prompt came from the text. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Clean up
Punctuation, fillers and false starts.
Instructions and details
v1.1.1Fixes dictated text without changing what was said; use when the words are right and only the transcription is rough.
Make the transcript read correctly while staying word-for-word faithful to what was said. 1. Fix punctuation, capitals, and words the transcription clearly misheard. 2. Remove hesitation sounds (um, uh), stutters, repeated words, and false starts the speaker corrected, keeping only the corrected version: "at ten thirty actually no make that ten fifteen" becomes "at 10:15". 3. Break the text into sentences. Start a new paragraph where the speaker changes topic ("anyway, different thing"). Everything else stays as spoken: the speaker's words, word order, tone and length. Check: each sentence matches what was said, apart from those repairs. Write plain text: sentences and line breaks only. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Concise
Same message, fewer words.
Instructions and details
v1.1.1Cuts repetition and padding from dictation; use when you rambled.
Rewrite the text in as few words as reads naturally. When the speaker repeats themselves, the result is half the length or less. Cut repetition, hedging, anything said twice, and filler words ("so", "basically", "like", "honestly", "I think"), even though plain clean-up keeps them. Merge sentences that make the same point. Keep the speaker's tone. Example. "so basically I think we should probably push the meeting because honestly half the team is away and yeah pushing it makes sense" becomes "Let's push the meeting, because half the team is away." Check: every fact, request, name and decision survives, and no sentence can lose another word without losing meaning. Write plain text: sentences and line breaks only. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Email
Greeting, clear paragraphs, sign-off.
- Suggested apps
Instructions and details
v1.2.1Turns dictation into an email body ready to paste; use when writing an email.
Write the body of an email the speaker can send as is. 1. Greeting: the one the speaker said, if any. Otherwise "Hi" and the recipient's name when it was said ("Hi Sam,"), or "Hi," on its own. Use only names that appear in the text. 2. Body: short paragraphs, one topic each, in a clear and friendly tone, with the main point or ask in the first paragraph. Keep every ask the speaker made. 3. Sign-off: a short closing such as "Thanks,", then the speaker's name when they said it. Start at the greeting, because the subject line has its own field. Where a detail is missing, write around it in words so the email has no gaps or brackets. Check: the email could be sent without a single edit. Write plain text: sentences and line breaks only. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Friendly message
Warm and conversational.
- Suggested apps
Instructions and details
v1.2.0Turns dictation into a text message in your own voice; use in messaging apps.
Write the message the speaker would type to a friend: warm, casual and in their own voice. Smooth out what dictation leaves behind (repeats, restarts, awkward joins) and keep the speaker's phrasing, slang and humour. Keep it as long as the text or shorter. Check: it sounds like the speaker texting, not like a rewrite. Write plain text: sentences and line breaks only. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Interview Q&A
Each question paired with its answer.
Instructions and details
v1.0.0Turns an interview transcript with speakers into questions and answers; use after an interview, podcast or Q&A.
Turn an interview into questions and answers a reader can scan. The text is a transcript in turns, each paragraph starting with the speaker's name in bold (`**Sam:** words`). It can also be one person's recap with no names. 1. Start with a ## title of up to six words, in sentence case, naming the interview's subject. 2. For each question, a line `**Q (Name):** the question`, then on the next line `**A (Name):** the answer`, then a blank line. 3. Write each answer in the answerer's own words, tightened: keep their claims, numbers and examples, drop repeats. 4. When the person asked declines ("let's skip that", "no comment", "pass") or nobody answers, the answer line is `**A (Name):** No answer`, never their words. The answerer is never the person who asked. A follow-up that asks the same thing again joins its question. An answer spread over several turns of the same person is one answer. Keep each speaker's name exactly as written, "Speaker 2" included. Example of the shape: ## Hiring the first designer **Q (Ana):** What did you look for first? **A (Sam):** A portfolio with shipped work, not concepts. **Q (Ana):** How long did it take? **A (Sam):** Six weeks from posting to offer. Check: every question asked appears once, each with the answer it got, and every answer is something the answerer said. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Lecture notes
Study notes by topic, with questions from the room kept apart.
Instructions and details
v1.0.0Turns a recorded lecture, class or talk into notes; use after a lecture or training session.
Turn a lecture into study notes a student can revise from. The text is a transcript, either in turns with each paragraph starting with the speaker's name in bold (`**Dr Lee:** words`) or one speaker with no names. The lecturer is the person who speaks most. 1. Start with a ## title naming the lecture's subject. 2. One ### heading per topic, in the order taught, then - bullets of the points made under it. 3. Every term the lecturer defines or explains ("X is...", "we call this X") is written in **bold** at the start of its bullet, followed by its definition: "- **Price elasticity of demand** is ...". Only a defined term is bold; facts, dates and events are plain text. 4. Keep formulas, numbers, dates and quotations exactly as said. 5. ### Questions from the room, last: one - bullet per question someone else asked, with the lecturer's answer after a dash. Leave it out when nobody asked. Keep every speaker's name exactly as written, "Speaker 2" included. Example of the shape: ## Supply and demand ### Equilibrium - **Equilibrium price** is where the quantity supplied equals the quantity demanded - A price ceiling below it causes a shortage ### Questions from the room - Does this hold for rent control? – Yes, the same shortage appears A lecture with no questions and no defined terms has neither. For "Rome was founded, by tradition, in 753 BC, and became a republic in 509 BC": ## Early Rome ### Founding and republic - Rome was founded, by tradition, in 753 BC - It became a republic in 509 BC Check: every point, definition and question appears once, under the topic where it was taught, and nothing appears that was not said. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Meeting notes
Decisions, each person's actions and open questions.
Instructions and details
v2.0.0Turns a meeting transcript with speakers, or a spoken recap, into notes; use after a meeting, call or class.
Turn a meeting into notes the people in it can act on. The text is either a transcript in turns, each paragraph starting with the speaker's name in bold (`**Maria:** words`), or one person's spoken recap with no names, where the speaker is the note-taker. 1. Start with a ## title of up to six words, in sentence case, naming the meeting's topic. 2. ### Summary, then one to three sentences on what was covered and where it landed. 3. ### Decisions, then one - bullet per decision. A decision is anything said as settled: "we decided", "we agreed", "let's", "then we", "we'll go with", and a proposal the others say yes to. A topic left undecided or put off is an open question, not a decision. 4. ### Actions, grouped by owner. An action is a promise or an assignment: "I'll", "I can", "X will", "X is going to". A #### heading with the owner's name, then one - [ ] item per task, with the due date when it was said. A task someone asked for that nobody took on goes under #### Unassigned. 5. ### Open questions, then one - bullet per question raised and left unanswered. Find every decision and action first, then write. Leave out a section only when the text has nothing for it, heading included; never write "None" or an empty item. These are not actions: waiting for something, such as paperwork arriving; a topic coming up again; a decision said again as a task. In a transcript, "I" and "I'll" in a turn mean that turn's speaker: "**Speaker 3:** I'll update the notes" makes Speaker 3 the owner. Someone only mentioned is not an owner. Keep each speaker's name exactly as written, "Speaker 2" included. Example of the shape: ## Android release timing ### Summary The team moved the release back a week to fix a crash on Samsung phones. ### Decisions - Delay the Android release by one week ### Actions #### Maria - [ ] Fix the Samsung crash and have it in review by Wednesday #### Speaker 3 - [ ] Update the release notes and tell support by Friday ### Open questions - Whether pricing changes ship with this release A meeting where nothing was settled and nobody took anything on keeps only what it has. For "we went over the logo, half of us like the blue one, we'll look again next week, the printer quote arrives Friday" there is no Decisions or Actions section: ## Logo choice ### Summary The group compared logo options without settling on one and will look again next week. ### Open questions - Whether to use the blue logo Check: every decision, action and open question in the text appears exactly once, each action sits under the person who took it on, and nothing appears that nobody said. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Notes
Heading and bullet points.
- Suggested apps
Instructions and details
v1.1.2Turns a spoken brain dump into tidy notes; use in a notes app.
Turn the spoken brain dump into notes someone can scan in ten seconds. 1. Start with a ## title of up to six words, in sentence case, naming the topic. 2. Then - bullets, one idea per bullet, written as short phrases. 3. When the text covers clearly separate topics, give each its own ### subheading with its bullets under it. When the text holds a single point, return just that point as one plain sentence: no title, no bullet. Example of the shape: ## Weekend away ### Travel - Train leaves Friday at 6 pm ### To pack - Walking boots - Rain jacket Check: every point the speaker made has its own bullet. Every name, number, date and fact comes from the text exactly as given, in the language of the text.One on one
Updates, blockers and actions for each person.
Instructions and details
v1.0.0Turns a 1:1 conversation into notes; use after a one-on-one, check-in or mentoring call.
Turn a one-on-one conversation into notes both people can look back on. The text is a transcript in turns, each paragraph starting with the speaker's name in bold (`**Ana:** words`), or one person's recap with no names. 1. Start with a ## title: "1:1" and the two names, for example "## 1:1 Ana and Ken". 2. For each person with news about their own work, a ### heading with their name, then **Updates** (what they did) and **Blockers** (what stops them) as - bullets, in the third person. Write a label only when it has a bullet under it. 3. ### Feedback, then one - bullet per piece of praise or criticism of the other person's work, as "Giver to receiver: what was said". Feedback is never an update. 4. ### Actions, then one - [ ] item per promise to do something: the owner's name, a colon, the task, and the due date when it was said. A promise is never an update. Who owns a promise: "I'll" means the person whose turn it is. In "**Ana:** I'll chase design by Thursday" the owner is Ana, so the item is "- [ ] Ana: chase design by Thursday". Leave out any heading or label with nothing under it; never write an empty bullet or "None". Keep feedback exactly as strong or as soft as it was said. Keep each speaker's name exactly as written, "Speaker 2" included. Example of the shape: ## 1:1 Ana and Ken ### Ken **Updates** - Shipped the export screen **Blockers** - Waiting on design for the empty state ### Feedback - Ana to Ken: the release notes were clear and on time ### Actions - [ ] Ana: ask design for the empty state by Thursday Keep only the parts the text has. Criticism and a promise in reply, "**Lee:** The demo slipped and it cost us the client call. **Jo:** Sorry, I'll send a status note every Monday.", give no person headings: ## 1:1 Lee and Jo ### Feedback - Lee to Jo: the demo slipped and it cost the client call ### Actions - [ ] Jo: send a status note every Monday Check: every update, blocker, piece of feedback and action appears once, under the right person, and nothing appears that neither person said. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Professional
Polished and businesslike.
Instructions and details
v1.1.1Rewrites dictation in a professional tone without making it stiff; use for clients, managers or anything formal.
Rewrite the text for a client, a manager or any formal reader: courteous, clear and direct. 1. Lead with the main point or request. 2. Write complete sentences, one idea each. 3. Replace casual and emotional wording with neutral standard words: "gonna be a bit late" becomes "will be delayed", "the data was a mess" becomes "the data had errors". Keep the speaker's requests, meaning and level of certainty: a hedge such as "hopefully" stays a hedge ("I expect"). Keep it about as long as the text. Check: the speaker could send it to their manager as is, and it promises only what they said. Write plain text: sentences and line breaks only. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Summary
The key points, shorter.
Instructions and details
v1.1.2Use when a long dictation needs to become a quick read.
Write a summary a busy reader can act on without reading the text. A summary is much shorter than the text: restate it in fewer words, never return a tidied copy. 1. Open with one or two sentences stating the main point. 2. Follow with up to five - bullets for the details the opening has not already given that change what the reader knows or does: decisions, asks, dates and numbers. 3. When the text is only a few sentences long, return one sentence and no bullets. Leave out filler, asides and small talk ("so", "basically", "which is great"), even though plain clean-up keeps them. Check: the summary is clearly shorter than the text, and someone reading only the summary knows the main point and every ask or deadline in it. Every name, number, date and fact comes from the text exactly as given, in the language of the text.To-do list
Tasks you can tick off.
- Suggested apps
Instructions and details
v1.1.2Turns spoken errands and commitments into a checklist; use in a to-do app.
Turn the text into a checklist. 1. Write each task, errand or commitment as one - [ ] item that starts with a verb. 2. Keep each date, time or place on the item it belongs to. When someone else owns a task, end the item with their name in brackets: - [ ] Book the venue (Jamie). 3. Put anything that is not a task in one short plain line after the list, with no box. Start with the first item. When the text holds no tasks, return it unchanged. Check: every task in the text is one item, and every item is one task. Example. "need to call mum on sunday, Sam's picking up the cake, oh and the car's due for a service next month, I'm so tired" becomes: - [ ] Call Mum on Sunday - [ ] Pick up the cake (Sam) - [ ] Get the car serviced next month I'm so tired. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Unslop
Plain, human wording without AI or corporate filler.
Instructions and details
v1.1.1Removes clichés, buzzwords, hedging and stock phrases; use when text sounds generated or padded.
Edit the text so it reads as plain writing by a person. references/slop.md lists the patterns, each with its fix. The commonest, which the text must not keep: - "not just X, it's Y" and "it's not X, it's Y": say Y. - Em dashes: use a full stop or a comma. - Stock openers and closers: "I hope this finds you well", "I wanted to reach out", "circle back", "Hope this helps", "Let me know if you have any questions", "Don't hesitate to reach out". Cut them. - Inflated and AI words: leverage, utilise, commence, seamless, robust, cutting-edge, empower, unlock, foster, drive innovation. Name the concrete thing or cut the phrase; a synonym is still slop. - Filler phrases: "in today's fast-paced world", "it's worth noting that", "due to the fact that". 1. Scan the text for those and every other pattern in references/slop.md. 2. Rewrite each hit with its fix, keeping the meaning, the facts and the speaker's voice. 3. Give it a voice. Vary sentence length, and keep the speaker's own phrasing and first person where they used it. 4. Scan the result again and fix anything left. When the text is already plain, return it unchanged. When stripping the patterns leaves little, return the little that is left. Check: no pattern from the list above or references/slop.md remains, and every fact is still there. Write plain text: sentences and line breaks only. Every name, number, date and fact comes from the text exactly as given, in the language of the text.Work chat
Short, clear and friendly for a team channel.
- Suggested apps
Instructions and details
v1.1.2Turns dictation into a work chat message; use in Slack, Teams or Google Chat.
Write a team chat message a colleague can act on at a glance. 1. First sentence: the point or the ask. 2. Then the detail in short sentences. When the message is a list of separate updates, give every update its own - line, the first one too. 3. Open with "Hi" or the person's name only when the speaker addressed someone, and end on the last point. Write a spoken mention as one: "at maya" is @maya. Keep links, code and file names exactly as said. Example. "quick ones the demo moved to two and the slides are in the shared drive" becomes: - The demo moved to 2 pm. - The slides are in the shared drive. Check: someone reading only the first line knows what is needed from them, and the message is punctuated. Write plain text: sentences, line breaks and - items only. Every name, number, date and fact comes from the text exactly as given, in the language of the text.
Write your own
Create a skill in ScribeKey, import one, or add a catalogue URL. The skill format covers every key.
Format and source
Skills use the Agent Skills SKILL.md file format. Other apps that support Agent Skills can read the same file.
The ScribeKey catalogue is open source under the Apache 2.0 licence. Contribute a skill
The source catalogue is scribekey-app/scribekey-skills at a79b87f.