NanoClaw OneCLI Gateway Installer
nanocoai/nanoclaw
Installs or refreshes OneCLI as the gateway provider for NanoClaw, copying the adapter files, registering the provider and running the setup script.
Generates or refreshes a project's shared repository context file so both Codex and Claude work from the same up-to-date knowledge layer.
Install Repository Context Generator
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-context -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-generate-context --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/vc-generate-context .claude/skills/vc-generate-context && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vc-generate-context" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-context into .claude/skills/vc-generate-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-generate-context", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-contextType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-context -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-generate-context --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/vc-generate-context .agents/skills/vc-generate-context && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vc-generate-context" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-context into .agents/skills/vc-generate-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-generate-context", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-context -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-generate-context --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/vc-generate-context .cursor/skills/vc-generate-context && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vc-generate-context" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-context into .cursor/skills/vc-generate-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-generate-context", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/withkynam/vibecode-pro-max-kit.git --path .claude/skills/vc-generate-context--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-context -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-generate-context --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/vc-generate-context .gemini/skills/vc-generate-context && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vc-generate-context" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-context into .gemini/skills/vc-generate-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-generate-context", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install withkynam/vibecode-pro-max-kit vc-generate-contextInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-context -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/vc-generate-context .github/skills/vc-generate-context && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vc-generate-context" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-context into .github/skills/vc-generate-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-generate-context", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-context -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-generate-context --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/vc-generate-context .opencode/skills/vc-generate-context && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vc-generate-context" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-generate-context into .opencode/skills/vc-generate-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-generate-context", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vc-generate-context- GitHub stars
- 1.1k
- Token cost
- ~817 tokens
- SKILL.md length
- 309 words
- Files
- 3 (incl. scripts, references)
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generates or refreshes a project's shared repository context file so both Codex and Claude work from the same up-to-date knowledge layer.
- Works in 8 steps: Read references/generate-context.md for… → Determine mode → Read process/context/all-context.md when… → …
- Refreshing stale or missing repository context documentation
- SKILL.md covers Workflow, Rules and Invocation Modes
- Runs JavaScript scripts from its folder; calls node
What it does
It maintains a central context file plus grouped context files for detected or approved areas, choosing a full scan when the central file is missing and a delta update when it already exists; an optional input can target one package, app, feature or architectural area to refresh first. Generating it means inspecting current repo state, active plans, feature folders, package scripts and important architecture files alongside any existing grouped docs, then writing the output with a scan timestamp, the repo's current commit, what changed since the last update, open questions and source references.
After writing, it runs a bundled validation script and treats a failure as a blocker before calling the context refreshed; if routing or grouped context changed, it also runs a second script that checks context discovery. The central file itself is treated as a durable routing protocol never to be replaced with generated prose, and stale or mis-grouped docs are flagged to a separate audit skill rather than being rewritten directly here.
When your agent uses it
- Refreshing stale or missing repository context documentation
- Generating a context file for one specific package or feature area
- Validating that generated context passes the project's own checks
Example prompts
- “Regenerate the repository context since the auth module changed.”
- “Refresh just the context for the billing package.”
- “Validate that our context files are still discoverable after this change.”
Requirements
- Node.js to run the bundled validation scripts
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Read references/generate-context.md for the full context contract.
- Determine mode
- Read process/context/all-context.md when present to identify relevant grouped context files.
- Inspect current repo state, active plans, feature folders, package scripts, tooling, important architecture files, and relevant…
- Produce process/context/all-context.md PLUS process/context/{group}/all-{group}.md for each detected or approved group (see Invocation…
- Include scan timestamp, repo HEAD if available, changes since last update, open questions, and source references.
- Validate the generated context
- If routing or grouped context changed, also run
What it can do on your machine
Read from SKILL.md and the folder at commit 3bcb2f9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Repository Context Generator loads about 817 tokens when it runs, and up to ~3.2k if it reads all its reference files. Until then it costs about 47 tokens; SKILL.md has 309 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from withkynam/vibecode-pro-max-kit at commit 3bcb2f9, republished under its MIT licence (© withkynam). 309 words, ~817 tokens.
Download SKILL.mdSave it as
.claude/skills/vc-generate-context/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- vc-generate-context
- description
- Generate or update the project's authoritative repository context at process/context/all-context.md. Use when repo context is missing, stale, or contradicted by code.
- trigger_keywords
- generate context, update context, refresh context, missing context
- layer
- contract
- metadata.author
- vibecode-pro-max-kit
- metadata.version
- 1.0.0
Generate 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 maintain process/context/all-context.md, the broad portable project knowledge layer shared by Codex and Claude. Use process/context/all-context.md as the context router before reading grouped docs.
Optional input: a package, app, feature, context group, or architectural area to refresh first.
Workflow
- Read
references/generate-context.mdfor the full context contract. - Determine mode:
- Full scan when
process/context/all-context.mdis missing. - Delta update when it exists.
- Full scan when
- Read
process/context/all-context.mdwhen present to identify relevant grouped context files. - Inspect current repo state, active plans, feature folders, package scripts, tooling, important architecture files, and relevant
process/context/**/*.mddocs. - Produce
process/context/all-context.mdPLUSprocess/context/{group}/all-{group}.mdfor each detected or approved group (see Invocation Modes below). - Include scan timestamp, repo HEAD if available, changes since last update, open questions, and source references.
- Validate the generated context:
bash node .claude/skills/vc-generate-context/scripts/validate-all-context.mjs - If routing or grouped context changed, also run:
bash node .claude/skills/vc-audit-context/scripts/validate-context-discovery.mjs
Rules
- Treat
process/context/as durable cross-agent knowledge. - Treat
process/context/all-context.mdas the durable routing protocol; do not replace it with generated prose. - Do not store agent-specific mechanics here unless they affect project workflow.
- Do not rewrite grouped context docs; if they are stale or mis-grouped, flag
audit-context. - Prefer concise, factual, path-specific documentation.
- Use
pnpmterminology for package management. - Treat validation failures as blockers before presenting context as refreshed.
Invocation Modes
| Mode | Trigger | Group-detection | Output |
|---|---|---|---|
setup-delegation | Called by vc-setup passing an approved-groups list | Skip re-detection; use the list provided | all-context.md + all-{group}.md for each approved group |
standalone-full | Direct invocation with no groups list | Self-detect groups via the detection table in references/generate-context.md | all-context.md + all-{group}.md for all detected groups |
delta | Invoked when context already exists; update context | Self-detect; create MISSING groups only; warn on unrecognized; never delete | all-context.md updated + any new all-{group}.md files created |
See references/generate-context.md for per-mode instructions, the Context Group Detection Table, and delta-mode group-creation rules.
© withkynam, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (scripts, references) in .claude/skills/vc-generate-context of withkynam/vibecode-pro-max-kit.
- SKILL.md
- references/generate-context.md
- scripts/validate-all-context.mjs
Open the folder on GitHubat commit 3bcb2f9
Compare with similar skills
Repository Context Generator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Repository Context Generator this skillwithkynam/vibecode-pro-max-kit | 1.1k | — | ~817 | Automated safety check: Pass | MIT | |
| NanoClaw OneCLI Gateway Installernanocoai/nanoclaw | 31k | — | ~1.1k | Automated safety check: Notes | MIT | |
| ccc Semantic Code Searchcocoindex-io/cocoindex-code | 2.7k | — | ~938 | Automated safety check: Pass | Apache-2.0 | |
| Context Engineeringabashev/vfs-s3 | 106 | 9 repos | ~2.6k | Automated safety check: Notes | Apache-2.0 | |
| Repomix Codebase Packeryamadashy/repomix | 29k | — | ~1.3k | Automated safety check: Notes | MIT | |
| Codebase Handbook BuilderRuhan-Wang/Harness_Handbook | 331 | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
ccc Semantic Code Search
cocoindex-io/cocoindex-code
Semantic code search and index management with the ccc CLI: the agent initializes, indexes and queries the project by concept, filtering by language or path.
Context Engineering
abashev/vfs-s3
Optimizes agent context setup. An agent skill from abashev/vfs-s3.
Repomix Codebase Packer
yamadashy/repomix
Packs a local directory or remote GitHub repository into one AI-friendly file with Repomix, then searches it to explore structure, find patterns and count tokens.
Codebase Handbook Builder
Ruhan-Wang/Harness_Handbook
Generates, refreshes, validates and uses a compact handbook that maps where a change touches in a repository, using the active Codex session and no external LLM API.
Codemap
JordanCoin/codemap
Gives an agent a quick map of a codebase's structure, dependencies, changes and handoffs, and tunes per-project config so the output stays code-first.
More from withkynam/vibecode-pro-max-kit
All 32 skills in this repoLibrary Documentation Seeker
withkynam/vibecode-pro-max-kit
Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.
Vc Sequential Thinking
withkynam/vibecode-pro-max-kit
Apply step-by-step analysis for complex problems with revision capability.
Agent Browser Automation
withkynam/vibecode-pro-max-kit
Drives a browser through the agent-browser CLI, using compact snapshots with element refs to keep context small in long sessions, plus video recording and cloud browsers.
Context Routing Audit
withkynam/vibecode-pro-max-kit
Audits a project's context routing, skill discoverability and skill wiring by running a chain of validator scripts and fixing whatever they report.
Active Plan Audit
withkynam/vibecode-pro-max-kit
Reviews a codebase's active plan files for staleness and completion, then archives only the ones confirmed done or obsolete against the real code.
Systematic Debugging and Investigation
withkynam/vibecode-pro-max-kit
Forces root-cause investigation before any fix, combining a four-phase debugging method with log, CI and performance investigation techniques and a rule against unverified completion claims.
Related
Works with
Categories
Questions about Repository Context Generator
What does Repository Context Generator do?
Generates or refreshes a project's shared repository context file so both Codex and Claude work from the same up-to-date knowledge layer. It maintains a central context file plus grouped context files for detected or approved areas, choosing a full scan when the central file is missing and a delta update when it already exists; an optional input can target one package, app, feature or architectural area to refresh first. Generating it means inspecting current repo state, active plans, feature folders, package scripts and important architecture files alongside any existing grouped docs, then writing the output with a scan timestamp, the repo's current commit, what changed since the last update, open questions and source references.
When should I use Repository Context Generator?
Repository Context Generator fits situations like: refreshing stale or missing repository context documentation; generating a context file for one specific package or feature area; validating that generated context passes the project's own checks.
How do I install Repository Context Generator in Claude Code?
Run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-context -a claude-code`. Or copy the skill folder (.claude/skills/vc-generate-context in withkynam/vibecode-pro-max-kit) into .claude/skills/vc-generate-context in your project. Claude Code loads it when a task matches its description.
How do I install Repository Context Generator in Codex?
Run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-context -a codex`. Or copy the skill folder (.claude/skills/vc-generate-context in withkynam/vibecode-pro-max-kit) into .agents/skills/vc-generate-context in your project. Codex loads it when a task matches its description.
Can I use Repository Context Generator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-generate-context -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vc-generate-context, .gemini/skills/vc-generate-context, .github/skills/vc-generate-context and .opencode/skills/vc-generate-context in your project.
What does Repository Context Generator need to run?
Going by SKILL.md and its folder, Repository Context Generator needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js to run the bundled validation scripts.
Does Repository Context Generator access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Repository Context Generator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Repository Context Generator use?
Repository Context Generator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Repository Context Generator use?
About 817 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.
What are the alternatives to Repository Context Generator?
Skills that share tags, products or a category with Repository Context Generator: NanoClaw OneCLI Gateway Installer (nanocoai/nanoclaw, 31k stars), ccc Semantic Code Search (cocoindex-io/cocoindex-code, 2.7k stars), Context Engineering (abashev/vfs-s3, 106 stars) and Repomix Codebase Packer (yamadashy/repomix, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Repository Context Generator?
withkynam (a GitHub user) maintains it in withkynam/vibecode-pro-max-kit, which has 1,144 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on June 21, 2026.
Source: withkynam/vibecode-pro-max-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.