agentsclimarketplace

Prototype lab

Skill markoblogo/abvx-agent-skills/skills/prototype-lab

Reviewable capability layer for coding agents. Portable skills, delivery gates, workflow patterns, and verification-first engineering.

Install
npx -y skills add markoblogo/abvx-agent-skills --skill prototype-lab

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Build throwaway prototypes to answer a specific product, UI, state-machine, data-model, or workflow question before committing production code. Use when the user asks to prototype, explore variants, sanity-check logic, try designs, make a playable mock, or learn quickly with code that will be deleted or absorbed.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, 312 tokens by cl100k_base, as published. Nobody here has run it

Prototype Lab

A prototype answers one question. It is not production code with fewer tests.

Pick The Prototype Question

Choose the branch:

  • Logic prototype: state model, workflow, parser, scoring, queue, rules, or business logic.
  • UI prototype: layout direction, interaction model, variants, motion, or product feel.
  • Integration prototype: unknown API/tool behavior, deployment constraint, or browser capability.

If ambiguous, state the assumption and keep the artifact easy to delete.

Rules

  • Mark it as prototype/throwaway in path, UI, comments, or README.
  • Use one command to run.
  • Keep state in memory unless persistence is the thing being tested.
  • Avoid broad abstractions, production plumbing, and hidden dependencies.
  • Surface state after actions so learning is visible.
  • Do not leave prototype code mixed with production code without a decision.

UI Variant Pattern

When exploring design, create 2-4 meaningfully different variants. Let the user switch via route, query param, segmented control, or small debug toolbar. Do not make tiny color-only variations.

Logic Pattern

When exploring state, make a terminal or local web harness that can run scripted cases and manual interactions. Print current state, event, output, and invariant violations.

Closeout

When the prototype answers the question:

  • capture the decision in an issue, ADR, notes file, commit message, or final report;
  • delete the prototype or identify exactly what will be absorbed into production;
  • list what remains unproven.

What ships with it: 2 files

1.4 KB alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,970. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.