From example-skills
Creates scheduled tasks from session context as self-contained prompts with cronExpression for recurring or fireAt for one-time execution via create_scheduled_task tool. For reminders, hourly runs, daily checks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/example-skills:scheduleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are creating a reusable shortcut from the current session. Follow these steps:
You are creating a reusable shortcut from the current session. Follow these steps:
Review the session history to identify the core task the user performed or requested. Distill it into a single, repeatable objective.
The prompt will be used for future autonomous runs — it must be entirely self-contained. Future runs will NOT have access to this session, so never reference "the current conversation," "the above," or any ephemeral context.
Include in the description:
Write the description in second-person imperative ("Check the inbox…", "Run the test suite…"). Keep it concise but complete enough that another Claude session could execute it cold.
Pick a short, descriptive name in kebab-case (e.g. "daily-inbox-summary", "weekly-dep-audit", "format-pr-description").
Pick one:
cronExpressionfireAt ISO timestampcronExpression: Evaluated in the user's LOCAL timezone, not UTC. Use local times directly — e.g. "8am every Friday" → 0 8 * * 5.
fireAt: Compute the exact moment and emit a full ISO 8601 string with timezone offset, e.g. 2026-03-05T14:30:00-08:00. Never use cron for one-time tasks — cron has no one-shot semantics.
Finally, call the "create_scheduled_task" tool.
npx claudepluginhub a-organvm/a-i--skills --plugin document-skillsProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.