Claude, Listener Creator.
Claude's listener-creator skill writes a file naming one condition, not a live watcher, so it fires reliably on exact matches and stays silent on anything else.
It's a reasonable assumption to make: if you ask Claude to flag and forward certain emails, something must be running in the background, constantly scanning your inbox. It isn't. The listener-creator skill reveals something more specific, and more limited, about how a Claude Skill actually works.
A folder, not a watcher
Open the listener-creator skill and there's no watcher process running anywhere. There are just two things: a SKILL.md file, about nine kilobytes of plain text, and a templates folder sitting beside it. Claude reads SKILL.md before it acts, then writes back a listener definition based on what it finds there. The instruction set is the file itself, not a background process quietly running on your account.
Steps, read top to bottom
Inside SKILL.md is a Steps section that Claude works through in order: read the request, write the condition, return the definition. Ask for a listener that flags any email from your boss marked urgent and forwards it immediately, and listener-creator writes exactly that condition into a file. From that point on, whenever a new email matches both boss and urgent, the same forward fires, every time, because the condition written into the file doesn't change on its own.
Reliable, and precisely bounded
That fixed condition is exactly what makes a listener reliable, and exactly what limits it. Because the rule never drifts, every email from your boss marked urgent forwards the same way, consistently. But an equally urgent email from a client never triggers it, because "client" was simply never written into the condition in the first place. A listener matches the literal words stored in its file, not a judgment call about how urgent a given email actually feels. It's a file naming one condition, firing on exactly that condition every time, and staying silent on anything that only resembles it.
Key takeaways
- A Claude Skill listener is a file describing one condition, not a live process monitoring your inbox.
- The listener-creator skill itself is just two files: a
SKILL.mdinstruction set and a templates folder. - Claude works through a fixed Steps section: read the request, write the condition, return the definition.
- A listener's reliability comes from its condition never changing on its own, which is also its limitation, since it only matches what was actually written into the file.
Try it yourself
Ask Claude: "I want a listener that flags any email mentioning a contract renewal and forwards it to my legal team. Read the listener-creator skill and walk me through what you'll do before you do it, show me exactly which condition you're writing into the file." Watching Claude name the condition before writing it is a direct way to see the Steps section working on your own request, narrated by Liam, in for Bear, as part of Humanitarians AI's Claude Basics series.
Chapters
Full transcript(auto-generated, with timestamps)
A Skill must be some live watcher scanning my inbox. Is that it?
[0:00]Someone assumes a skill is a live watcher scanning your inbox in real time. It isn't. It's a template Claude fills in, a file describing conditions to match later. So, what does listener creator actually build? Open the folder
A folder, not a watcher
[0:13]And there's no watcher running, just a skill. md file about 9 kilobytes in a templates folder beside it. Two files. This one is listener creator. Claude reads skill.md before it acts, then writes back a listener definition. The file is the instruction set, not a process running in the background. Inside skill.md is a step section. Work
Steps, top to bottom — the anchor
[0:32]Top to bottom. Read the request, write the condition, return the definition. Ask for listener that flags any email from your boss marked urgent and forwards it right away, and listener creator writes exactly that condition into a file. From then on, whenever a new email matches boss and urgent, the same forward fires. That's why it's
Reliable — then out of scope
[0:49]Reliable. The condition in the file doesn't change, so every email from your boss marked urgent forwards the same way. But an equally urgent email from a client never fires it, because client was never written into the condition. The listener matches the words in the file, not how urgent the email actually is. A listener isn't a watcher hovering over your inbox. It's a file naming one condition, and it fires on exactly that condition every time, and stays silent on anything that only feels the same. Your turn. Here's the prompt. Read it with me. I want a listener that flags
Carry-out
[1:20]Any email mentioning a contract renewal and forwards it to my legal team. Read the listener creator skill and walk me through what you'll do before you do it. Show me exactly which condition you're writing into the file. Liam in for bear. Claude listener creator, Liam in for
Your turn
[1:34]Bear.
More from Claude
1:42Why wrapping the same text in XML changes the answer Claude gives
1:27Claude, Executive Briefing.
1:50Why the server hands back an encrypted context you're only going to echo
1:53Why partial JSON can be a valid object before the closing brace arrives
4:12Claude, Closing — Do You Have to Be a Salesperson to Use the Sales Plugin?
3:39