Back to all skills
operationsVersion 1.1.015 minutes

Sponsor Follow-Up Assistant

Use this when the work is stuck in fragments: notes, deadlines, duplicates, owner comments, and half-finished drafts that need to become a usable workflow.

Why it is worth your emailYou get a clean operating pattern for turning messy local media inputs into structured output without losing private context or next actions.
sponsor-follow-up-assistant.zip1.1.0

Expected output

A structured working draft with duplicate handling, gaps, and next actions.
  • Inputs named before work starts
  • Assumptions separated from facts
  • Next human action made explicit

Use it when

  • You need to turn operational fragments into a clean, repeatable local media workflow.
  • You want the AI agent to normalize messy inputs without losing practical context.
  • You need output that can move straight into publishing, CRM, or internal follow-up review.

What you need before running it

Raw items, relationship context, deadlines, owner notes, and any required format.

Known duplicates, exclusions, and sensitive details.

The final channel where the output will be used.

What comes out

  • A structured working draft with duplicate handling, gaps, and next actions.
  • Internal notes separated from publishable or sendable language.
  • A short checklist for the operator to approve before use.

What’s in the package

SKILL.mdexamples/worked-example.mdreferences/quality-checks.mdtemplates/operator-worksheet.md

The archive also includes a manifest with version, checksum, compatibility, category, and package metadata.

Quality gates

  • Duplicates removed and gaps named.
  • Private information kept out of public-facing output.
  • Next human action is explicit.

Compatibility checked

Codex, Claude

Compatibility is published only after package structure and ordinary read-path checks.