Vc Audit Context

CommunityPopular

withkynam

vc-audit-context

Audit project context routing, shared-skill discoverability, and Claude/Codex wiring. Use when context docs or skill surfaces move, split, or drift.

Overview

Publisher	withkynam
Repository	`vibecode-pro-max-kit`
Skill name	`vc-audit-context`
Stars	1.1K
Forks	234
Bundled files	11
License	MIT
Links	Skill source Repository

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.
11 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by withkynam on GitHub. Read the source before you install it.

Installation

Install the Vc Audit Context 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.
https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-audit-context
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-audit-context

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

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/withkynam/vibecode-pro-max-kit.git /tmp/vibecode-pro-max-kit
mkdir -p .claude/skills
cp -r /tmp/vibecode-pro-max-kit/.claude/skills/vc-audit-context .claude/skills/vc-audit-context

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

Use it in TypingMind

Enable Vc Audit Context 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 Vc Audit Context 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 Vc Audit Context 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.

Audit Context

Output style: Follow process/development-protocols/communication-standards.md — answer-first, plain language, no unexplained jargon, TL;DR on long responses.

Use this skill to verify that the project's durable context layer is discoverable and organized.

Optional input: a context group, agent, skill, or folder scope to prioritize during the audit.

Workflow

Run find process/context/ -type f | sort to get the full file listing before routing. This ensures no context file is silently skipped when the router is incomplete or drifted.
Read process/context/all-context.md for the context routing protocol.
Read references/audit-context.md for the full audit process.

Run the context discovery validator:

bash
node .claude/skills/vc-audit-context/scripts/validate-context-discovery.mjs

3a. Run the protocol discovery frontmatter validator (enforces discovery frontmatter on every process/development-protocols/**/*.md, recursive incl. vc-system-behavior/; note.md is the only intentional exclusion):

bash
node .claude/skills/vc-audit-context/scripts/validate-protocol-discovery.mjs

Run the shared skill routing coverage validator:

bash
node .claude/skills/vc-audit-context/scripts/validate-skill-routing.mjs

Run the skill cross-reference validator:

bash
node .claude/skills/vc-audit-context/scripts/validate-skill-cross-refs.mjs

Run the skill dependency/confusable analysis:

bash
node .claude/skills/vc-audit-context/scripts/validate-skill-dependencies.mjs
node .claude/skills/vc-audit-context/scripts/validate-confusable-skills.mjs

Regenerate or check the machine-readable skill catalog:

bash
node .claude/skills/vc-audit-context/scripts/generate-skills-catalog.mjs --write
node .claude/skills/vc-audit-context/scripts/generate-skills-catalog.mjs --check

Validate that every SKILL.md carries trigger_keywords + a valid layer (contract|helper) and that the catalog is in sync:

bash
node .claude/skills/vc-audit-context/scripts/validate-skill-keywords.mjs

If any script reports failures, inspect the referenced files and patch the smallest relevant surface.
Re-run the failed validators until they pass.

For agent/skill harness validation (agent parity, skill frontmatter, README.md sync, protocol wiring), use the audit-vc skill.

Context Bootstrap (when process/context/ doesn't exist or needs full init)

Use when initializing a new project's context layer from scratch:

Run vc-scout in parallel across major source directories (skip .git, node_modules, .claude, caches) to gather codebase summaries.
Create process/context/all-context.md (routing table, architecture, conventions) and group all-{group}.md entrypoints for any durable domains identified.
Parallel reader strategy for existing context files — before updating, spawn subagents proportional to file count: 1-3 files read directly; 4-6 files use 2-3 reader agents; 7+ files use 4-5 reader agents (max 5), distributing by LOC.
After generating or updating context files, run find process/context -name '*.md' -print0 | xargs -0 wc -l | sort -rn — files over 800 LOC should be split into a context group or the user asked.
Finish by running the discovery validator (step 3 above) before declaring done.

Rules

Treat .claude/skills/ as canonical; .agents/skills/ is the Codex discovery symlink.
Treat .claude/skills/vc-audit-context/references/skill-routing-policy.json as the explicit allowlist for intentionally non-routed shared skills.
Do not move large context files without updating process/context/all-context.md.
Do not delete compatibility wrappers unless no current reference points to them.
Keep context groups durable-domain based, not one group per temporary feature.
When updating agents, mirror Claude markdown and Codex TOML surfaces together.
Treat validator warnings as audit findings unless the user asks for a strict cleanup.
Prefer validator-backed routing truth over adding more soft prose.
Treat process/context/generated-skills-catalog.json as the machine-readable catalog owned by audit-context.

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 Vc Audit Context AI skill do?

Audit project context routing, shared-skill discoverability, and Claude/Codex wiring. Use when context docs or skill surfaces move, split, or drift.

Why use Vc Audit Context on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-audit-context. 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 Vc Audit Context?

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 Vc Audit Context?

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

Is the Vc Audit Context AI skill free?

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

Openclaw Testing

openclaw

OrganizationPopular

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Release Openclaw Ci

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

Release Openclaw Mac

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Release Openclaw Maintainer

openclaw

OrganizationPopular

Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Audit Context

Workflow

Context Bootstrap (when process/context/ doesn't exist or needs full init)

Rules

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now