Web Application Testing
anthropics/skills
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
Structured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing.
Install Workflow
$ npx skills add notque/vexjoy-agent --skill workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install notque/vexjoy-agent workflow --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/notque/vexjoy-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/process/workflow .claude/skills/workflow && 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 "workflow" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/process/workflow into .claude/skills/workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow", 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/notque/vexjoy-agent/tree/main/skills/process/workflowType 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 notque/vexjoy-agent --skill workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install notque/vexjoy-agent workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/process/workflow .agents/skills/workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "workflow" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/process/workflow into .agents/skills/workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow", 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 notque/vexjoy-agent --skill workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install notque/vexjoy-agent workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/process/workflow .cursor/skills/workflow && 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 "workflow" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/process/workflow into .cursor/skills/workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow", 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/notque/vexjoy-agent.git --path skills/process/workflow--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 notque/vexjoy-agent --skill workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install notque/vexjoy-agent workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/process/workflow .gemini/skills/workflow && 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 "workflow" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/process/workflow into .gemini/skills/workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow", 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 notque/vexjoy-agent workflowInstalls 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 notque/vexjoy-agent --skill workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/process/workflow .github/skills/workflow && 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 "workflow" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/process/workflow into .github/skills/workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow", 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 notque/vexjoy-agent --skill workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install notque/vexjoy-agent workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/notque/vexjoy-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/process/workflow .opencode/skills/workflow && 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 "workflow" agent skill from https://github.com/notque/vexjoy-agent/tree/main/skills/process/workflow into .opencode/skills/workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workflow", 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
workflow- GitHub stars
- 435
- Token cost
- ~3.1k tokens
- SKILL.md length
- 1,204 words
- Files
- 156 (incl. references)
- Skills in repo
- 61
- Repo updated
- First seen
- Licence
- MIT
At a glance
Structured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing.
- Works in 11 steps: SPEC → STATE → ITERATE → …
- Testing & QA work in your project
- SKILL.md covers Mode Selection, Feature Lifecycle, Planning and Objective Loop, plus 3 more sections
- Runs Python and JavaScript scripts from its folder; calls python3
What it does
Workflow is an agent skill from notque/vexjoy-agent. Structured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing.
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 162 other files, including reference files (for example `references/adr-template.md`, `references/agent-upgrade.md` and `references/article-evaluation-pipeline.md`).
It sits in Testing & QA. The repository describes itself as: VexJoy AI Agent with Jev Intelligent Routing - /do routes plain-English requests to the right specialist agent and gates the work with reviews, tests, and a learning loop. The licence is MIT.
When your agent uses it
- Testing & QA work in your project
Example prompts
- “/workflow”
Requirements
- Python 3
- Node.js
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep, Skill, Agent, Task
Workflow steps
11 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5218674. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBashGlobGrepSkillAgentTask
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Python and JavaScript, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
python3
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
Workflow loads about 3.1k tokens when it runs, and up to ~285k if it reads all its reference files. Until then it costs about 26 tokens; SKILL.md has 1,204 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Skill, Agent, Task
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from notque/vexjoy-agent at commit 5218674, republished under its MIT licence (© notque). 1,204 words, ~3,149 tokens.
Download SKILL.mdSave it as
.claude/skills/workflow/SKILL.md (or your agent's skills folder). This skill also uses 155 other files; get the full folder from GitHub.- name
- workflow
- description
- Structured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing.
- allowed-tools
- Read, Write, Edit, Bash, Glob, Grep, Skill, Agent, Task
- user-invocable
- true
- context
- fork
- routing.force_route
- true
- routing.not_for
- code review (use review), testing (use testing), security (use security)
- routing.triggers
- workflow, multi-phase task, feature design, feature plan, feature implement, build feature end to end, full feature lifecycle, write spec, define…
- routing.category
- process
- routing.pairs_with
- review, testing, security, pr-workflow
Workflow Skill
Five modes for structured multi-phase work. Match the request, follow that mode's instructions.
Mode Selection
| Request pattern | Mode |
|---|---|
| Feature design/plan/implement/validate/release, end-to-end | Feature Lifecycle |
| Write spec, define requirements, create plan, interview, pause/resume | Planning |
| Keep working until, iterate until done, drive to done | Objective Loop |
| Make faster, speed up, reduce latency, profile, hill climb | Hill Climb |
| All other structured workflows: review, debug, refactor, research, create, explore, upgrade | Ad-Hoc Workflow |
Feature Lifecycle
Phase-gated workflow: DESIGN > PLAN > IMPLEMENT > VALIDATE > RELEASE. Each phase must pass its gate before the next begins.
Phase Routing
If .feature/ exists, check state: python3 ~/.claude/scripts/feature-state.py status.
Route to the indicated phase.
If no feature state exists, determine entry from intent:
- "design", "think through", "explore approaches" -> DESIGN
- "plan", "break down", "create tasks" -> PLAN (requires completed design)
- "implement", "execute plan" -> IMPLEMENT (requires completed plan)
- "validate", "quality gates" -> VALIDATE (requires completed implementation)
- "release", "merge", "ship it" -> RELEASE (requires passed validation)
- "end to end", "full lifecycle" -> DESIGN (start from beginning)
Phase References
Load the phase reference, then follow it exactly:
| Phase | Reference | Produces |
|---|---|---|
| DESIGN | references/fl-design.md | design.md |
| PLAN | references/fl-plan.md | Wave-ordered task list |
| IMPLEMENT | references/fl-implement.md | Code changes |
| VALIDATE | references/fl-validate.md | Quality gate report |
| RELEASE | references/fl-release.md | Merged PR |
| End-to-end | references/fl-pipeline.md | Full lifecycle |
| State conventions | references/fl-shared.md | -- |
| Error recovery | references/fl-error-handling.md | -- |
State operations use python3 ~/.claude/scripts/feature-state.py only.
Never manipulate state files directly.
Planning
Spec writing, plan creation, interviews, ambiguity triage, and session pause/resume. Planning owns specs and saved plans; execution goes through subagent-driven-development or workflow dispatch.
Sub-mode Routing
| Signal | Reference |
|---|---|
| Write spec, user stories, define requirements, scope, acceptance criteria | references/pl-spec.md |
| Discuss ambiguities, resolve gray areas, pre-planning discussion | references/pl-pre-plan.md |
| Interview me, depth-first review, "not sure", "where do I start", "poke holes" | references/pl-depth-first-interview.md |
| Implicit ambiguity or unclear implementation choices | references/pl-ambiguity-triage.md |
| Another person holds needed facts or approval | references/pl-human-source-elicitation.md |
| Observation can settle a disputed choice | references/pl-empirical-prototype.md |
| Phase or session transition near | references/pl-context-boundary.md |
| Create plan, task plan, file-backed planning | references/pl-plan-files.md |
| Check plan, validate plan, pre-execution check | references/pl-check.md |
| List plans, show plan, complete plan, manage plans | references/pl-manage.md |
| Pause, save progress, handoff, stopping for now | references/pl-pause.md |
| Resume, continue, pick up where I left off | references/pl-resume.md |
For interviews, batch independent questions into frontier rounds. Ask dependent questions sequentially. Include a recommendation per question.
Objective Loop
Iterate-until-verified-done loop. A user states an objective with verifiable done-criteria; each iteration routes one /do cycle, verifies by executing the criteria, and reschedules until verified-done or budget-stop.
Phase 1: SPEC
Gather from the request: objective statement, DONE-CRITERIA (verifiable checks), iteration budget (default 5), NOT-DONE-YET guardrails (what may never be done to satisfy a criterion).
DONE-CRITERIA types: command (preferred -- deterministic command with expected
exit code/output) or rubric (only when no mechanical check exists -- frozen
at SPEC time, graded by a fresh-context agent).
Phase 2: STATE
Write .objective/<slug>/state.md from references/ol-state-file.md. Wakeups
resume from the state file, never conversation memory.
Phase 3: ITERATE
Plan the smallest next step. Route through /do: classify -> route -> dispatch agents -> evaluate. The loop dispatches exclusively through /do -- never edit inline.
Phase 4: VERIFY
Run every done-criterion check. A worker's "passes" claim never substitutes for re-running.
command: run it, paste exit code and output into iteration log.rubric: dispatch fresh-context sub-agent (did NOT produce the work) with artifact + rubric only. Returns PASS/FAIL with cited evidence.
All pass -> final report, STOP. Any unmet -> Phase 5.
Criteria-gaming guard: a criterion may never be satisfied by weakening a hook, gate, test, or safety control. Stop and report the conflict if that is the only visible path.
Phase 5: RESCHEDULE or STOP
All pass: stop. Unmet + iterations remain: update state file, call
ScheduleWakeup (delay 270s for active polling, 1200s+ for idle work).
Budget exhausted: honest NOT-DONE report with per-criterion status.
Hill Climb
Metric-driven optimization loop. One number moves; everything else stays fixed. Each iteration: hypothesis -> one change -> correctness floor -> re-measure -> accept or revert.
Phase 1: SPEC
| Field | Required | Default |
|---|---|---|
| METRIC (one number, units, direction) | yes | -- |
| MEASURE (deterministic command) | yes | -- |
| TARGET (value that ends the loop) | yes | -- |
| FLOOR (correctness gate commands, must exit 0) | yes | -- |
| FIXTURE (pinned dataset/workload) | yes | -- |
| Variance tolerance | no | 2x baseline spread |
| Iteration budget | no | 8 |
| Plateau threshold K | no | 3 |
One METRIC per loop. Two numbers with a trade-off: promote one to the FLOOR.
Load references/hc-domain-playbooks.md for pre-filled SPEC blocks per domain
(frame rate, API latency, CI time, bundle size, memory, token cost).
Phase 2: BASELINE
Run MEASURE N times (N >= 5, N >= 10 for wall-clock). Record median and spread. If spread >= target improvement: STOP -- harness too noisy. Report noise sources and offer to stabilize first.
Show full SKILL.md (469 more words)Show less
Phase 3: PROFILE
Locate the cost before changing anything. Load references/hc-profiling-tools.md
for per-domain tooling. Guessing at hot spots is the dominant failure mode.
Phase 4: HYPOTHESIZE and CHANGE
State one hypothesis targeting the profiled hot spot. Make one change. Run FLOOR commands -- revert immediately if any fail.
Phase 5: MEASURE
Run MEASURE N times. Compare median to baseline. Accept only if delta > variance
tolerance. Update ledger (references/hc-ledger.md). If accepted, new baseline.
Phase 6: LOOP or STOP
Target reached: final report. K consecutive non-improving iterations: plateau stop. Budget exhausted: report what worked and what remains.
Ad-Hoc Workflow
For structured multi-phase work that does not fit the four modes above. Identify the workflow from the table, load its reference, follow its phases exactly.
Cost Gate
Ask first: does this need a multi-agent workflow? Skip the workflow when:
single-file mechanical edit (use quick), one agent satisfies the request
(direct dispatch), lookup/status/count (direct agent). Escalate only when the
request has independent subtasks, needs orthogonal verification, or names
"comprehensive / thorough / adversarial / tournament."
Composable Patterns
| Pattern | What it does |
|---|---|
| Classify-and-act | Route by type up front; or classify-at-end |
| Fan-out-and-synthesize | Independent agents in parallel, barrier, one synthesizer |
| Adversarial verification | Executor builds, fresh skeptic refutes |
| Generate-and-filter | Over-generate candidates, gate keeps survivors |
| Tournament | N agents attempt same task; pairwise judges pick winner per round |
| Loop-until-done | Repeat until hard completion test passes |
| Quarantine | Read-only triage agent for untrusted content; separate privileged acting agent |
Workflow Catalog
Load the reference for the matched workflow. references/... paths resolve
under ${CLAUDE_SKILL_DIR}.
| Category | Workflow | Reference |
|---|---|---|
| Code Review | Comprehensive multi-wave | references/comprehensive-review.md |
| Debugging | Evidence-based diagnosis | references/systematic-debugging.md |
| Refactoring | Safe refactoring with test gates | references/systematic-refactoring.md |
| Research | Formal research with source gates | references/research-pipeline.md |
| Research | Research to article | references/research-to-article.md |
| Content | Article evaluation | references/article-evaluation-pipeline.md |
| Content | De-AI content | references/de-ai-pipeline.md |
| Content | Documentation | references/doc-pipeline.md |
| Exploration | Codebase exploration | references/explore-pipeline.md |
| Exploration | Multi-perspective analysis | references/do-perspectives.md |
| Creation | Skill creation | references/skill-creation-pipeline.md |
| Creation | Hook development | references/hook-development-pipeline.md |
| Creation | MCP server | references/mcp-pipeline-builder.md |
| Creation | Pipeline scaffolding | references/pipeline-scaffolder.md |
| Creation | Domain research | references/domain-research.md |
| Creation | Chain composition | references/chain-composer.md |
| Creation | Auto-pipeline generation | references/auto-pipeline.md |
| Upgrade | Agent/skill upgrade | references/agent-upgrade.md |
| Upgrade | System upgrade | references/system-upgrade.md |
| Upgrade | Toolkit improvement | references/toolkit-improvement.md |
| Testing | Pipeline test runner | references/pipeline-test-runner.md |
| Testing | Pipeline retro | references/pipeline-retro.md |
| GitHub | Profile rules extraction | references/github-profile-rules.md |
| Orchestration | Task orchestration | references/workflow-orchestrator.md |
| Orchestration | DAG composition | references/dag-composition-patterns.md |
| Orchestration | Compatibility matrix | references/dag-compatibility-matrix.md |
| Orchestration | Common DAG patterns | references/dag-skill-patterns.md |
| Orchestration | DAG examples | references/dag-orchestration-examples.md |
| Orchestration | DAG advanced | references/dag-orchestration-advanced.md |
| Orchestration | Feedback loop | references/feedback-loop-construction.md |
Terminology
"Workflow" is the canonical term. "Pipeline" is the retained legacy alias --
kept for back-compat in routing keys, meta.name exports, and
pipeline-index.json. Use "workflow" in new prose; do not rename code
identifiers.
Error Handling
| Error | Response |
|---|---|
| Mode ambiguous | Ask the user to clarify intent |
| Phase mismatch | Report current state, suggest correct next phase |
| Missing artifact | Route back to previous phase |
| Noisy harness (hill-climb) | Stop; report spread vs target improvement |
| Budget exhausted | Honest NOT-DONE report with per-criterion status |
| State file missing on wakeup | Report and stop; ask user to restate objective |
© notque, 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 155 other files (references) in skills/process/workflow of notque/vexjoy-agent.
- SKILL.md
- references/adr-template.md
- references/agent-upgrade.md
- references/article-evaluation-pipeline.md
- references/article-evaluation-pipeline/references/report-template.md
- references/article-evaluation-pipeline/references/wabi-sabi-classification.md
- references/auto-pipeline.md
- references/auto-pipeline/references/pipeline-catalog.json
- references/auto-pipeline/references/pipeline-catalog.md
- references/build_dag.py
- references/chain-composer.md
- references/chain-composer/references/canonical-chains.md
- references/comprehensive-review-workflow.js
- references/comprehensive-review.md
- … and 142 more
Open the folder on GitHubat commit 5218674
Compare with similar skills
Workflow 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 |
|---|---|---|---|---|---|---|
| Workflow this skillnotque/vexjoy-agent | 435 | — | ~3.1k | Automated safety check: Notes | MIT | |
| Web Application Testinganthropics/skills | 180k | 51 repos | ~966 | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Bugsfossasia/eventyay-interpretation | 1.6k | 31 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| TDDfossasia/eventyay-interpretation | 1.6k | 28 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| 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
fossasia/eventyay-interpretation
Test-driven development. An agent skill from fossasia/eventyay-interpretation.
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 notque/vexjoy-agent
All 61 skills in this repoGame Asset Generator
notque/vexjoy-agent
Deterministic palette/matrix pixel art (not AI). An agent skill from notque/vexjoy-agent.
PR Workflow
notque/vexjoy-agent
Pull request lifecycle: commit, codex review, sync, review, fix, status, cleanup, and PR mining.
Architecture Deepening
notque/vexjoy-agent
Improve architecture across modules by deepening interfaces.
Code Quality
notque/vexjoy-agent
Code quality: cleanup, linting, formatting, quality gates. An agent skill from notque/vexjoy-agent.
Codebase Analyzer
notque/vexjoy-agent
Statistical rule discovery from Go codebase patterns. An agent skill from notque/vexjoy-agent.
Comment Quality
notque/vexjoy-agent
Review and fix temporal references in code comments. An agent skill from notque/vexjoy-agent.
Related
Categories
Questions about Workflow
What does Workflow do?
Structured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing. Workflow is an agent skill from notque/vexjoy-agent. Structured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing.
When should I use Workflow?
Workflow fits situations like: testing & QA work in your project.
How do I install Workflow in Claude Code?
Run `npx skills add notque/vexjoy-agent --skill workflow -a claude-code`. Or copy the skill folder (skills/process/workflow in notque/vexjoy-agent) into .claude/skills/workflow in your project. Claude Code loads it when a task matches its description.
How do I install Workflow in Codex?
Run `npx skills add notque/vexjoy-agent --skill workflow -a codex`. Or copy the skill folder (skills/process/workflow in notque/vexjoy-agent) into .agents/skills/workflow in your project. Codex loads it when a task matches its description.
Can I use Workflow 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 notque/vexjoy-agent --skill workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow, .gemini/skills/workflow, .github/skills/workflow and .opencode/skills/workflow in your project.
What does Workflow need to run?
Going by SKILL.md and its folder, Workflow needs Python and JavaScript for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3; Node.js. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, Skill, Agent, Task.
Does Workflow 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 Workflow safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Workflow use?
Workflow 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 Workflow use?
About 3.1k tokens (SKILL.md is roughly 13k 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 282k tokens, read only when the agent opens those files.
What are the alternatives to Workflow?
Skills that share tags, products or a category with Workflow: Web Application Testing (anthropics/skills, 180k stars), Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars), TDD (fossasia/eventyay-interpretation, 1.6k 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 Workflow?
notque (a GitHub user) maintains it in notque/vexjoy-agent, which has 435 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on October 3, 2026.
Source: notque/vexjoy-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.