Ctx Verify logo

Ctx Verify

Community
stevesolun
ctx-verify

Select proportional validation for changes or reviews in the ctx repository. Use before handing off material code, workflow, migration, documentation, security, packaging, or release changes; before a PR; or when asked whether a change is adequately tested. Do not use for pure questions with no changed artifact.

Overview

Publisherstevesolun
Repositoryctx
Skill namectx-verify
Stars
588
Forks
69
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 stevesolun on GitHub. Read the source before you install it.

Installation

Install the Ctx Verify 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/stevesolun/ctx/tree/main/.claude/skills/ctx-verify
  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/stevesolun/ctx.git /tmp/ctx
mkdir -p .claude/skills
cp -r /tmp/ctx/.claude/skills/ctx-verify .claude/skills/ctx-verify
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ctx Verify 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 Ctx Verify 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 Ctx Verify 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.

Verify ctx changes

  1. Inspect the requested behavior and changed surface. Read only the relevant section of CONTRIBUTING.md before selecting checks.
  2. Run the smallest focused tests or deterministic checks that exercise the changed behavior first.
  3. Escalate evidence in proportion to risk:
    • Small, localized change: focused tests, schemas, or diff checks.
    • Material repository change: scripts/no_mistakes_run.sh fast.
    • PR-level, contract, workflow, migration, packaging, security, or release change: run the fast gate, then python scripts/ci_preflight.py --profile pr.
    • Documentation navigation or linked public-asset change: follow the tracker contract in CONTRIBUTING.md; do not require tracker changes for ordinary prose-only edits.
    • Windows-sensitive change: follow the native-CI contract in CONTRIBUTING.md; local checks do not replace required Windows evidence.
  4. Treat the fast gate as committed-history evidence. When the working tree is dirty, pair it with focused checks against the actual uncommitted changes.
  5. If a gate cannot find its trusted pytest, Ruff, and mypy environment, report the environment failure. Do not silently install dependencies or weaken the trust check.
  6. Use an independent validator only when semantic risk remains after deterministic checks, especially for material security, migration, or release work.
  7. Report each check, its result, and any omitted or unavailable evidence.

Rubric

Mark each applicable criterion pass, fail, or not verified:

  • Intent: The artifact satisfies the request without unrelated scope.
  • Behavior: Fresh evidence covers the changed success path and relevant failure or regression paths.
  • Static integrity: Applicable lint, formatting, and type checks pass.
  • Repository contracts: Migration, changed-file, documentation, packaging, and platform requirements remain satisfied where relevant.
  • Evidence quality: Results apply to the actual changed surface and are not stale or inapplicable.
  • Handoff: Skipped checks and residual risks are stated plainly.

Do not claim completion while an applicable criterion fails. Treat missing required evidence as not verified, not as a pass.

Frequently asked questions

What does the Ctx Verify AI skill do?

Select proportional validation for changes or reviews in the ctx repository. Use before handing off material code, workflow, migration, documentation, security, packaging, or release changes; before a PR; or when asked whether a change is adequately tested. Do not use for pure questions with no changed artifact.

Why use Ctx Verify on TypingMind?

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

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

Which AI models can use Ctx Verify?

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 Ctx Verify?

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

Is the Ctx Verify AI skill free?

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