agentsclimarketplace

Product context analysis

Skill Suraj787/motif/skills/product-context-analysis

Use when you need to establish the product purpose, product type, page/screen type, and the user with their primary task before any interaction or effect is considered.From its SKILL.md

Install
npx -y skills add Suraj787/motif --skill product-context-analysis

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.
  • 0 stars0 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.5 KB, 288 tokens by cl100k_base, as published. Nobody here has run it

Product Context Analysis

Responsibility: Resolve the top four levels of the Motif reasoning model so every later decision is grounded in context, not aesthetics.

When to invoke

  • At the start of any Motif task (steps 1-5 of the root workflow).
  • Whenever the interaction objective is unclear or contested.

Inputs

  • The target repository (framework, routes, design tokens, existing components).
  • The product brief or request.

Outputs

  • Development purpose, why the product exists.
  • Product type, and a firm website vs web application classification.
  • Page/screen type, landing, dashboard, list/table, form, detail, wizard, etc.
  • User + primary task, who acts and what they are trying to accomplish.
  • A short statement of the interaction problem to hand to interaction-design.

How it connects

  • Reads intelligence/ taxonomies (product types, page types, user intents) to classify, not to prescribe effects.
  • Does not touch registry/, context first, catalogue later.
  • Hands its findings to interaction-design; records them in the decision log.

Notes

Websites optimise persuasion and narrative; web applications optimise task throughput and repeat use. Misclassifying here cascades into wrong patterns downstream, so make the website/application call explicit and justify it.

What ships with it

Read from the repository

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

Keep looking

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