Навыки cron-schedule-planner

📦

cron-schedule-planner

Name: cron-schedule-planner
Author: dboeckli

Ревизия содержимого r1 Средний риск ⚙️ Внешние команды📁 Доступ к файловой системе

Plan GitHub Actions Cron Schedules

Scheduled workflows can collide and increase runner contention. This skill maps cron activity and suggests less crowded times for resource-intensive jobs.

Поддерживает: Claude Codex Code(CC)

📊 71 Адекватно

Maintain this Skill? Claim it 📊 71 Адекватно

Установить с помощью моего Агента

Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.

Запрос агента

Review the Skillstore skill "cron-schedule-planner" from https://skillstore.io/skills/dboeckli-cron-schedule-planner.md and its manifest at https://skillstore.io/api/skills/dboeckli-cron-schedule-planner/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.

Ресурсы для AI-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

Markdown-детали GET /skills/dboeckli-cron-schedule-planner.md Подписанный manifest GET /api/skills/dboeckli-cron-schedule-planner/manifest Подписанный lockfile GET /api/skills/dboeckli-cron-schedule-planner/lockfile

Протестировать

Использование «cron-schedule-planner». Do our nightly workflows collide?

Ожидаемый результат:

The report finds three scheduled runs at 02:00 UTC. Two are high-intensity container builds, making this the primary collision window.

Использование «cron-schedule-planner». When should the integration build run?

Ожидаемый результат:

Move the integration build to an empty UTC hour identified by the report. Review daylight-saving effects before applying the change.

Использование «cron-schedule-planner». Are queue delays concentrated at specific times?

Ожидаемый результат:

Recent runs show the highest average queue delay during one crowded hour. The suggested alternatives have lower observed delays and no scheduled entries.

Аудит безопасности

Средний риск

v1 • 26.09.2026 Открыть версионный отчет

All 98 static alerts are false positives caused by comments, Markdown backticks, escaped formatting, expected command substitution, and benign file handling. Commands use quoted arguments and support the documented read-only analysis. One medium contextual risk remains because repository-controlled values are written unescaped into an agent-facing Markdown report.

Просканировано файлов

697

Проанализировано строк

Пункты проверки

Ложные срабатывания проигнорированы

Подтверждённые проблемы безопасности (1)

Средний

scripts/cron-schedule-planner.sh:231 scripts/cron-schedule-planner.sh:418

Unescaped Remote Data in Agent-Facing Report

Remote workflow names and cron text are inserted into Markdown without escaping. A crafted repository value could alter report structure or inject instructions when an agent summarizes it.

The script retrieves repository-controlled workflow content and writes derived values directly into Markdown. The downstream instructions explicitly ask an agent to summarize that report.

Факторы риска

⚙️ Внешние команды (50)

📁 Доступ к файловой системе (19)

Аудитор:: codex

Поделиться и цитировать этот отчет

Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.

Открыть версионный отчет

Копировать ссылку на отчёт

https://skillstore.io/skills/dboeckli-cron-schedule-planner/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Значок Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/dboeckli-cron-schedule-planner/security.svg)](https://skillstore.io/skills/dboeckli-cron-schedule-planner?utm_source=security_passport_badge)

Значок HTML

<a href="https://skillstore.io/skills/dboeckli-cron-schedule-planner?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dboeckli-cron-schedule-planner/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Встраиваемая карточка

<iframe src="https://skillstore.io/embed/skills/dboeckli-cron-schedule-planner.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Академические ссылки (APA · BibTeX · CFF)

Цитата APA

dboeckli. (2026). cron-schedule-planner security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dboeckli-cron-schedule-planner/audits/1

Цитата BibTeX

@techreport{dboeckli-dboeckli-cron-schedule-planner-2026,
  author = {dboeckli},
  title = {cron-schedule-planner security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/dboeckli-cron-schedule-planner/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "cron-schedule-planner security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "dboeckli"
date-released: "2026-09-26"
url: "https://skillstore.io/skills/dboeckli-cron-schedule-planner/audits/1"
identifiers:
  - type: other
    value: "skillstore:dboeckli-cron-schedule-planner:audit:1"
    description: "Skillstore immutable audit report identifier"

Оценка Skillstore

Почему такая оценка Достоверность доказательств: Средний

Архитектура

Сопровождаемость

Контент

Сообщество

Соответствие спецификации

Что вы можете построить

Reduce CI schedule collisions

Review scheduled workflows across an organization and move demanding jobs away from crowded hours.

Coordinate repository maintenance

Compare nightly builds, dependency updates, and validation jobs before choosing a new schedule.

Review runner contention

Combine schedule density with recent queue times to identify practical execution windows.

Попробуйте эти промпты

Check one repository

Analyze scheduled workflows in owner/repository and show their UTC and Europe/Zurich times.

Find organization collisions

Scan repositories owned by organization and identify crowded UTC hours and high-intensity workflows.

Choose a better build time

Find a less crowded hour for the Testcontainers workflow and explain the proposed schedule change.

Use queue evidence

Analyze organization schedules with recent queue statistics, rank alternative hours, and present changes for approval without editing workflows.

Лучшие практики

Use explicit repository scope when only selected projects should be analyzed.
Review suggested times against business deadlines and daylight-saving changes.
Confirm every workflow edit after inspecting the generated report and proposed difference.