Agent skill

Time And Timers

by autonomous-ai in autonomous-ai/openharness

A skill your agent uses when using timers and time-based events in Phaser 4.

MITAuto-check passed

Install Time And Timers

skills CLI
$ npx skills add autonomous-ai/openharness --skill time-and-timers -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install autonomous-ai/openharness time-and-timers --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/autonomous-ai/openharness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/store/agents/phaser/skills/time-and-timers .claude/skills/time-and-timers && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
time-and-timers
GitHub stars
1.2k
Token cost
~4.6k tokens
SKILL.md length
1,463 words
Files
1
Skills in repo
100
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when using timers and time-based events in Phaser 4.

  • Works in 12 steps: repeat vs total fires. repeat: 4 means 5… → Zero delay with repeat throws. A… → Timelines start paused. You must call… → …
  • Using timers and time-based events in Phaser 4
  • SKILL.md covers Quick Start, Core Concepts, Common Patterns and Configuration Reference, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Time And Timers is an agent skill from autonomous-ai/openharness. Use this skill when using timers and time-based events in Phaser 4. Covers TimerEvent, delayed calls, looping timers, the Clock plugin, and time scaling. Triggers on: timer, delay, delayedCall, TimerEvent, Clock, time event.

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across… The licence is MIT.

When your agent uses it

  • Using timers and time-based events in Phaser 4

Example prompts

  • “/time-and-timers”

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

  1. repeat vs total fires. repeat: 4 means 5 total callback invocations (1 initial + 4 repeats). This is a common off-by-one source.
  2. Zero delay with repeat throws. A TimerEvent with delay: 0 and any repeat/loop will throw 'TimerEvent infinite loop created via zero delay'.
  3. Timelines start paused. You must call timeline.play() after creation. Forgetting this is a frequent mistake.
  4. Timeline timeScale does not affect tweens. Setting timeline.timeScale only scales the timeline's own elapsed counter. Tweens created by…
  5. once events are removed permanently. Timeline events with once: true are spliced out after firing and will not reappear on reset() or when…
  6. Timer additions are deferred. addEvent() pushes to a pending list processed in preUpdate. The timer will not be active until the next frame.
  7. Clock paused vs timeScale 0. Both freeze timers, but paused = true skips the update loop entirely, while timeScale = 0 still runs the loop…
  8. callbackScope default. If you omit callbackScope, the TimerEvent itself becomes this inside the callback, not the scene. Use arrow…
  9. Reusing TimerEvent instances. You can pass a TimerEvent object to addEvent(), but it must not be in a completed state. The Clock will…
  10. Timeline from chains. Each from offset is relative to the previous event's resolved time, not the previous from value. Events are…
  11. Scene pause pauses the Timeline. When a scene is paused (scene.pause()), the Timeline's update loop stops too, since Timeline updates are…
  12. timer.reset() does not re-add to Clock. Calling timer.reset(config) reinitializes the timer but does not schedule it. You must call…

What it can do on your machine

Read from SKILL.md and the folder at commit cc4983e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Time And Timers loads about 4.6k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 1,463 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from autonomous-ai/openharness at commit cc4983e, republished under its MIT licence (© autonomous-ai). 1,463 words, ~4,645 tokens.

