How do I install the Vc:audit Context skill?

Run npx skillmds@latest add opencue/vc-audit-context in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vc:audit Context safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vc:audit Context?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vc:audit Context free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vc:audit Context?

opencue (@opencue) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vc:audit Context by opencue — Agent Skill

Name: Vc:audit Context
Author: opencue

File contents

Audit Context

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

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

Workflow

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:

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

Run the shared skill routing coverage validator:

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

Run the skill cross-reference validator:

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

Run the skill dependency/confusable analysis:

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

Regenerate or check the machine-readable skill catalog:

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

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.

Rules

Treat .Codex/skills/ as canonical; .agents/skills/ is the Codex discovery symlink.
Treat .Codex/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 Codex 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.

---name: vc-audit-contextdescription: Audit Flowser context routing, shared-skill discoverability, and Codex/Codex wiring. Use when context docs or skill surfaces move, split, or drift.---# Audit ContextUse this skill to verify that Flowser's durable context layer is discoverable and organized.Optional input: a context group, agent, skill, or folder scope to prioritize during the audit.## Workflow1. Read `process/context/all-context.md` for the context routing protocol.2. Read `references/audit-context.md` for the full audit process.3. Run the context discovery validator: ```bash node .Codex/skills/vc-audit-context/scripts/validate-context-discovery.mjs ```4. Run the shared skill routing coverage validator: ```bash node .Codex/skills/vc-audit-context/scripts/validate-skill-routing.mjs ```5. Run the skill cross-reference validator: ```bash node .Codex/skills/vc-audit-context/scripts/validate-skill-cross-refs.mjs ```6. Run the skill dependency/confusable analysis: ```bash node .Codex/skills/vc-audit-context/scripts/validate-skill-dependencies.mjs node .Codex/skills/vc-audit-context/scripts/validate-confusable-skills.mjs ```7. Regenerate or check the machine-readable skill catalog: ```bash node .Codex/skills/vc-audit-context/scripts/generate-skills-catalog.mjs --write node .Codex/skills/vc-audit-context/scripts/generate-skills-catalog.mjs --check ```8. If any script reports failures, inspect the referenced files and patch the smallest relevant surface.9. 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.## Rules- Treat `.Codex/skills/` as canonical; `.agents/skills/` is the Codex discovery symlink.- Treat `.Codex/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 Codex 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`.

Frequently asked questions

Vc:audit Context