Skip to content
TrustedSkillsbeta
Back to all skills

Dashboard Requirements

Checked
product-on-purpose·v1.0.0·data·Apache-2.0

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

Install on your platform

Showing OpenClaw.

  1. 1

    Run this in your terminal

    terminal
    $

What we know about this skill

Publisher

product-on-purpose

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned product-on-purpose/pm-skills at 1cef1a9eae.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1cef1a9eae
Manifest
skills/measure-dashboard-requirements/SKILL.md
Scanned
5 files, 871 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill analyzes existing Product on Purpose dashboard data and generates a structured requirements document. It identifies key performance indicators (KPIs), user stories, and acceptance criteria based on observed usage patterns and reported issues within the dashboard. The output is formatted as a clear, actionable document suitable for engineering teams or further refinement by product managers.

When to use it

  • Rapid Requirements Definition: Quickly generate initial requirements when starting a new feature development cycle.
  • Dashboard-Driven Insights: Translate observed user behavior and reported issues from the Product on Purpose dashboard into concrete needs.
  • Alignment with User Needs: Ensure that development efforts are directly aligned with how users are actually interacting with the product.
  • Reducing Ambiguity: Create a shared understanding of requirements between product, design, and engineering teams.

Key capabilities

  • KPI identification from dashboard data
  • User story generation based on usage patterns
  • Acceptance criteria definition for user stories
  • Structured requirements document output

Example prompts

  • "Analyze the Product on Purpose dashboard data and generate a requirements document focusing on user onboarding."
  • "Based on reported issues in the dashboard, create user stories and acceptance criteria for improving search functionality."
  • "Generate a list of KPIs that would indicate successful adoption of the new feature based on dashboard usage."

Tips & gotchas

The quality of the generated requirements depends heavily on the completeness and accuracy of the data within the Product on Purpose dashboard. Ensure the dashboard is capturing relevant user interactions and feedback for optimal results.