Install
$ agentstack add skill-hardiktiwari-pm-operating-os-knowledge-updater ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Knowledge Updater
Update knowledge layer documents (knowledge/) with automatic snapshotting. Before any update, the current version is saved to memory/knowledge-snapshots/ so the retrospective agent can track how strategy evolved over time.
When to Use
- Updating
knowledge/files (strategy, segments, metrics, competitive landscape) - After quarterly planning when strategy shifts
- After significant market or competitive changes
- When asked "update my strategy", "refresh knowledge docs", or "knowledge update"
Process
1. Identify What's Changing
Ask if not clear:
- Which knowledge doc(s) are being updated?
- What changed? (new strategy, updated segments, revised metrics, competitive shift)
- Why? (quarterly planning, market shift, exec direction, experiment results)
2. Snapshot Current State
Before making any changes, save the current version:
- Create a timestamped snapshot directory:
memory/knowledge-snapshots/YYYY-MM-DD/ - Copy the file(s) being updated into that directory with their original names
- Add a
_changelog.mdfile to the snapshot:
# Knowledge Snapshot — YYYY-MM-DD
**Reason for update:** [what triggered this change]
**Files updated:** [list]
## Changes Summary
- [File 1]: [what changed and why]
- [File 2]: [what changed and why]
3. Make the Update
Edit the knowledge file(s) in knowledge/{product}/ with the new content. Ensure:
- Format matches the existing template structure
- Changes are clearly reflected in the content
- No orphaned references (e.g., removing a segment that's referenced elsewhere)
4. Log as a Decision (optional)
If the knowledge update reflects a significant strategic shift, suggest logging it as a decision trace using the decision-logger skill.
Output
- Updated knowledge file(s) in
knowledge/{product}/ - Snapshot of previous version in
memory/knowledge-snapshots/YYYY-MM-DD/ - Changelog documenting what changed and why
Over time, snapshots enable:
- Drift detection: How has stated strategy evolved quarter over quarter?
- Decision coherence: Do knowledge updates align with decision traces?
- Retrospective analysis: The retrospective agent compares current knowledge to snapshots to surface gradual shifts
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hardiktiwari
- Source: hardiktiwari/PM-operating-OS
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.