Lessons Log
Checked<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Install on your platform
Showing OpenClaw.
- 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.
Automated safety checks
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
- Scanned
- 5 files, 667 lines
About this skill
What it does
The product-on-purpose-lessons-log skill allows an AI agent to record and organize lessons learned from product development experiences. It captures key details like the situation, decision made, outcome observed, and a suggested action for future avoidance or replication. This structured logging facilitates knowledge sharing and continuous improvement within product teams.
When to use it
- After a significant product launch: Document what went well and what could be improved for subsequent releases.
- Following a failed experiment: Analyze the reasons behind the failure and extract actionable insights.
- During post-mortem reviews: Systematically capture learnings from incidents or challenging situations.
- To onboard new team members: Provide a readily accessible repository of past experiences and decisions.
Key capabilities
- Records situation details (context).
- Captures decision made at the time.
- Documents observed outcome.
- Suggests actions for future reference.
Example prompts
- "Log a lesson about why our recent feature launch was delayed, including what we decided to do and what happened as a result."
- "Record a lesson learned from the A/B test on pricing tiers – specifically focusing on the unexpected user behavior."
- “Create a new lessons log entry for the incident with the payment processing system last week.”
Tips & gotchas
The quality of the logged lessons depends heavily on the detail and honesty provided in the initial input. Encourage thorough descriptions to maximize the value of the recorded learnings.