objective-evaluator_skill

This skill evaluates products and designs through three objective lenses inspired by Fadell, Norman, and Rams to guide unbiased critique.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill objective-evaluator

  • _meta.json297 B
  • SKILL.md4.7 KB

Overview

This skill evaluates products, features, or design concepts using an objective framework drawn from three design classics. It classifies offerings as Tool vs Vitamin, inspects visceral/behavioral/reflective design layers, and flags red‑flag violations to produce a clear, actionable verdict.

How this skill works

Run three independent audits: a Tool audit (painkiller vs vitamin) from Build, a Toy audit (visceral, behavioral, reflective) from Design of Everyday Things, and a Trash check (red flags) from Dieter Rams’ principles. Synthesize results to produce a final classification with audience nuance, tensions, and practical recommendations.

When to use it

  • Assess product-market fit for a new feature or startup idea
  • Review usability and emotional impact of a UI or physical design
  • Audit marketing claims and potential deceptive practices
  • Decide whether to invest resources in improving vs retiring a product
  • Compare variants to prioritize roadmap work

Best practices

  • Run each audit independently to avoid confirmation bias
  • Explicitly identify target user segments before scoring
  • Score with examples and evidence, not intuition alone
  • Surface tensions (e.g., strong utility but weak emotional appeal)
  • Call out monetization or identity trade-offs separately from design

Example use cases

  • Evaluate whether a new feature is essential or just nice-to-have for core workflows
  • Review a consumer gadget for first-impression appeal, usability, and long-term identity
  • Audit a marketing campaign for overstated claims or hidden costs
  • Prioritize engineering fixes when a product is useful but has behavioral friction
  • Decide whether a product should be repositioned as pro tool vs lifestyle accessory

FAQ

Report each audit independently, then synthesize. Highlight who benefits: a product can be a critical Tool for pros while remaining a Toy for casual users.

What counts as a red flag?

Any violation of physical or logical reality, clear deceptive design, fabricated need through marketing, or deliberate planned obsolescence qualifies as a red flag and usually warrants rejection or redesign.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational