setup-laterdog
Skill2 starsChanged 29 days agoApache-2.0View on GitHub
Clone, build, install and start later.dog on a Mac for the person you work for, hand them exactly the four steps only they can do, and prove the result.
- Installs packages
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-appSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- verify-laterdogSkill
- architectSkill
- benchmark-checklistSkill
- correct-recurring-errorsSkill
- create-verification-skillSkill
- independent-reviewSkill
- maintain-verification-skillSkill
- monitor-and-shipSkill
- orchestrate-cloud-workSkill
- setup-laterdogSkill
- verify-laterdogSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use when someone says "set up later.dog for me", "install later.dog", or points you at github.com/woodbeary/later-dog.
- Distinctive: line 16
Follow AGENTS.md: pnpm only, Node 24+, never verify against the person's live data when a fixture will do.
- Distinctive: line 17
Never type, read aloud or move a credential.
- Distinctive: line 36
Their turn, part 2 — permissions: If they want a dog to control this Mac ("This PC" in Dog's computer), macOS asks for Accessibility and …
- Distinctive: line 53
Leave the person a short list: what works now, which of steps 4, 5 and 7 are still theirs, and the one command to restart the app.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Set up later.dog
Use when someone says "set up later.dog for me", "install later.dog", or points you at github.com/woodbeary/later-dog. Use the later.dog MCP server. Tool prefixes depend on the client; discover tools by their names below.
later.dog is a macOS desktop app (Apple silicon) for AI agents (the app calls them dogs) that run on the person's own ChatGPT or Claude accounts. Nothing here needs an API key. Four things need the person's hands; everything else is yours.
Rules
- Follow
AGENTS.md: pnpm only, Node 24+, never verify against the person's live data when a fixture will do. - Never type, read aloud or move a credential. Device codes, OAuth consents, macOS permission prompts and GitHub tokens are the person's; you prepare the exact step and say when it is their turn.
- Say what you verified and what you did not. "Fixture success does not qualify a live provider."
Procedure
- Prerequisites.
git, Node 24 (nvmis fine: the repo has.nvmrc), pnpm 10.33 (corepack enable && corepack prepare pnpm@10.33.0 --activate). The provider CLIs the person will use: Codex (npm i -g @openai/codex@0.154.0), Claude Code (npm i -g @anthropic-ai/claude-code). Install them under the newest Node the machine has: a GUI launch searches nvm's bin directories newest first. - Get the code.
git clone https://github.com/woodbeary/later-dog.git && cd later-dog && pnpm install --frozen-lockfile. - Build and install the app.
pnpm laterdog:package→release/mac-arm64/later.dog.app; thenditto release/mac-arm64/later.dog.app /Applications/later.dog.app && open -a later.dog. Ifswiftcfails on this Mac the build still completes without voice dictation; say so. (Or use a release zip from GitHub: unzip, drag to Applications and open it. Releases are signed with an Apple Developer ID and notarized, so macOS only asks once.) - Their turn, part 1 — sign in. The welcome tour's providers step lists what was found. For each provider they want: ChatGPT plan uses Codex's device code (a URL and a code, confirmed in their browser), Claude opens a browser consent and pastes a code. Tell them which provider, where the button is, and that the code expires in minutes. Do not start a sign-in they did not ask for.
- Their turn, part 2 — permissions. If they want a dog to control this Mac ("This PC" in Dog's computer), macOS asks for Accessibility and Screen Recording.
- First dog. New dog → Starting role (chief of staff, engineer, nightly audit engineer, reviewer, project manager, inbox manager, intel scout, gatekeeper) → pick the provider that is Ready. Send one message and make sure a reply comes back; if the reply is a sign-in card, go back to step 4.
- Optional: the self-hosted supervisor (not part of the 0.3.3 release). Skip it unless they ask for it. Follow
docs/laterdog/cloudflare.md(their Cloudflare account,wrangler loginis their click; the app secretsLATERDOG_TOKENandLATERDOG_BACKUP_KEYyou may generate withopenssl rand; GitHub: runpnpm laterdog:github(or use Workspace → Connect GitHub) — it prints a code from GitHub's device sign-in inside the container; the person enters it at github.com/login/device and authorizes; never move their token yourself). Save~/.laterdog/supervisor.json({ "url": "https://…workers.dev", "tokenFile": "~/.laterdog/supervisor-token" }), runpnpm laterdog:login(device code, theirs), thenpnpm laterdog:doctormust showprofile.authenticated: trueandgithub.authenticated: true. Register a repository in Workspace with its published Codex Cloud environment ID (from the Codex web UI, theirs).
Prove it
pnpm laterdog:doctoroutput (when a supervisor is connected), the About dialog's version, and one real reply from a dog. Keep screenshots or the exact command output; do not describe what you did not see.- Leave the person a short list: what works now, which of steps 4, 5 and 7 are still theirs, and the one command to restart the app.
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
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.

