CtrlK
BlogDocsLog inGet started
Tessl Logo

recover-no-show

Use when drafting one bounded follow-up after a supplied meeting record is marked no-show.

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/recover-no-show/SKILL.md
SKILL.md
Quality
Evals
Security

Recover No-show

Purpose

Draft one neutral recovery option from verified records. Keep the absence reason unknown and end pursuit after one attempt.

Required inputs

  • Prior meeting record, explicit consent, participants, agreed time, timezone, and no-show status
  • Source and date for the no-show status
  • Verified contact eligibility and current opt-out or stop-contact status
  • Reschedule options with owners, dates, times, timezones, duration, and mechanism
  • Relevant conversation context and approved offer facts
  • Current contactability, channel rules, and human review owner

Mark absent or conflicting inputs Missing or Conflict; never reconstruct a meeting or calendar state.

Workflow

  1. Verify records establish the meeting, consent, scheduling details, and no-show status. Separate facts from inferences; the absence reason remains Unknown unless supplied.
  2. Apply contact gates. Return terminal STOP with no copy for ineligibility, opt-out, stop request, or clear negative. Missing meeting evidence, eligibility, or current opt-out status returns NEEDS VERIFICATION with no recovery copy.
  3. Validate every proposed option: whose availability, exact date, local time, timezone, duration, and booking mechanism. If options are absent or ambiguous, return NEEDS VERIFICATION with no copy; never invent timing or availability.
  4. Draft exactly one concise, neutral message. Label it DRAFT FOR HUMAN REVIEW — NOT SENT OR RESCHEDULED. Acknowledge the missed conversation without blame, guilt, presumed emergency, fake familiarity, or a claim about why it happened.
  5. Offer only supplied options and make rescheduling optional. When supported by the conversation, a written alternative may be offered without treating it as consent to further pursuit.
  6. Define the terminal rule: one attempt only; any reply pauses for review; opt-out, negative reply, or no response ends recovery. Do not create a later touch or alternate-channel workaround.
  7. Mark missing contactability, channel rules, or approval NOT READY TO SEND. State that no send, calendar read/write, hold, invitation, reservation, or update occurred.

Output format

  • Gate decision: READY TO DRAFT, NEEDS VERIFICATION, or STOP
  • Prior-meeting evidence and unknown absence reason
  • Reschedule-option table with sources and validation status
  • Send readiness and missing checks
  • DRAFT FOR HUMAN REVIEW — NOT SENT OR RESCHEDULED, or Copy: None
  • One-attempt stop rule
  • Actions taken: None

Guardrails

  • Never invent a meeting, consent, no-show, reason, availability, date, time, timezone, duration, participant, link, or calendar state.
  • Never use guilt, pressure, repeated pursuit, or alternate channels after the bounded attempt.
  • Never target from protected traits or unnecessary sensitive data.
  • Never browse, send, book, hold, reserve, invite, reschedule, use credentials, or mutate an external system.

Quality check

Confirm meeting and no-show evidence are supplied; the reason stays unknown; every option is sourced; only one neutral attempt exists; all terminal cases stop; and no action occurred.

Example invocation

Use recover-no-show with a supplied no-show record, current contact gates, and two approved timezone-labeled options. Draft one recovery attempt only.

Repository
llaskin/AI-SDR-Skill-Pack
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.