Skill

setup-automation

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

npx claudepluginhub danielrosehill/claude-code-plugins --plugin schedule-manager

Tool Access

This skill uses the workspace's default tool permissions.

Preview

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

SKILL.md

Similar Skills

using-superpowers

180.9k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Stars0

Forks0

Last CommitApr 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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.