Check In logo

Check In

OrganizationPopular
amd
check-in

Run a short personal check-in that picks up where the last one left off, following up on what the user said they would do and recording what changed. Use when the user says good morning, asks for a check-in, or asks what they were working on.

Overview

Publisheramd
Repositorygaia
Skill namecheck-in
Stars
1.6K
Forks
176
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by amd on GitHub. Read the source before you install it.

Installation

Install the Check In AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/amd/gaia/tree/main/hub/skills/check-in
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/amd/gaia.git /tmp/gaia
mkdir -p .claude/skills
cp -r /tmp/gaia/hub/skills/check-in .claude/skills/check-in
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Check In in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Check In on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Check In is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Check In

A check-in is worth having only if it remembers the last one. This is the smallest skill in the pack that demonstrates the whole memory loop: recall commitments, ask about them, write back what you learn.

Procedure

  1. Recall open commitments. recall(category="reminder", limit=20) — the things the user said they would do and has not closed out. reminder is the category for todos; there is no task category, and passing one silently matches nothing.
  2. Recall recent context. search_past_conversations(days=7, limit=10) for what has actually been going on. Use it to make the greeting specific.
  3. Open with one concrete follow-up, not a generic greeting:

    Yesterday you said you'd finish the pricing deck. How did that go? If memory is empty, say so plainly and ask what they are working on — a fabricated callback is far worse than admitting a blank slate.

  4. Ask at most three questions. A check-in that turns into an interrogation stops getting answered.
  5. Write back what changed.
    • Done → update_memory(knowledge_id=..., content="... — completed <date>")
    • Still open → leave it, but note the new expected date
    • New → remember(fact="<commitment> by <date>", category="reminder", due_at="<ISO date>")
  6. Close with one line on what you will ask about next time.

Tone

Brief, specific, unsentimental. No performance of enthusiasm, no "you've got this". Track the work, not the mood — unless the user brings up the mood, in which case listen rather than advise.

Honest limits

  • The user starts this, not GAIA. A truly proactive daily check-in needs the scheduler to run skills on a cron, which is not wired yet (--skill is rejected when adding a schedule). Today this runs when invoked.
  • Everything here depends on memory being enabled. With memory off there is no check-in to speak of — say so instead of running an empty version.
  • Do not record anything the user marks private. If in doubt, ask before storing.

Fork this

Point it at a team instead of a person: recall commitments per owner in step 1 and produce a standup digest in step 6.

Frequently asked questions

What does the Check In AI skill do?

Run a short personal check-in that picks up where the last one left off, following up on what the user said they would do and recording what changed. Use when the user says good morning, asks for a check-in, or asks what they were working on.

Why use Check In on TypingMind?

Because you install it once and use it with any model. Check In is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Check In in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/amd/gaia/tree/main/hub/skills/check-in. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Check In?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Check In?

As many as you like. As long as a model supports skills, you can use Check In with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Check In AI skill free?

Yes. It is published on GitHub by amd under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