Skip to content
TrustedSkillsbeta
Back to all skills

Instrumentation Spec

Checked
product-on-purpose·v1.0.0·writing·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-instrumentation-spec/SKILL.md
Scanned
5 files, 759 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 allows AI agents to generate detailed instrumentation specifications for product development, ensuring comprehensive data collection and analysis. It creates specifications that include event names, properties, and intended use cases aligned with specific product features or user flows. The generated specifications help teams build robust tracking systems from the outset of a project.

When to use it

  • New Feature Development: Generate instrumentation specs before coding begins for a new feature in your application.
  • Product Roadmap Planning: Define necessary data points and tracking requirements during product roadmap planning sessions.
  • Refactoring Existing Features: Create updated instrumentation specifications when refactoring or redesigning existing features.
  • Onboarding New Team Members: Provide clear documentation of existing instrumentation for new developers joining the team.

Key capabilities

  • Defines event names and properties for tracking user actions.
  • Specifies intended use cases for each tracked event.
  • Aligns instrumentation with specific product features or user flows.
  • Generates detailed specifications suitable for engineering implementation.

Example prompts

  • "Generate an instrumentation specification for the 'user signup' flow, including properties like email address and referral source."
  • "Create a spec for tracking clicks on the 'add to cart' button in our e-commerce application."
  • "I need an instrumentation specification for the new search feature, detailing events related to query submission and result display."

Tips & gotchas

The quality of the generated specifications depends heavily on the clarity and detail provided in the initial prompt. Be specific about the product features or user flows you want to track.