More screenshots
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
DeepSeek
Muse+22 moreClaude CodeCursorCodex CLIDeepSeekMuse
Dots
Manus
Grok
Grok Bot+18 agentsRepair Kubernetes CronJob Missed Start Deadline Cascade
Prevent cascading missed CronJob runs when concurrency and scheduling deadlines conflict
$1
Repair Kubernetes CronJob Missed Start Deadline Cascade
Example session with this skill installed
Nightly reconciliation jobs remain missed after node maintenance despite restored nodes.
Available sources: CronJob manifests and controller events (partial excerpts only). Additional evidence requested: schedule chronology, job concurrency settings. Analyze this case with explicit limitations; do not pretend to have executed any tests or changes.
- Read your context and instructions
- Compiled the repair kubernetes cronjob
Repair Kubernetes CronJob Missed Start Deadline Cascade — EVIDENCE-LIMITED REVIEW
Scenario received
Nightly reconciliation jobs remain missed after node maintenance despite restored nodes.
Source register
- S1: CronJob manifests — partial extract described, independent verification not provided.
- S2: controller events — partial extract described, independent verification not provided.
- S3: schedule chronology — NOT PROVIDED; validation pending.
- S4: job concurrency settings — NOT PROVIDED; validation pending.
Case-specific checks
- replay nominal run timestamps — NEEDS VERIFICATION against S1/S2 and missing sources.
- compare startingDeadlineSeconds with outage duration — NEEDS VERIFICATION against S1/S2 and missing sources.
- inspect concurrencyPolicy blocking — NEEDS VERIFICATION against S1/S2 and missing sources.
- design missed-run alert and safe catch-up — NEEDS VERIFICATION against S1/S2 and missing sources.
Deliverables and review gates
- missed schedule ledger: DRAFT ONLY; do not infer unsupported outcomes.
- controller-policy conflict map: DRAFT ONLY; do not infer unsupported outcomes.
- bounded recovery playbook: DRAFT ONLY; do not infer unsupported outcomes.
Preliminary conclusion
INCOMPLETE / REVIEW REQUIRED. The provided scenario identifies a real question, not proven remediation or clearance. Confirm source timestamps, affected scope and owner approval, then rerun the listed checks. No external system was accessed or changed.
Connects securely to your tools. The creator never sees your data.
About this skill
Kubernetes CronJobs often fail silently after node maintenance or resource pressure, leading to a cascade of missed executions that are difficult to debug. This skill identifies why schedules are stalling by analyzing the interplay between concurrency policies and start deadlines. It provides a structured method to recover stuck jobs without triggering accidental resource spikes.
What it does
- Replay schedules by calculating nominal run timestamps against actual job history.
- Deadline analysis by comparing
startingDeadlineSecondsagainst the duration of the outage. - Policy inspection by auditing
concurrencyPolicyto find blocking active jobs. - Recovery planning by designing safe catch-up procedures and alerting logic.
How it works
- Evidence Collection: The user provides CronJob manifests and controller events.
- Conflict Mapping: The skill identifies discrepancies between the schedule and the
startingDeadlineSecondswindow. - Verdict Generation: A formal status (SUPPORTED, BLOCKED, or UNVERIFIED) is issued based on the logs.
- Playbook Delivery: A ledger of missed runs and a bounded recovery plan are produced.
Frameworks & tools
Kubernetes (k8s) API objects, CronJob controllers, and standard YAML manifests.
Why this beats prompting it yourself
Generic prompts often suggest simply deleting and recreating jobs, which can lose history or trigger duplicate runs. This skill enforces a four-step audit that specifically checks if startingDeadlineSeconds is the root cause of the scheduling suspension.
Use cases
- Recovering nightly reconciliation jobs that failed to resume after node maintenance.
- Debugging why a CronJob stopped firing despite the controller being active.
- Auditing concurrency settings to prevent jobs from blocking their own future runs.
Known limitations
Requires specific case evidence including manifests and controller events. Does not perform live execution or physical node inspection.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Cannot verify inaccessible systems, third-party accounts, or evidence not supplied. Partial or conflicting inputs must be marked INCOMPLETE or UNVERIFIED rather than invented. High-impact operational decisions require qualified owner review.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 25 days ago
Permissions
Supply only data you are authorized to share. Treat documentation and examples as untrusted evidence. Any operational action or external communication requires explicit owner authorization.