Skip to content
TrustedSkillsbeta
Back to all skills

Retrospective

Checked
product-on-purpose·v1.0.0·productivity·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.

Scanned
6 files, 710 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 facilitates running a Product Retrospective, helping teams reflect on their work and identify areas for improvement. It guides the process through distinct phases like "What Went Well," "What Could Be Improved," and "Action Items." The retrospective focuses on outcomes rather than individual blame, fostering a culture of continuous learning within product teams.

When to use it

  • After completing a significant sprint or project milestone to assess progress and identify adjustments.
  • When team morale is low or productivity has stalled, to uncover underlying issues and rebuild momentum.
  • To proactively surface process inefficiencies before they become major roadblocks.
  • During regular cadence (e.g., monthly) to ensure consistent reflection and adaptation.

Key capabilities

  • Guides users through the "What Went Well," "What Could Be Improved," and "Action Items" phases of a retrospective.
  • Facilitates structured discussion around outcomes, not individual performance.
  • Helps teams identify actionable steps for future improvement.
  • Provides a framework for consistent retrospective practice.

Example prompts

  • “Let’s run a product retrospective on the last sprint.”
  • "Guide us through a retrospective focusing on our recent feature launch."
  • "Facilitate a retrospective to understand why we missed our deadline."

Tips & gotchas

This skill is most effective when used with a team committed to open and honest feedback. Ensure all participants understand the focus on outcomes and continuous improvement, not individual accountability.