State logo

State

Community
cwinvestments
state

Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.

Overview

Publishercwinvestments
Repositorymemstack
Skill namestate
Stars
425
Forks
45
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 cwinvestments on GitHub. Read the source before you install it.

Installation

Install the State 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/cwinvestments/memstack/tree/master/skills/state
  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/cwinvestments/memstack.git /tmp/memstack
mkdir -p .claude/skills
cp -r /tmp/memstack/skills/state .claude/skills/state
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable State 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 State 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 State 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.

📍 State: Updating Project State...

Maintain a living document of where you are right now in a project.

Activation

When this skill activates, output:

📍 State: Updating project state...

Then execute the protocol below.

Context Guard

ContextStatusPriority
User says "update state", "save state", "project state"ACTIVE: update STATE.mdP1
User says "where was I", "where did I leave off"ACTIVE, read and present STATE.mdP1
User starts a session and STATE.md existsACTIVE, read silently, use as contextP2
User says "save diary" or "log session"DORMANT, Diary handles full session logsnone
User says "save project" or "handoff"DORMANT, Project skill handles lifecyclenone
User asks to recall past sessionsDORMANT, Echo handles historical recallnone

Protocol

Reading State (session start or "where was I")

  1. Check for STATE.md in the current project's .claude/ directory:
    {project_dir}/.claude/STATE.md
  2. If found, read it and present a brief summary:
    • What was being worked on
    • Any blockers
    • The immediate next step
  3. If not found, say: "No STATE.md exists yet. I can create one after we start working."

Writing/Updating State

  1. Gather current state:

    • What task/phase is actively being worked on right now
    • Decisions made during this session (with rationale)
    • Open blockers or unanswered questions
    • Explicit next steps (not vague, specific enough to resume cold)
    • Key files modified recently
  2. Check git status for uncommitted work:

    bash
    git status --short
  3. Write STATE.md to the project's .claude/ directory:

    markdown
    # Project State
    *Last updated: {YYYY-MM-DD HH:MM}*
    
    ## Currently Working On
    {Active task or phase: be specific}
    
    ## Decisions Made
    - {Decision}: {Rationale}
    
    ## Blockers
    - [ ] {Blocker description}
    
    ## Next Steps
    1. {Immediate next action, specific enough to start cold}
    2. {Following action}
    
    ## Recently Modified Files
    - {file path}: {what changed}
    
    ## Uncommitted Changes
    {List any unstaged/uncommitted work, or "None: clean working tree"}
  4. Confirm with a brief summary of what was saved.

Deconfliction

SkillWhat it tracksWhen
StateCurrent snapshot, where you are right nowDuring session, living document
DiaryHistorical log, what you did in a sessionEnd of session, append-only
ProjectProject lifecycle, handoff between sessionsSession boundaries
WorkTask list, what needs to be doneWhen planning/tracking todos

State is the present tense complement to Diary's past tense. State tells you where to resume; Diary tells you what happened.

Inputs

  • Current working context (project, files, git status)
  • User's description of current state (or auto-detected from session)

Outputs

  • {project_dir}/.claude/STATE.md: updated living document
  • Brief confirmation summary

Example Usage

User: "update state"

📍 State: Updating project state...

Saved: C:\Projects\AdminStack\.claude\STATE.md

Currently: Building CC Monitor notification system
Blockers: None
Next: Wire up WebSocket events to notification dropdown

This will auto-load next session for seamless pickup.

Level History

  • Lv.1: Base: Living STATE.md creation and update protocol. Read via Work Step 0 or manual invocation. Deconfliction with Diary/Project/Work. (Origin: MemStack v3.1, Feb 2026)

Frequently asked questions

What does the State AI skill do?

Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.

Why use State on TypingMind?

Because you install it once and use it with any model. State 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 State in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cwinvestments/memstack/tree/master/skills/state. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use State?

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 State?

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

Is the State AI skill free?

Yes. It is published on GitHub by cwinvestments 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 👇