スキル 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.