스킬 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 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

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 • 2026. 9. 26. 버전별 보고서 열기

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.