Claude Md Updater logo

Claude Md Updater

Community
jamditis
claude-md-updater

Scans the session for lessons and workflows, then proposes scoped CLAUDE.md edits. Use for save this lesson or add to context.

Overview

Publisherjamditis
Repositoryclaude-skills-journalism
Skill nameclaude-md-updater
Stars
397
Forks
64
Bundled files
1
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • 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 jamditis on GitHub. Read the source before you install it.

Installation

Install the Claude Md Updater 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.
  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/jamditis/claude-skills-journalism.git /tmp/claude-skills-journalism
mkdir -p .claude/skills
cp -r /tmp/claude-skills-journalism/dev-toolkit/skills/claude-md-updater .claude/skills/claude-md-updater
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Claude Md Updater 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 Claude Md Updater 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 Claude Md Updater 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.

CLAUDE.md auto-updater

Analyze the current conversation to identify information worth persisting in CLAUDE.md for future sessions, then propose the edits for approval before writing anything.

What to look for

1. Hard-won lessons

  • Debugging sessions that revealed non-obvious causes
  • Workarounds for platform or tool limitations
  • Anti-patterns discovered through failure
  • "The real problem was..." moments

2. New infrastructure

  • New services deployed
  • New endpoints or URLs
  • New file paths or directories
  • New credentials or tokens (reference only, never the values)

3. New workflows

  • Commands that solve recurring problems
  • Multi-step processes that work well
  • Integration patterns between systems

4. Updated information

  • Changed ports, IPs, or URLs
  • New capabilities added to existing systems
  • Deprecated or removed features

Analysis process

  1. Scan the conversation for keywords:

    • "fixed", "solved", "the issue was", "turns out"
    • "deployed", "set up", "configured", "installed"
    • "new endpoint", "new service", "new path"
    • "doesn't work", "limitation", "workaround"

  2. Categorize findings. Only durable facts belong in CLAUDE.md:

    • Hard-won lessons go to the "Hard-won lessons" section
    • Infrastructure changes update the relevant section
    • New workflows go to the appropriate section
    • Transient, session-specific notes do not go in CLAUDE.md (see "What not to persist")

  3. Build the exact diff. Produce a unified diff against the current CLAUDE.md showing the precise lines and sections to be added or changed. This diff is what the user approves, not a summary of it.

  4. Present the diff for approval and write nothing until the user approves.

Output format

Show the exact patch first, then a short summary grouped by category:

## Proposed CLAUDE.md updates

```diff
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ section being changed @@
 existing context line
+new durable lesson, infra fact, or workflow
```

Summary of the diff above:
- Hard-won lessons: [one line, if any]
- Infrastructure updates: [one line, if any]
- New workflows: [one line, if any]

Apply this diff? Nothing is written until you approve.

What not to persist

CLAUDE.md is team-shared (checked into git) and advisory: it loads into every session, so it is for durable, infrequently-changing facts, not a running log. Per the project-memory skill, keep these out of CLAUDE.md:

  • Transient "what we did today" session summaries
  • Anything that changes frequently
  • Things Claude learns over time through corrections

Route those to auto memory (~/.claude/projects/<project>/memory/, which Claude maintains on its own) or to a gitignored CLAUDE.local.md for personal notes. Putting them in CLAUDE.md bloats shared context and loads stale per-session facts into future sessions.

Rules

  1. Never add sensitive values. Reference where a credential is stored; never include the actual token.
  2. Keep it concise. CLAUDE.md should stay scannable; target under 200 lines.
  3. Avoid duplication. Check whether the information already exists before adding it.
  4. Match the existing style. Follow the tone and format of the current file.
  5. Durable facts only. Persist hard-won lessons, infrastructure facts, and workflows. Session-specific notes belong in auto memory or a gitignored CLAUDE.local.md, never the committed CLAUDE.md.

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 Claude Md Updater AI skill do?

Scans the session for lessons and workflows, then proposes scoped CLAUDE.md edits. Use for save this lesson or add to context.

Why use Claude Md Updater on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jamditis/claude-skills-journalism/tree/master/dev-toolkit/skills/claude-md-updater. 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 Claude Md Updater?

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 Claude Md Updater?

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

Is the Claude Md Updater AI skill free?

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

Related AI Skills

View all
obra logo

Verification Before Completion

obra
CommunityPopular

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence…

25.8K
288.1K
Instructions
View
obra logo

Writing Plans

obra
CommunityPopular

Use when you have a spec or requirements for a multi-step task, before touching code

25.8K
288.1K
1 files
View
mattpocock logo

Ask Matt

mattpocock
CommunityPopular

Ask which skill or flow fits your situation. A router over the skills in this repo.

22.3K
264.4K
2 files
View
mattpocock logo

Code Review

mattpocock
CommunityPopular

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what…

22.3K
264.4K
1 files
View

Set up your own AI workspace now

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