Menu

Individual skill

auto-reply-is-not-a-reply

0upvotes

Use this skill when classifying inbound responses to outbound — out-of-office, vacation and parental-leave auto-responders, delivery notices, and other machine-generated mail that looks like engagement. Produces a triage decision that keeps the sequence alive, keeps the metrics clean, and reschedules the next touch to when the human is actually back.

skills/lucas-godtfredsen/auto-reply-is-not-a-reply/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
236
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

An out-of-office arrives in the same inbox, in the same thread, as a real
answer. Filed as one, it corrupts three things at once. This is how to file it.

## The play

1. **Classify machine mail as its own outcome**, alongside interested,
   question, referral, not now, not interested and unsubscribe. A triage
   vocabulary without this bucket does not skip the auto-responder — it files
   it under the nearest wrong label.
2. **Read the return date if the message states one; never infer one.** "Back
   on the 20th" is a date. "Away for a while" is not, and a guessed date is a
   send at the wrong time dressed as intelligence.
3. **Reschedule instead of advancing.** The touch was never spent: nobody read
   the message. Move the next one to one working day *after* they return —
Back to top