agentleFS
Sign inStart free
Panchangam18Panchangam18/background-computer-use/skills/clock/SKILL.md

clock

Skill4 starsChanged 7 months agoMITView on GitHub

Clock.app heuristics for background-computer-use. Use when the user asks you to set an alarm, start a timer, run a stopwatch, or manage world clocks.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. jootsing-research/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always call get_app_state app="Clock" before interacting.

    line 8
  2. Very specific:

    When adding a world-clock city from the search sheet, click the result row rather than pressing Return.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Driving Clock with background computer use

  1. Always call get_app_state app="Clock" before interacting.
  2. Clock has four tabs (World Clock, Alarms, Stopwatch, Timers); after switching tabs, the tree changes completely — re-call get_app_state.
  3. When adding a world-clock city from the search sheet, click the result row rather than pressing Return.
  4. Alarm toggles are switch elements embedded in each row — click the switch, not the row.
  5. Time pickers are usually settable=true; prefer set_value with a numeric string. If the picker is not settable, use scroll against the picker element's index.
  6. In Stopwatch, Start/Stop is a single button whose title toggles; re-read state after each press.

Extended notes live in server/app-hints/Clock.md; the MCP server injects them on every get_app_state call for Clock.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free