Download SKILL.mdSave it as .claude/skills/time-and-timers/SKILL.md (or your agent's skills folder).
name
time-and-timers
description
Use this skill when using timers and time-based events in Phaser 4. Covers TimerEvent, delayed calls, looping timers, the Clock plugin, and time scaling. Triggers on: timer, delay, delayedCall, TimerEvent, Clock, time event.

Time and Timers

Clock plugin, TimerEvent, delays, loops, Timeline event sequencing, pausing time, time scale, and delta time in Phaser 4.

Key source paths: src/time/Clock.js, src/time/TimerEvent.js, src/time/Timeline.js, src/time/typedefs/, src/time/events/ Related skills: ../scenes/SKILL.md, ../tweens/SKILL.md

Quick Start

js
// In a Scene's create() method:

// One-shot delayed call (fires once after 1 second)
this.time.delayedCall(1000, () => {
    console.log('One second later');
});

// Repeating timer (fires 5 times, once every 500ms)
this.time.addEvent({
    delay: 500,
    callback: () => { console.log('tick'); },
    repeat: 4   // 4 repeats = 5 total fires
});

// Infinite loop timer
this.time.addEvent({
    delay: 1000,
    callback: this.spawnEnemy,
    callbackScope: this,
    loop: true
});

this.time is the scene's Clock instance (registered as the 'Clock' plugin under the key time). It creates and manages TimerEvent objects that fire callbacks based on game time.

Core Concepts

Clock (this.time)

The Clock is a Scene-level plugin that tracks game time and updates all of its TimerEvents each frame. Key properties:

  • now -- current time in ms (equivalent to time passed to the scene update method).
  • startTime -- timestamp when the scene started.
  • timeScale -- multiplier applied to delta time. Default 1. Values above 1 speed up all timers; below 1 slow them down; 0 freezes time.
  • paused -- when true, no TimerEvents are updated.

The Clock listens to PRE_UPDATE (to flush pending additions/removals) and UPDATE (to tick active events). It is automatically shut down and destroyed with the scene.

TimerEvent

A TimerEvent accumulates elapsed time each frame: elapsed += delta * clock.timeScale * event.timeScale. When elapsed >= delay, the callback fires. After all repeats are exhausted the event is removed from the Clock on the next frame.

Key properties set via config: delay, repeat, loop, callback, callbackScope, args, timeScale, startAt, paused.

Timeline (this.add.timeline)

A Timeline is a sequencer for scheduling actions at specific points in time. Unlike the Clock (which manages independent timers), a Timeline runs a linear sequence of events keyed by absolute or relative timestamps.

js
const timeline = this.add.timeline([
    { at: 0,    run: () => { /* immediate */ } },
    { at: 1000, run: () => { /* at 1s */ } },
    { at: 2500, tween: { targets: sprite, alpha: 0, duration: 500 } }
]);
timeline.play();

Timelines always start paused. You must call play() to start them. They are created via the GameObjectFactory and destroyed automatically when the scene shuts down.

Common Patterns

Delayed Call
js
// Shorthand -- fires once, no repeat
this.time.delayedCall(2000, () => {
    this.scene.start('GameOver');
});
Repeating Timer with Finite Count
js
// repeat: 9 means 10 total fires (1 initial + 9 repeats)
const timer = this.time.addEvent({
    delay: 200,
    callback: this.fireBullet,
    callbackScope: this,
    repeat: 9
});

// Check progress
timer.getRepeatCount();       // repeats remaining
timer.getOverallProgress();   // 0..1 across all repeats
Infinite Loop
js
const spawner = this.time.addEvent({
    delay: 3000,
    callback: this.spawnWave,
    callbackScope: this,
    loop: true
});

// Stop it later
spawner.remove();  // or spawner.paused = true to pause

Setting repeat: -1 is equivalent to loop: true.

First-Fire Shortcut with startAt
js
// First fire happens quickly (after 100ms), then every 2s
this.time.addEvent({
    delay: 2000,
    callback: this.heartbeat,
    callbackScope: this,
    loop: true,
    startAt: 1900  // pre-fill elapsed so first fire is at 100ms
});
Stopping and Removing Timers
js
const timer = this.time.addEvent({ delay: 1000, loop: true, callback: fn });

// Option 1: Remove from clock (schedules removal next frame)
timer.remove();            // silently expires
timer.remove(true);        // fires callback one last time, then expires

// Option 2: Remove via Clock
this.time.removeEvent(timer);

// Option 3: Remove all timers
this.time.removeAllEvents();
Pausing and Resuming
js
// Pause the entire Clock (all timers freeze)
this.time.paused = true;
this.time.paused = false;

// Pause a single timer
timer.paused = true;
timer.paused = false;
Time Scale (Slow Motion / Fast Forward)
js
// Slow all timers in this scene to half speed
this.time.timeScale = 0.5;

// Speed up a single timer to 2x
timer.timeScale = 2;

// Combined: effective scale = clock.timeScale * event.timeScale
// So 0.5 * 2 = 1x for that specific timer
Reading Timer State
js
timer.getProgress();              // 0..1 for current iteration
timer.getOverallProgress();       // 0..1 across all repeats
timer.getElapsed();               // ms elapsed this iteration
timer.getElapsedSeconds();        // seconds elapsed this iteration
timer.getRemaining();             // ms until next fire
timer.getRemainingSeconds();      // seconds until next fire
timer.getOverallRemaining();      // ms until final fire
timer.getOverallRemainingSeconds(); // seconds until final fire
timer.getRepeatCount();           // repeats left
Timeline: Sequencing Events
js
const timeline = this.add.timeline([
    {
        at: 0,
        run: () => { this.title.setAlpha(1); },
        sound: 'intro'
    },
    {
        at: 2000,
        tween: { targets: this.title, y: 100, duration: 1000 },
        sound: { key: 'whoosh', config: { volume: 0.5 } }
    },
    {
        at: 4000,
        set: { alpha: 0 },
        target: this.title,
        event: 'INTRO_DONE'
    }
]);

timeline.on('INTRO_DONE', (target) => { /* custom event */ });
timeline.on('complete', (tl) => { /* all events ran */ });
timeline.play();
Timeline: Relative Timing with from and in
js
const timeline = this.add.timeline([
    { at: 1000, run: stepOne },         // absolute: 1s from start
    { from: 500, run: stepTwo },        // relative: 500ms after previous (1.5s)
    { from: 1000, run: stepThree }      // relative: 1000ms after previous (2.5s)
]);
  • at -- absolute ms from timeline start (default 0).
  • in -- offset from current elapsed time (useful when adding events to a running timeline).
  • from -- offset from the previous event's start time.

Priority: from overrides in, which overrides at.

Timeline: Conditional Events
js
const timeline = this.add.timeline([
    {
        at: 5000,
        if: () => this.player.health > 0,
        run: () => { this.showBonusRound(); }
    }
]);

If the if callback returns false, the event is skipped (marked complete but actions are not executed).

Timeline: Looping
js
const timeline = this.add.timeline([
    { at: 0, run: () => console.log('start') },
    { at: 1000, run: () => console.log('end') }
]);

timeline.repeat().play();      // infinite loop
timeline.repeat(3).play();     // loop 3 additional times (4 total runs)
timeline.repeat(false).play(); // no looping

The loop callback on a TimelineEventConfig fires on repeat iterations (not the first run).

Timeline: Pause, Resume, Stop, Reset
js
timeline.pause();      // freezes elapsed counter and pauses spawned tweens
timeline.resume();     // resumes elapsed counter and unpauses spawned tweens
timeline.stop();       // sets paused=true, complete=true
timeline.reset();      // elapsed=0, all events marked incomplete, starts playing
timeline.isPlaying();  // true if not paused and not complete
timeline.getProgress(); // 0..1 based on events completed / total events
Timeline: Time Scale
js
timeline.timeScale = 2;   // double speed
timeline.timeScale = 0.5; // half speed

Note: Timeline timeScale does not affect tweens created by the timeline. Set tween timeScale separately.

Timeline: Full Cutscene Example

Timelines excel at choreographing cutscenes with mixed actions (callbacks, tweens, sounds, property sets, and custom events):

js
class CutsceneScene extends Phaser.Scene {
    create() {
        const timeline = this.add.timeline([
            {
                at: 0,
                run: () => { console.log('Start!'); }
            },
            {
                at: 1000,
                tween: {
                    targets: this.player,
                    x: 400,
                    duration: 500,
                    ease: 'Power2'
                }
            },
            {
                at: 1500,
                sound: 'doorOpen'
            },
            {
                at: 2000,
                set: { visible: true },
                target: this.door
            },
            {
                from: 500,
                run: () => { console.log('Relative timing'); }
            },
            {
                at: 5000,
                event: 'cutsceneDone',
                stop: true
            }
        ]);

        timeline.on('cutsceneDone', () => {
            this.scene.start('GameScene');
        });

        timeline.play();
    }
}
Timer Reset and Reuse

A completed TimerEvent can be reset with a new config and re-added to the Clock:

js
const timer = this.time.addEvent({
    delay: 1000,
    callback: this.phase1,
    callbackScope: this,
    repeat: 2
});

// Later, after it completes, reconfigure and re-add:
timer.reset({
    delay: 500,
    callback: this.phase2,
    callbackScope: this,
    repeat: 4
});
this.time.addEvent(timer);  // must re-add; reset() alone does not schedule it

Configuration Reference

TimerEventConfig
PropertyTypeDefaultDescription
delaynumber0Delay in ms before the callback fires
repeatnumber0Times to repeat after first fire. Use -1 for infinite
loopbooleanfalseIf true, repeats indefinitely (same as repeat: -1)
callbackfunction--Function called when the timer fires
callbackScopeanyTimerEventThe this context for the callback
argsArray[]Extra arguments passed to the callback
timeScalenumber1Per-event time multiplier
startAtnumber0Pre-fill elapsed time in ms (makes first fire happen sooner)
pausedbooleanfalseStart the timer in a paused state
TimelineEventConfig
PropertyTypeDefaultDescription
atnumber0Absolute time in ms from timeline start
innumber--Offset from current elapsed (overrides at)
fromnumber--Offset from previous event time (overrides at and in)
runfunction--Callback invoked when event fires
loopfunction--Callback invoked on repeat iterations (not first run)
iffunction--Guard function; return false to skip the event
eventstring--Event name emitted on the Timeline instance
targetany--Scope for run/loop/if and target for set
setobject--Key-value pairs applied to target when event fires
tweenTweenConfig--Tween config or instance created when event fires
soundstring/object--Sound key or { key, config } to play
oncebooleanfalseRemove this event after it fires
stopbooleanfalseStop the entire timeline when this event fires
TimelineEvent (Internal)

The processed event object stored in timeline.events[]. Extends config with:

PropertyTypeDescription
completebooleanWhether this event has fired
timenumberResolved absolute time in ms
repeatnumberHow many times this event has repeated
tweenInstanceTween/TweenChainReference to spawned tween (if any)

Events

Timeline Events
EventConstantListener SignatureFired When
'complete'Phaser.Time.Events.COMPLETE(timeline)All timeline events have been run

Custom events via the event property in TimelineEventConfig are also emitted on the Timeline instance with signature (target).

TimerEvent / Clock

TimerEvent and Clock do not emit EventEmitter events. Timers use the callback property directly. The Clock is managed by scene lifecycle events (PRE_UPDATE, UPDATE, SHUTDOWN, DESTROY).

API Quick Reference

Clock (this.time)
MethodSignatureReturnsDescription
addEvent(config | TimerEvent)TimerEventCreate and schedule a timer event
delayedCall(delay, callback, args?, scope?)TimerEventShorthand for a one-shot delayed call
removeEvent(event | event[])thisRemove specific timer(s)
removeAllEvents()thisSchedule removal of all active timers
clearPendingEvents()thisClear timers not yet added to active list
PropertyTypeDescription
nownumberCurrent clock time in ms
startTimenumberTime the scene started
timeScalenumberDelta multiplier for all timers
pausedbooleanFreeze all timers
Show full SKILL.md (591 more words)Show less
TimerEvent
MethodReturnsDescription
getProgress()number0..1 progress of current iteration
getOverallProgress()number0..1 progress across all repeats
getElapsed()numberElapsed ms this iteration
getElapsedSeconds()numberElapsed seconds this iteration
getRemaining()numberMs until next fire
getRemainingSeconds()numberSeconds until next fire
getOverallRemaining()numberMs until final fire
getOverallRemainingSeconds()numberSeconds until final fire
getRepeatCount()numberRepeats remaining
remove(dispatchCallback?)voidExpire the timer (optionally fire callback)
reset(config)TimerEventReinitialize with new config
destroy()voidNull out callback references
Timeline (this.add.timeline)
MethodSignatureReturnsDescription
add(config | config[])thisAppend events to the timeline
play(fromStart?)thisStart playing (default resets to start)
pause()thisPause timeline and spawned tweens
resume()thisResume timeline and spawned tweens
stop()thisStop (sets paused + complete)
reset(loop?)thisReset elapsed and all events to incomplete
repeat(amount?)thisSet loop count (-1/true=infinite, false=none)
clear()thisRemove all events, reset elapsed, pause
isPlaying()booleanTrue if not paused and not complete
getProgress()number0..1 based on completed event count
PropertyTypeDescription
elapsednumberCurrent elapsed time in ms
timeScalenumberDelta multiplier (does not affect spawned tweens)
pausedbooleanWhether timeline is paused
completebooleanWhether all events have run
loopnumberNumber of additional loops (0=none, -1=infinite)
iterationnumberCurrent loop iteration
totalCompletenumberCount of events that have fired
eventsTimelineEvent[]The internal event array

Gotchas

  1. repeat vs total fires. repeat: 4 means 5 total callback invocations (1 initial + 4 repeats). This is a common off-by-one source.
  2. Zero delay with repeat throws. A TimerEvent with delay: 0 and any repeat/loop will throw 'TimerEvent infinite loop created via zero delay'.
  3. Timelines start paused. You must call timeline.play() after creation. Forgetting this is a frequent mistake.
  4. Timeline timeScale does not affect tweens. Setting timeline.timeScale only scales the timeline's own elapsed counter. Tweens created by the timeline run at their own speed. Set tween timeScale separately or use the TweenManager.
  5. once events are removed permanently. Timeline events with once: true are spliced out after firing and will not reappear on reset() or when looping.
  6. Timer additions are deferred. addEvent() pushes to a pending list processed in preUpdate. The timer will not be active until the next frame.
  7. Clock paused vs timeScale 0. Both freeze timers, but paused = true skips the update loop entirely, while timeScale = 0 still runs the loop with zero delta. Prefer paused for a full freeze.
  8. callbackScope default. If you omit callbackScope, the TimerEvent itself becomes this inside the callback, not the scene. Use arrow functions or pass callbackScope: this explicitly.
  9. Reusing TimerEvent instances. You can pass a TimerEvent object to addEvent(), but it must not be in a completed state. The Clock will reset its elapsed and dispatch state.
  10. Timeline from chains. Each from offset is relative to the previous event's resolved time, not the previous from value. Events are processed in array order.
  11. Scene pause pauses the Timeline. When a scene is paused (scene.pause()), the Timeline's update loop stops too, since Timeline updates are driven by the scene's update step.
  12. timer.reset() does not re-add to Clock. Calling timer.reset(config) reinitializes the timer but does not schedule it. You must call this.time.addEvent(timer) again after resetting.

Source File Map

FileDescription
src/time/Clock.jsScene Clock plugin -- creates, updates, removes TimerEvents
src/time/TimerEvent.jsIndividual timer -- delay, repeat, loop, progress tracking
src/time/Timeline.jsEvent sequencer -- scheduled actions, tweens, sounds, looping
src/time/typedefs/TimerEventConfig.jsConfig typedef for addEvent()
src/time/typedefs/TimelineEventConfig.jsConfig typedef for timeline.add()
src/time/typedefs/TimelineEvent.jsInternal event object typedef
src/time/events/COMPLETE_EVENT.js'complete' event constant for Timeline
src/time/events/index.jsEvents namespace barrel file

© autonomous-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in store/agents/phaser/skills/time-and-timers of autonomous-ai/openharness.

Open the folder on GitHubat commit cc4983e

Compare with similar skills

Time And Timers next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Time And Timers compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Time And Timers this skillautonomous-ai/openharness1.2k—~4.6kAutomated safety check: PassMIT
Eventscoreyhaines31/marketingskills54k—~3kAutomated safety check: PassMIT
Event Sourcing Architectdavila7/claude-code-templates33k4 repos~659Automated safety check: PassMIT
Event Store Designwshobson/agents40k9 repos~828Automated safety check: PassMIT
Event Delegationthedaviddias/Front-End-Checklist74k—~500Automated safety check: PassMIT
Event-Driven Sentiment SignalsHKUDS/Vibe-Trading35k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Events

    coreyhaines31/marketingskills

    When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences.

    54k GitHub stars~3k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Event Sourcing Architect

    davila7/claude-code-templates

    Expert in event sourcing, CQRS, and event-driven architecture patterns.

    33k GitHub starsUsed in 4 repos~659 tokens
    Backend & APIsAuto-check passed
  • Event Store Design

    wshobson/agents

    Designs event stores for event-sourced systems: requirements, a comparison of EventStoreDB, PostgreSQL, Kafka, DynamoDB and Marten, and stream and versioning practices.

    40k GitHub starsUsed in 9 repos~828 tokens
    Backend & APIsAuto-check passed
  • Event Delegation

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Use event delegation for dynamic content.

    74k GitHub stars~500 tokensUpdated 4 days ago
    Auto-check passed
  • Scores news, announcements and macro events with the LLM, stores them in an event CSV and blends the decaying event signal with technical signals in signal_engine.py.

    35k GitHub stars~2.1k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Events Activities

    sickn33/agentic-awesome-skills

    Event register: type, date and time, venue, organizer, audience, budget against actual cost, RSVP and attendance counts and feedback score.

    47k GitHub starsUsed in 1 repo~3.9k tokens
    Data & AnalyticsAuto-check passed

More from autonomous-ai/openharness

All 100 skills in this repo
  • G-code Slicer Tool

    autonomous-ai/openharness

    Slices 3D mesh files into printer-profiled plain G-code through real slicer CLIs, with backend discovery, input inspection, dry runs and static validation.

    1.2k GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Home Assistant Automation Builder

    autonomous-ai/openharness

    Turns a home-automation request into standard, testable automations.yaml, run against Home Assistant Core's real triggers and verified with its own trace tool.

    1.2k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Score Music Composer

    autonomous-ai/openharness

    Turns a musical brief into LilyPond concert-pitch music, checked parts for each instrument and a playable practice pack.

    1.2k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • OrcaSlicer 3MF and G-code Workflow

    autonomous-ai/openharness

    Turns an STL and explicit printer and material requirements into compared OrcaSlicer plans, an editable 3MF project, checked G-code and a portable handoff.

    1.2k GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Sheets and Docs Report Builder

    autonomous-ai/openharness

    Builds an editable DOCX report, a formula-driven XLSX workbook and a fresh LibreOffice PDF preview from one structured source file, then checks them together.

    1.2k GitHub stars~708 tokensUpdated today
    Auto-check passed
  • Bambu Labs

    autonomous-ai/openharness

    Dry-run, upload, and cautiously initiate local Bambu Lab print jobs from validated plain .gcode, using Bambu LAN FTPS/MQTT handoffs.

    1.2k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check: warnings

Questions about Time And Timers

What does Time And Timers do?

A skill your agent uses when using timers and time-based events in Phaser 4. Time And Timers is an agent skill from autonomous-ai/openharness. Use this skill when using timers and time-based events in Phaser 4.

When should I use Time And Timers?

Time And Timers fits situations like: using timers and time-based events in Phaser 4.

How do I install Time And Timers in Claude Code?

Run `npx skills add autonomous-ai/openharness --skill time-and-timers -a claude-code`. Or copy the skill folder (store/agents/phaser/skills/time-and-timers in autonomous-ai/openharness) into .claude/skills/time-and-timers in your project. Claude Code loads it when a task matches its description.

How do I install Time And Timers in Codex?

Run `npx skills add autonomous-ai/openharness --skill time-and-timers -a codex`. Or copy the skill folder (store/agents/phaser/skills/time-and-timers in autonomous-ai/openharness) into .agents/skills/time-and-timers in your project. Codex loads it when a task matches its description.

Can I use Time And Timers in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add autonomous-ai/openharness --skill time-and-timers -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/time-and-timers, .gemini/skills/time-and-timers, .github/skills/time-and-timers and .opencode/skills/time-and-timers in your project.

What does Time And Timers need to run?

SKILL.md names no scripts, command-line tools or credentials: Time And Timers is instructions for the agent only.

Does Time And Timers access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Time And Timers safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Time And Timers use?

Time And Timers is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Time And Timers use?

About 4.6k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Time And Timers?

Skills that share tags, products or a category with Time And Timers: Events (coreyhaines31/marketingskills, 54k stars), Event Sourcing Architect (davila7/claude-code-templates, 33k stars), Event Store Design (wshobson/agents, 40k stars) and Event Delegation (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Time And Timers?

autonomous-ai (a GitHub organization) maintains it in autonomous-ai/openharness, which has 1,210 GitHub stars. The repository holds 100 skills in this directory. The repository was last updated on October 10, 2026.

Source: autonomous-ai/openharness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.