Persist Ml Git logo

Persist Ml Git

Organization
probabl-ai
persist-ml-git

Commit the current loop stage when the end-turn hook says invoke. Trigger after `python -m skore_skills git end-turn --stage <stage>` returns action invoke, or when the user asks to commit this turn's work.

Overview

Publisherprobabl-ai
Repositoryskore-skills
Skill namepersist-ml-git
Stars
144
Forks
9
Bundled files
1
LicenseBSD-3-Clause
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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by probabl-ai on GitHub. Read the source before you install it.

Installation

Install the Persist Ml Git 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/probabl-ai/skore-skills/tree/main/skills/persist-ml-git
  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/probabl-ai/skore-skills.git /tmp/skore-skills
mkdir -p .claude/skills
cp -r /tmp/skore-skills/skills/persist-ml-git .claude/skills/persist-ml-git
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Persist Ml Git 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 Persist Ml Git 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 Persist Ml Git 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.

Persist ML Git

The hook already ran this turn. Follow its JSON. Run git yourself.

  1. If action is skip, stop. Do not nag. Load triage-ml-task if installed, else stop.
  2. If reason is resolve-dotfiles and ambiguous_dotfiles is non-empty, ask once which hidden paths to keep. Include an explicit Keep none option. An empty multi-select is not an answer. Then python -m skore_skills git ignore-merge --decide plus --keep <path> for each chosen path (no --keep if they keep none, including when they pick Keep none). Do not re-ask names gone from the next JSON. Never keep .env or .skore. If ambiguous_dotfiles is empty or reason is persist, do not ask about hidden paths. Exit code 2 from git ignore-merge is the structured dotfile decision required outcome, not a generic command failure: read its JSON, ask the decision, and rerun with --decide.
  3. If review_paths is non-empty, ask once which of those paths to keep tracked. Include an explicit Keep none option. An empty multi-select is not an answer. List each JSON path and kind, and say that the rest are ignored. Then python -m skore_skills git review-decide with --keep <path> for each chosen path and --ignore <path> for every other path in the list (no --keep if they keep none, including when they pick Keep none). Pass a folder path through with its trailing slash so the ignore line is that folder. Copy paths and kinds from the JSON; do not invent them. Do not re-ask paths gone from the next JSON. Never --keep .env or .skore. If review_paths is empty, do not ask about file size, artifacts, or datasets. Do this when reason is resolve-review, and also after step 2 when reason is resolve-dotfiles and that payload lists review_paths. Exit code 2 from git review or git review-decide is the structured review decision required outcome, not a generic command failure: read its JSON, ask the decision, and rerun review-decide.
  4. Run git status. Stage only non-secret paths that are not still listed in review_paths: git add -- <paths>. Never .env or .skore.
  5. Commit with a one-line subject from this turn's files and intent: git commit -m "…". Do not use a canned stage slogan.
  6. Load triage-ml-task if installed, else stop.

Stop conditions

  • Do not git push, amend, rebase, or git config.
  • Do not invent a commit when the hook was skip (off, unanswered, no_repo, clean).
  • Do not call python -m skore_skills git end-turn --stage <stage> to perform the commit; that command only prints facts.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Persist Ml Git AI skill do?

Commit the current loop stage when the end-turn hook says invoke. Trigger after `python -m skore_skills git end-turn --stage <stage>` returns action invoke, or when the user asks to commit this turn's work.

Why use Persist Ml Git on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/probabl-ai/skore-skills/tree/main/skills/persist-ml-git. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Persist Ml Git?

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 Persist Ml Git?

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

Is the Persist Ml Git AI skill free?

Yes. It is published on GitHub by probabl-ai under the BSD-3-Clause 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 👇