Web Application Testing
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
A skill your agent uses when a SPEC, INNOVATE, or VALIDATE (Layer 2) approach hinges on an unverified runtime/library/external mechanism: run a probe from the 8-family taxonomy and produce a…
Install Vc Feasibility Test
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-feasibility-test -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-feasibility-test --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-feasibility-test .claude/skills/vc-feasibility-test && 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-feasibility-test" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-feasibility-test into .claude/skills/vc-feasibility-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-feasibility-test", 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-feasibility-testType 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-feasibility-test -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-feasibility-test --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-feasibility-test .agents/skills/vc-feasibility-test && 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-feasibility-test" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-feasibility-test into .agents/skills/vc-feasibility-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-feasibility-test", 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-feasibility-test -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-feasibility-test --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-feasibility-test .cursor/skills/vc-feasibility-test && 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-feasibility-test" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-feasibility-test into .cursor/skills/vc-feasibility-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-feasibility-test", 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-feasibility-test--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-feasibility-test -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-feasibility-test --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-feasibility-test .gemini/skills/vc-feasibility-test && 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-feasibility-test" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-feasibility-test into .gemini/skills/vc-feasibility-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-feasibility-test", 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-feasibility-testInstalls 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-feasibility-test -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-feasibility-test .github/skills/vc-feasibility-test && 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-feasibility-test" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-feasibility-test into .github/skills/vc-feasibility-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-feasibility-test", 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-feasibility-test -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-feasibility-test --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-feasibility-test .opencode/skills/vc-feasibility-test && 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-feasibility-test" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-feasibility-test into .opencode/skills/vc-feasibility-test/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-feasibility-test", 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-feasibility-test- GitHub stars
- 1.1k
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,054 words
- Files
- 5 (incl. scripts)
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a SPEC, INNOVATE, or VALIDATE (Layer 2) approach hinges on an unverified runtime/library/external mechanism: run a probe from the 8-family taxonomy and produce a…
- Works in 8 steps: Read the hypothesis from the… → Pick the probe family (1–8) and its cost… → Confirm the safety gate for that cost… → …
- VALIDATE (Layer
- SKILL.md covers Boundary vs…, When To Invoke, Skill Executor and Probe-Method Taxonomy (pick…, plus 5 more sections
- Runs JavaScript scripts from its folder; calls docker, wrangler and pnpm
What it does
Vc Feasibility Test is an agent skill from withkynam/vibecode-pro-max-kit. Use when a SPEC, INNOVATE, or VALIDATE (Layer 2) approach hinges on an unverified runtime/library/external mechanism: run a probe from the 8-family taxonomy and produce a VIABLE/NOT-VIABLE/INCONCLUSIVE VERDICT artifact.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts (for example `scripts/fixtures/validate-feasibility-verdict/fail.md`, `scripts/fixtures/validate-feasibility-verdict/pass-pvl.md` and `scripts/fixtures/validate-feasibility-verdict/pass.md`).
It sits in Testing & QA. The repository describes itself as: Your AI forgets. This remembers. Spec-driven coding harness for vibecoders, product owners, CEOs and real builders — self-improving context memory, 15 agents, 33 skills working…. The licence is MIT.
When your agent uses it
- VALIDATE (Layer
Example prompts
- “/vc-feasibility-test”
Requirements
- Node.js
- Docker
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Read the hypothesis from the VC-FEASIBILITY-PROBE-NEEDED signal
- Pick the probe family (1–8) and its cost class
- Confirm the safety gate for that cost class is met. If not → write an
- Design the minimal probe within that family
- Run the probe empirically — capture actual output, not expected output
- Analyze the evidence: does it confirm or refute the hypothesis?
- Assign a verdict: VIABLE | NOT-VIABLE | INCONCLUSIVE
- Write the VERDICT artifact to the active task folder
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 4 files in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
dockerwranglerpnpmbun
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, wrangler and pnpm, which can reach the network depending on how they are called.
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
Vc Feasibility Test loads about 2.4k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 1,054 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). 1,054 words, ~2,387 tokens.
Download SKILL.mdSave it as
.claude/skills/vc-feasibility-test/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- vc-feasibility-test
- description
- Use when a SPEC, INNOVATE, or VALIDATE (Layer 2) approach hinges on an unverified runtime/library/external mechanism: run a probe from the 8-family taxonomy and produce a VIABLE/NOT-VIABLE/INCONCLUSIVE VERDICT artifact.
- argument-hint
- [hypothesis] [task-folder] [probe-family]
- trigger_keywords
- feasibility, spike, verify assumption, probe mechanism, empirical check, unverified mechanism, does this work, runtime quirk, api shape check
- layer
- contract
- metadata.author
- vibecode-pro-max-kit
- metadata.version
- 2.0.0
vc-feasibility-test
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
One-shot empirical probe skill. Used when SPEC or INNOVATE encounters an approach hinging on an unverified external/runtime/library mechanism — the question is "does this mechanism actually work the way the design assumes?", asked before the decision locks.
Boundary vs vc-test-coverage-plan
These two skills are complementary and must not be confused:
vc-feasibility-test(this skill) = PRE-decision. "Does the mechanism work at all?" Run before SPEC/INNOVATE locks an approach, when the answer is unknown. Output: a one-shot VERDICT artifact.vc-test-coverage-plan= POST-plan. "How do I cover this blast radius across the 4 test tiers?" Run after a plan exists, when the design is already chosen. Output: a per-area tier table.
If the approach is already decided and you are assigning test tiers → use
vc-test-coverage-plan. If you cannot decide because a mechanism is unverified →
use this skill first.
When To Invoke
- When vc-spec-agent, vc-innovate-agent, or a vc-validate-agent Layer 2 dimension agent emits
VC-FEASIBILITY-PROBE-NEEDED - When a mechanism cannot be verified from source code alone
- One-shot: not an iterative loop (use vc-autoresearch for iteration)
Skill Executor
Always executed by vc-debugger (via the VC-FEASIBILITY-PROBE-NEEDED signal routing
in orchestration.md). SPEC, INNOVATE, and VALIDATE Layer 2 agents do not run probes themselves.
Probe-Method Taxonomy (pick one family)
Every probe belongs to one of these 8 families. Name the chosen family in the VERDICT. Each family has a default cost/safety class (see next section) — the probe inherits it.
| # | Family | What it probes | Typical method | Default cost class |
|---|---|---|---|---|
| 1 | Local process / Node script | pure library/runtime behavior in isolation | run a .mjs/Bun script, regex/parse check, call the lib fn directly | cheap-local |
| 2 | Unit/integration test harness | behavior under the project's own test runner | pnpm --filter … test (Vitest) or bun test on a scratch case | cheap-local |
| 3 | tRPC / Prisma / DB query | route shape, query behavior, index/constraint semantics | hit a tRPC route or run a Prisma/raw-SQL query against a test DB | needs-container (only if it needs the live app DB) / else cheap-local |
| 4 | External API shape capture | real response shape/behavior of a 3rd-party API | one live request to OpenRouter / Stripe / Composio / Clerk / Bright Data | needs-live-provider |
| 5 | Container exec / internal-port curl | in-container service behavior, proxy injection, file-server, supervisord | docker exec … curl http://localhost:{port} on a disposable container | needs-container |
| 6 | Browser / CDP capture | anti-detect quirks, CDP events, SPA nav, popup behavior | Playwright/CDP client, page.on(...), snapshot | needs-browser |
| 7 | WS / SSE handshake & timing | gateway WS framing, SSE delivery/reconnect, JSONL shape | raw ws/EventSource client + frame/timing capture | needs-container (if against in-container service) / else cheap-local |
| 8 | Cloudflare worker runtime | KV staleness, step-replay/idempotency, edge JWT verify | wrangler dev + curl, deploy a throwaway worker | needs-cf |
If none of the 8 fit, the question is probably not a feasibility probe — reconsider
whether vc-research-agent (unknown context) or vc-test-coverage-plan (known
design) is the right tool instead.
Probe Cost / Safety Class (MANDATORY GATE)
Every VERDICT declares one cost class. The class governs whether the probe may run
unattended or needs explicit opt-in. A probe that cannot be run within its safety
gate produces an INCONCLUSIVE verdict — it is never silently skipped or faked.
| Cost class | Safety gate | If gate not met |
|---|---|---|
| cheap-local | none — run freely (local script, test harness, parse check) | n/a |
| needs-container | use a disposable container only. NEVER docker exec the shared dev container (app-*) or shared Postgres. Disposable live-E2E containers need the disposable-cleanup env gate enabled. | verdict INCONCLUSIVE, note "no disposable container available" |
| needs-live-provider | requires explicit double opt-in from the user before any billed/live 3rd-party call (OpenRouter, Stripe, Composio, Bright Data, Clerk). Default local mode is BYOK Mistral. | verdict INCONCLUSIVE, note "live-provider opt-in not granted" |
| needs-browser | a browser/CDP session must be available; never drive a shared user session | verdict INCONCLUSIVE, note "no browser session available" |
| needs-cf | a wrangler dev/throwaway-worker sandbox; never touch a deployed production worker | verdict INCONCLUSIVE, note "no CF sandbox available" |
The emitted VC-FEASIBILITY-PROBE-NEEDED signal SHOULD carry the anticipated cost
class so the orchestrator can resolve the opt-in gate before dispatching vc-debugger
(see orchestration.md §VC-FEASIBILITY-PROBE-NEEDED Signal Routing).
Show full SKILL.md (399 more words)Show less
Probe Execution Steps
- Read the hypothesis from the
VC-FEASIBILITY-PROBE-NEEDEDsignal - Pick the probe family (1–8) and its cost class
- Confirm the safety gate for that cost class is met. If not → write an
INCONCLUSIVEverdict with the gate-not-met reason and stop. Do NOT escalate to a higher-cost probe or run against a shared resource. - Design the minimal probe within that family
- Run the probe empirically — capture actual output, not expected output
- Analyze the evidence: does it confirm or refute the hypothesis?
- Assign a verdict:
VIABLE|NOT-VIABLE|INCONCLUSIVE - Write the VERDICT artifact to the active task folder
VERDICT Artifact Format
Filename: {slug}_FEASIBILITY_{dd-mm-yy}.md
Location: same active task folder as the SPEC/plan that triggered the probe
Required frontmatter fields (MUST be present — validated by validate-feasibility-verdict.mjs):
---
slug: [task-slug]
date: YYYY-MM-DD
verdict: VIABLE | NOT-VIABLE | INCONCLUSIVE
originating-phase: spec | innovate | pvl
---The originating-phase: field is REQUIRED. Valid values:
spec— probe triggered by vc-spec-agent ([SP3])innovate— probe triggered by vc-innovate-agent ([I2.5])pvl— probe triggered by vc-validate-agent Layer 2 ([V2-PROBE])
Required sections (MUST be present — validated by validate-feasibility-verdict.mjs):
Hypothesis
One-sentence statement of what is being tested.
Mechanism Under Test
The specific external, runtime, or library behavior being probed.
Probe Family
One of the 8 families above (e.g. 5 — Container exec / internal-port curl).
Probe Cost Class
One of: cheap-local | needs-container | needs-live-provider | needs-browser | needs-cf.
State whether the safety gate was met.
Probe Method
The exact command(s) or steps run to test the hypothesis.
Evidence Captured
The raw output from the probe (trimmed to relevant lines). For an INCONCLUSIVE
gate-not-met verdict, state explicitly that the probe was not run and why.
Verdict
One of: VIABLE | NOT-VIABLE | INCONCLUSIVE
Resulting Design Constraint
The "action consequence" of the probe, split into three explicit parts:
- What this licenses: what the approach is now allowed to depend on.
- What this forbids: what the approach must NOT depend on.
- What remains uncertain (known-gap): what the probe did not settle and must be
treated as an open risk (for
INCONCLUSIVE, this is the main content).
Completion Signal
After writing the VERDICT artifact, emit:
VC-FEASIBILITY-VERDICT-READY: [verdict keyword] — [full path to VERDICT file]Example:
VC-FEASIBILITY-VERDICT-READY: NOT-VIABLE — process/features/model-selector/active/model-selector_10-06-26/model-selector_FEASIBILITY_10-06-26.mdRe-spawn Handoff
The orchestrator reads the VERDICT artifact and extracts a Prior Feasibility: summary.
Format passed to the re-spawned agent:
Prior Feasibility: [hypothesis] — verdict: [VIABLE|NOT-VIABLE|INCONCLUSIVE] — licenses: [one line] — forbids: [one line] — uncertain: [one line]Example:
Prior Feasibility: Does the gateway forward params.provider.sort? — verdict: NOT-VIABLE — licenses: nothing new — forbids: any approach depending on params.provider.sort being forwarded (the layer strips it) — uncertain: whether a different forwarding field survivesThe re-spawned SPEC, INNOVATE, or VALIDATE agent reads this block and uses the verdict to lock or reject the approach. When originating-phase: pvl, the re-spawned vc-validate-agent resumes from V1 and records resolved probes in a ## Feasibility Probes Resolved subsection of the validate-contract (omitted when no probe ran).
© 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 4 other files (scripts) in .claude/skills/vc-feasibility-test of withkynam/vibecode-pro-max-kit.
- SKILL.md
- scripts/fixtures/validate-feasibility-verdict/fail.md
- scripts/fixtures/validate-feasibility-verdict/pass-pvl.md
- scripts/fixtures/validate-feasibility-verdict/pass.md
- scripts/validate-feasibility-verdict.mjs
Open the folder on GitHubat commit 3bcb2f9
Compare with similar skills
Vc Feasibility Test 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 |
|---|---|---|---|---|---|---|
| Vc Feasibility Test this skillwithkynam/vibecode-pro-max-kit | 1.1k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Web Application Testinganthropics/skills | 180k | 51 repos | ~966 | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Bugsfossasia/eventyay-interpretation | 1.6k | 32 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| TDDpietheinstrengholt/rssmonster | 564 | 30 repos | ~906 | Automated safety check: Pass | MIT | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| TDDsanity-io/sanity | 6.4k | 20 repos | ~1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Diagnosing Bugs
fossasia/eventyay-interpretation
Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.
TDD
pietheinstrengholt/rssmonster
Test-driven development. An agent skill from pietheinstrengholt/rssmonster.
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
- Official
TDD
sanity-io/sanity
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
Context Driven Development
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
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
Categories
Questions about Vc Feasibility Test
What does Vc Feasibility Test do?
A skill your agent uses when a SPEC, INNOVATE, or VALIDATE (Layer 2) approach hinges on an unverified runtime/library/external mechanism: run a probe from the 8-family taxonomy and produce a…. Vc Feasibility Test is an agent skill from withkynam/vibecode-pro-max-kit. Use when a SPEC, INNOVATE, or VALIDATE (Layer 2) approach hinges on an unverified runtime/library/external mechanism: run a probe from the 8-family taxonomy and produce a VIABLE/NOT-VIABLE/INCONCLUSIVE VERDICT artifact.
When should I use Vc Feasibility Test?
Vc Feasibility Test fits situations like: VALIDATE (Layer.
How do I install Vc Feasibility Test in Claude Code?
Run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-feasibility-test -a claude-code`. Or copy the skill folder (.claude/skills/vc-feasibility-test in withkynam/vibecode-pro-max-kit) into .claude/skills/vc-feasibility-test in your project. Claude Code loads it when a task matches its description.
How do I install Vc Feasibility Test in Codex?
Run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-feasibility-test -a codex`. Or copy the skill folder (.claude/skills/vc-feasibility-test in withkynam/vibecode-pro-max-kit) into .agents/skills/vc-feasibility-test in your project. Codex loads it when a task matches its description.
Can I use Vc Feasibility Test 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-feasibility-test -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-feasibility-test, .gemini/skills/vc-feasibility-test, .github/skills/vc-feasibility-test and .opencode/skills/vc-feasibility-test in your project.
What does Vc Feasibility Test need to run?
Going by SKILL.md and its folder, Vc Feasibility Test needs JavaScript for the scripts in its folder and the command-line tools its instructions call (docker, wrangler, pnpm and bun). Our summary lists: Node.js; Docker.
Does Vc Feasibility Test access the network?
SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Vc Feasibility Test 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 Vc Feasibility Test use?
Vc Feasibility Test 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 Vc Feasibility Test use?
About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vc Feasibility Test?
Skills that share tags, products or a category with Vc Feasibility Test: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (pietheinstrengholt/rssmonster, 564 stars) and TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vc Feasibility Test?
withkynam (a GitHub user) maintains it in withkynam/vibecode-pro-max-kit, which has 1,145 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.