Install any skill in seconds. Free to start, no credit card required.
Get Started Free →withkynam/vc-context-discovery
Discover and load all relevant context for the current task. Lists feature group nested files with full paths, loads process/context/ files by domain routing. Called at the start of every agent session.
Passed 14 of 21 test cases with the skill, and 3 of 21 without it.
and 19 more in the full report
15 fixed2 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
If the discover-context.mjs script is unavailable, what exact CLI command should be run first to list all context files in sorted order?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies find process/context/ -type f | sort. | Missed | Passed |
The instructions your model reads when the skill loads.
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Discover and load all relevant context for the current task. This skill lists feature group nested files with full paths and loads process/context/ files by domain routing table. It is the canonical context-loading entrypoint for every agent session.
At the start of every agent session (research, innovate, plan, validate, execute, update-process, fast-mode). Also at the start of any skill that needs repo context before operating.
Document the canonical schemas for three file types used across the repo. These schemas enable frontmatter-aware routing and filtering.
Context file frontmatter schema:
name: context:{slug}
description: "one-line scope — used by vc-context-discovery for routing"
keywords: comma, separated, task, vocabulary, terms # drives grep-first keyword routing
related: [context:{other-slug}, context:{another-slug}] # sibling/cross-group links (optional)
date: dd-mm-yy
keywords — strongly recommended, non-empty. Comma-separated task-vocabulary terms an
agent would use to describe a task this doc serves (e.g. session, token, refresh, jwt, login). This is the match surface for discover-context.mjs --match; weak/absent
keywords are why a relevant doc never gets routed to. Lint WARNS when empty (so existing
projects don't break on sync) — backfill at UPDATE-PROCESS.related — OPTIONAL list of context:{slug} values for sibling docs that are usually
needed together (the markdown-native equivalent of cross-links). Every slug listed MUST
resolve to a real context: doc; dangling links fail lint. Discovery follows these after
the primary match so a task touching two domains loads both.Plan file frontmatter schema:
name: plan:{slug}
description: "one-line scope and feature"
date: dd-mm-yy
feature: {feature-folder-name}
phase: "{phase-id}" # optional, for phase program plans only
test cases passed, vs 3 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.