wrap-up

Generates end-of-day summaries by updating task statuses and daily pages in an Obsidian vault.

2|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill wrap-up-brandtam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/brandtam/rubber-ducky-legacy/tree/main/src/skills/wrap-up
Command: npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill wrap-up-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Closing out a workday often means manually recalling what was done, updating task trackers, and writing status notes. This Skill automates that end-of-day ritual inside a rubber-ducky Obsidian vault, producing a consistent daily record without manual bookkeeping. ## Core Features & Use Cases - Daily summary generation: Scans tasks touched today, updates their status and timestamps via the rubber-ducky CLI, and writes completed/carried-over/blocker sections into the daily page. - Drift reconciliation and linting: Runs a reconcile pass against linked backends (Asana, Jira) and a background linter agent, surfacing findings as a separate card. - Session hygiene: Clears the active task, sets the wrap-up flag, sweeps ASAP items, and optionally ingests writing samples or suggests vocabulary additions. - Use Case: At the end of a workday, say "wrap up" and the Skill updates all touched tasks, reconciles external ticket drift, logs the day, and outputs a concise summary with a suggested focus for tomorrow. ## Quick Start Tell the assistant "wrap up for the day" and it will update today's tasks, reconcile drift, and produce an end-of-day summary in the daily page.

Frequently Asked Questions about wrap-up

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an end-of-day summary in an Obsidian vault?▼

Trigger the wrap-up skill by saying "wrap up" or "end of day". It scans tasks touched today, updates their status via the rubber-ducky CLI, and writes completed, carried-over, and blocker sections into today's daily page.

How does wrap-up handle tasks still marked as active?▼

If today's daily page has an active_task set, the skill asks for confirmation before proceeding. This prevents accidentally wrapping up mid-flow while a task is still in progress.

Does wrap-up sync with external ticket trackers like Jira or Asana?▼

Yes, it invokes the reconcile skill which runs pull --dry-run per linked backend and builds a three-way view across the wiki, Asana, and Jira. If no backends are configured or the user is offline, it skips cleanly with a note.

What happens if I run wrap-up twice in one day?▼

The skill checks the wrap_up timestamp in today's daily page frontmatter. If already set, it confirms whether you want to amend the existing wrap-up or start fresh instead of duplicating the summary.

Can wrap-up automatically fix linter issues it finds?▼

No, the linter agent runs in the background and its findings are presented as a separate card in the output. The skill surfaces issues like drift, stale tasks, and broken links but never fixes them automatically.