Skip to content
Skills Library
Personal productivity · Automation

tidy

/tidy

Run the Keeper nightly upkeep by hand with the installed nightly job: lint, the dream code half, the memory check, the workspaces view, and the state push. Use when the person says `/tidy`, when the start page says the nightly is OLDER THAN 36 HOURS, or when a failed nightly needs a rerun.

Repository
foxrun ↗
Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Run the Keeper nightly upkeep by hand with the installed nightly job: lint, the dream code half, the memory check, the workspaces view, and the state push. Use when the person says `/tidy`, when the start page says the nightly is OLDER THAN 36 HOURS, or when a failed nightly needs a rerun.

Original author description

Run the Keeper nightly upkeep by hand with the installed nightly job: lint, the dream code half, the memory check, the workspaces view, and the state push. Use when the person says `/tidy`, when the start page says the nightly is OLDER THAN 36 HOURS, or when a failed nightly needs a rerun.

How it works

  1. When
  2. Steps
  3. Gotchas
Original SKILL.md headings · 38 lines, 292 words
SKILL.md preview
---
name: tidy
description: "Run the Keeper nightly upkeep by hand with the installed nightly job: lint, the dream code half, the memory check, the workspaces view, and the state push. Use when the person says `/tidy`, when the start page says the nightly is OLDER THAN 36 HOURS, or when a failed nightly needs a rerun."
kind: knowledge
---

# Tidy

`/tidy` runs the same job the scheduled nightly runs, now. It uses the installed nightly, never a copy.

## When

- The person says `/tidy`.
- The start page `NIGHTLY` line ends with `OLDER THAN 36 HOURS: run /tidy`.
- The nightly failed and its fault is fixed.

## Steps

1. Check that no nightly runs now: `ls ~/.foxrun/runs/.dream.lock`.
   Done when: the file is absent. If it is there, stop and say who holds it. Never remove it.
2. Run the installed nightly the way the scheduled job runs it:

   ```
   cd ~/.foxrun && FOXRUN_HOME=~/.foxrun FOXRUN_PORTFOLIO=~/foxrun PYTHONDONTWRITEBYTECODE=1 python3 -B ~/.foxrun/cron/nightly.py
   ```

   Add `--dry-run` to see the steps with no push and no dream write.
   Done when: it prints its last line, `Nightly: exit <n>; ...; <receipt folder>`.
3. Read the receipt: the newest `~/.foxrun/runs/nightly/*-nightly/receipt.json`.
   Done when: you have the exit and the result of each step: lint, dream, check, workspaces view, push.
4. Rebuild the start pages: `python3 ~/.foxrun/memory/state.py build --all`.
   Done when: the `NIGHTLY` line shows this run and has no `OLDER THAN 36 HOURS` flag.
5. Report one line for each step, ok or failed, with the finding counts and the receipt path.
   Done when: each failed step has a task or bug row the same day (the Keeper loop).

## Gotchas

- The job runs at low priority, so it can take a few minutes. Wait for its last line.
- A finding is not a fix. Do not fix findings inside `/tidy`; file them.
- The push step sends only `~/.foxrun/state/` to its own remote, as the nightly does each night.
- If `~/.foxrun/cron/nightly.py` is missing, say so and stop. Do not run a source copy.
- Nothing is cleared or deleted. Receipts stay in `~/.foxrun/runs/nightly/`.
Files in this package (2)
  • SKILL.md 2 KB
  • replays/runs-the-installed-nightly.json 1 KB

Versions

RepositoryScoreLicence
This page · foxrun-ai/foxrun100MIT
mblode/agent-skills100MIT
finolabs/finolabs-vibecode100MIT
ericrisco/rsc-harness100MIT
davepoon/buildwithclaude100MIT
darioabc/massimo100MIT
GaoFei2025-0314/tidy100MIT
stefanocaronia/claude-project90MIT
ChristopherMichael-Stokes/claude-config90MIT

Database snapshot: 13.11.2026 · package version f320b63c2cd6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100nightly
    Run canonical nightly close-parity maintenance across synthesis, hygiene, sweeps, health, ledgers, and vault sync. Use when running the full nightly protocol.
  • 96nightly-dream
    Use when setting up a nightly self-review cron for Hermes.
  • 90memory-tidy
    Use when auditing, consolidating, or cleaning a repo's .claude/memory store, "dọn memory", "memory tidy", the biweekly memory audit, duplicate or stale memory notes, MEMORY.md index drift, or a scheduled memory-tidy audit. NOT for the built-in machine-local auto-memory under…
  • 96review
    Show the memory consolidation proposal that is waiting for approval (from a nightly dream or an earlier /rem:dream) and apply the operations the user picks. Use when the session start note says a dream is waiting, or the user says "show the dream", "review memory changes", "what…
  • 100nightly-ledger-capture
    Stage missing honesty, trust-decay, failure-mode, and decision-outcome records from local evidence. Use when capturing nightly ledger candidates; writes require an oracle.
  • 82dream
    Review, apply or discard last night's dream (DREAM.md), the proposed tidy-up of Claude's memory that /sundown:shutdown writes. Only runs when the user types /sundown:dream.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.