agentleFS
yourbeckettyourbeckett/beckett-for-claude/skills/check-ins/SKILL.md

check-ins

Skill0 starsChanged 25 days agoMITView on GitHub

Set up check-ins that beckett sends on a schedule, such as a weekday nudge to log a run or a Sunday prompt to plan the week, and change or pause them.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When beckett is connected, follow the shared rules in the use-beckett skill.

    line 12

≈ “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

Check-ins

  • If no beckett tools are available, beckett isn't connected yet. Tell the user once, and if you can suggest connectors, suggest beckett so they get a Connect button. Give the steps, keep what they asked for, and offer to finish it once beckett is connected. Don't say anything was saved to or found in beckett.
    • In Claude chat or Cowork: open Customize > Plugins, choose beckett, and select Connect on the Connectors tab.
    • In Claude Code: run /mcp, choose beckett, and sign in.
    • Signing in creates a beckett account for anyone who doesn't have one, with a free week and no card.
  • When beckett is connected, follow the shared rules in the use-beckett skill.
  • A check-in is a recurring prompt beckett sends to ask the user for an update. Create one with beckett_check_in_write: its type (recurring_check_in, habit_nudge, task_reminder, or event_reminder), the time, a short label, the frequency (daily, weekday, weekly, custom, or interval_days), and the prompt to ask.
  • To change a check-in, find it with beckett_check_in_read, then update its time, frequency, or prompt. To pause one, set active to false; to resume it, set active to true.
  • A one-time reminder is a task, not a check-in; see the reminders skill.

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.