Staying Current

Community

Houseofmvps

staying-current

Use whenever answering anything version-sensitive — library/framework/SDK APIs, package versions, model IDs, pricing, CLI flags, config, or "latest/newest" anything. Verify against current sources instead of training data.

Overview

Publisher	Houseofmvps
Repository	`ultraship`
Skill name	`staying-current`
Stars	122
Forks	14
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

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 Houseofmvps on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
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.

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/Houseofmvps/ultraship.git /tmp/ultraship
mkdir -p .claude/skills
cp -r /tmp/ultraship/skills/staying-current .claude/skills/staying-current

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Staying Current 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 Staying Current 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 Staying Current 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.

Staying Current

Training data has a cutoff. Libraries ship breaking changes, prices change, model IDs get renamed, and APIs get deprecated after that cutoff. Answering version-sensitive questions from memory is the single most common way an otherwise-correct agent ships wrong code. This skill is the standing rule for not doing that.

The Ultraship Currency Guard hook (UserPromptSubmit) already fires on every prompt and injects a reminder when it detects version-sensitive language. This skill is what you do when that fires — or any time you're about to state a fact whose correct answer changes over time.

The rule

Before stating any of the following, verify it against a current source. Never answer from training data alone:

Library / framework / SDK API signatures, imports, hooks, options
Package versions, compatibility, and what's deprecated
CLI flags and config file schemas
Model IDs, model names, context windows, and capabilities
Pricing, rate limits, free-tier limits, quotas
"Latest", "newest", "current", "recommended" anything
Release notes, changelogs, migration steps

Where to verify

Source	Use for
context7 MCP (`resolve-library-id` → `query-docs`)	Library/framework/SDK documentation and API syntax. This is the primary source for code. Use it even when you think you know the answer.
WebSearch / WebFetch	Versions, pricing, model IDs, release notes, deprecations, anything not in a library's docs. The current month is the search context — say "2026" in queries when recency matters.
The project's lockfile (`package-lock.json`, `pnpm-lock.yaml`, `requirements.txt`, `go.sum`, `Cargo.lock`)	The exact version actually installed here — always check this before assuming a version.

How to apply

Detect. If the question touches anything in the rule above, do not answer yet.
Check what's installed. Read the lockfile/manifest to learn the real version in this project.
Pull current docs. Resolve the library on context7 and query the specific API. For non-library facts (pricing, model IDs), WebSearch then WebFetch the authoritative page.
Answer from the source, and cite it. Quote the version/date you verified against.
If you can't verify, say so. "I couldn't confirm this against a current source" is correct. A confident wrong API is not.

Anti-patterns

❌ Writing an import or hook call from memory for a library you haven't checked this session.
❌ Quoting a price or model ID without fetching the current page.
❌ Assuming the latest major version — projects pin old ones; read the lockfile.
❌ Treating a recalled Ultraship memory as current — memories are point-in-time; re-verify file paths, flags, and versions before acting on them.

Note on Claude/Anthropic specifically

When the task involves Claude, the Anthropic API, model IDs, or pricing, the same rule applies with extra force — these change frequently. Verify model IDs and pricing against current Anthropic docs before quoting them.

Frequently asked questions

What does the Staying Current AI skill do?

Why use Staying Current on TypingMind?

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

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

Which AI models can use Staying Current?

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 Staying Current?

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

Is the Staying Current AI skill free?

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

Test Driven Development

obra

CommunityPopular

Use when implementing any feature or bugfix, before writing implementation code

Using Git Worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

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…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Staying Current

The rule

Where to verify

How to apply

Anti-patterns

Note on Claude/Anthropic specifically

Frequently asked questions

Related AI Skills

Set up your own AI workspace now