Run any Skill in Manus with one click

setup-automation

Stars1

Forks0

UpdatedApril 28, 2026 at 11:36

Stub — set up automatic recurring runs of wrapup and morning-brief via the user's preferred scheduler. Currently outlines options without configuring.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

danielrosehill

danielrosehill/Claude-Schedule-Manager-Plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	setup-automation
description	Stub — set up automatic recurring runs of wrapup and morning-brief via the user's preferred scheduler. Currently outlines options without configuring.

Setup Automation (stub)

This skill is a placeholder until tooling preferences are gathered. It documents the options and lets the user pick one to implement.

Options to surface

When invoked, walk the user through these choices:

systemd user timer — Linux native, no extra deps. Two unit files per cadence (timer + service).
cron — universal, simple, less observable.
KDE / GNOME scheduled task — desktop-integrated, fragile across reboots.
n8n workflow — if the user runs n8n. Cron node → exec node calling Claude Code in headless mode.
Home Assistant automation — if the user runs HA. Time trigger → shell_command service.
Claude Code's native scheduling — /schedule for one-time or recurring agent runs (cloud).

What NOT to do yet

Don't write systemd units or cron entries from this skill. Once the user picks an approach, scaffold the implementation in a follow-up (or hand off to the relevant plugin: homelab-private for HA/systemd, etc.).

Suggested cadence

morning-brief — weekday mornings, 07:00 local
wrapup — weekday evenings, 18:00 local; weekly variant Friday 17:00

Confirm cadence with the user before any future implementation step.

More from this repository

same repository

agenda

danielrosehill/Claude-Schedule-Manager-Plugin

Manage meeting agendas as Google Docs — create, link to a calendar event description, share with attendees, or email. One skill, four sub-actions.

2026-04-281

assign-dates

danielrosehill/Claude-Schedule-Manager-Plugin

Assign due dates to Todoist tasks in batch. Walks the user through each undated task and applies their choice.

2026-04-281

assign-priorities

danielrosehill/Claude-Schedule-Manager-Plugin

Assign priorities to Todoist tasks in batch. Walks the user through each unprioritised task and applies their choice.

2026-04-281

batch-create-events

danielrosehill/Claude-Schedule-Manager-Plugin

Create multiple Google Calendar events from a structured list. Resolves attendees once across the batch, confirms the table, then writes.

2026-04-281

batch-create-tasks

danielrosehill/Claude-Schedule-Manager-Plugin

Create multiple Todoist tasks from a structured list. Confirms the table, then writes serially.

2026-04-281

create-event

danielrosehill/Claude-Schedule-Manager-Plugin

Create a single Google Calendar event. Resolves attendees via the contacts MCP. Optionally links a Drive doc (agenda) into the description.

2026-04-281

name	setup-automation
description	Stub — set up automatic recurring runs of wrapup and morning-brief via the user's preferred scheduler. Currently outlines options without configuring.

Setup Automation (stub)

This skill is a placeholder until tooling preferences are gathered. It documents the options and lets the user pick one to implement.

Options to surface

When invoked, walk the user through these choices:

systemd user timer — Linux native, no extra deps. Two unit files per cadence (timer + service).
cron — universal, simple, less observable.
KDE / GNOME scheduled task — desktop-integrated, fragile across reboots.
n8n workflow — if the user runs n8n. Cron node → exec node calling Claude Code in headless mode.
Home Assistant automation — if the user runs HA. Time trigger → shell_command service.
Claude Code's native scheduling — /schedule for one-time or recurring agent runs (cloud).

What NOT to do yet

Don't write systemd units or cron entries from this skill. Once the user picks an approach, scaffold the implementation in a follow-up (or hand off to the relevant plugin: homelab-private for HA/systemd, etc.).

Suggested cadence

morning-brief — weekday mornings, 07:00 local
wrapup — weekday evenings, 18:00 local; weekly variant Friday 17:00

Confirm cadence with the user before any future implementation step.