schedule — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited schedule (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.