Generate auditable WCET upper bounds for real-time embedded tasks.
npx skills add https://github.com/robotijn/ctoc --skill wcet-budget
Please help me install this Agent Skill. Skill: wcet-budget Source: https://github.com/robotijn/ctoc/tree/main/skills/realtime/wcet-budget Command: npx skills add https://github.com/robotijn/ctoc --skill wcet-budget
Hard real-time embedded systems require provable, auditable worst-case execution time (WCET) bounds to meet safety-critical deadlines, pass regulatory certification, and avoid in-flight deadline misses that risk hardware safety and system reliability. Manual WCET estimation is error-prone, often underestimates bounds, and fails to account for microarchitectural effects like cache jitter and pipeline stalls.
Use the wcet-budget skill to analyze the worst-case execution time of all deadline-bearing real-time tasks in the current plan, validate their schedulability, and generate the compliant .ctoc/realtime/wcet/<plan-id>.yaml artifact for certification review.
High-intent search queries and answers about installing and using this skill.
To calculate provable WCET bounds for hard real-time embedded systems, you analyze task code with loop bound annotations and microarchitectural modeling to generate auditable upper bounds. This process accounts for cache jitter, pipeline stalls, and bus contention effects.
Yes, WCET analysis supports multicore platforms by enforcing Robust Time Partitioning through cache colouring, core pinning, and memory bandwidth quotas. This ensures calculated execution time bounds remain valid under realistic multicore bus contention.
To validate schedulability for ISO 26262 ASIL D tasks, you reconcile WCET bounds against declared per-task time budgets and run response-time analysis. This identifies unschedulable systems and verifies deadline compliance before deployment.
The best way to document worst-case execution time for DO-178C Level A certification is generating citation-backed WCET artifacts. These include documented safety margins, loop annotations, and Hardware-in-the-Loop corroboration for release gating.
Manual WCET estimation fails to account for cache jitter and pipeline stalls because it is error-prone and often underestimates bounds. It lacks automated microarchitectural modeling required to safely capture complex hardware contention effects.
claudcherejiAnalyze hardware specifications and generate firmware architecture proposals for embedded systems.
robotijnEnforce four-rung verification ladders for safety-critical embedded functions.
adobeConfigure and harden Adobe AEM Cloud Dispatcher and HTTPD configurations.
OpentronsStandardize and execute static deploy tasks for Python CLIs.
