agentsclimarketplace
Sign in

Workbench design docs

Skill Fearvox/multica-ultimate-workbench/skills/workbench-design-docs

Product design, technical design documents, user-facing copy, specs, diagrams, and handoff documentation.From its SKILL.md

Install
npx -y skills add Fearvox/multica-ultimate-workbench --skill workbench-design-docs

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 23 stars23 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.

SKILL.md

1.4 KB, 274 tokens by cl100k_base, as published. Nobody here has run it

Workbench Design Docs

Use this skill for product design, technical design documents, user-facing copy, specs, diagrams, and handoff docs.

Design Standard

  • Start from the actual user workflow, not a marketing page.
  • Define the first usable screen, control surface, success state, error state, and handoff path.
  • For internal tools, prefer dense, scannable, operational UI and docs.
  • Keep language precise and action-oriented.
  • Avoid feature claims that are not implemented or verified.

Documentation Standard

  • Keep one canonical version whenever possible.
  • Update durable docs when live behavior changes.
  • Separate strategy, decisions, logs, issue templates, and automation specs.
  • Include IDs, commands, schedules, and evidence only when they help future recovery.
  • Do not include secrets or private credentials.
  • Keep skills/README.md aligned with live skill IDs and agent attachment maps.
  • For SDD work, keep stage artifacts scannable and avoid burying the actual artifact in discussion replies.

Output Contract

For product design:

  • USER GOAL
  • WORKFLOW
  • SUCCESS CRITERIA
  • NON-GOALS
  • OPEN QUESTIONS

For docs:

  • what changed,
  • why it matters,
  • where the canonical source now lives,
  • what must be verified next.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,852. 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.