{"id":68229,"plugin_id":"plugin_asdk_app_6ad03038d02c819197530d0e644693f7","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-28T13:13:12.827Z","digest":"9f8cc63340461a36c38983618ed5ff47aca804e6fad7d6f8790b4abaa4c7860c","against":null,"payload":{"description":"Explain numeric five-field cron and calculate upcoming runs from an explicit reference timestamp and IANA timezone.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":425}],"name":"cron-explorer","skill_md_contents":"---\nname: cron-explorer\ndescription: Explain numeric five-field cron and calculate upcoming runs from an explicit reference timestamp and IANA timezone.\n---\nCall `explore_cron` with `expression`, `timezone`, `reference`, and optionally `count` (default 5, maximum 20). Supply the timezone and timestamp explicitly; do not infer them. Timestamp includes seconds and Z or an offset. Runs are strictly after the reference.\nSupported fields: minute, hour, day-of-month, month, day-of-week. Numeric wildcards, lists, ascending ranges, steps; Sunday 0 or 7. A number with a step runs from that number to the field maximum. If either day field begins with `*`, both must match; otherwise day-of-month OR day-of-week suffices (Vixie cron behavior). This distinction also applies to `*/steps`.\nDST policy skips nonexistent wall times and includes both repeated instants, showing offsets. Other schedulers may behave differently. Search stops after 1,830 days and reports partial results. Reference years 1970–2095. No names, macros, seconds, years, ?, L, W, #, commands, execution, installation, or monitoring.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}