Install
$ agentstack add skill-lunchpaillola-pipa-skills-pipa-improve-operations ✓ 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
Pipa Improve Operations
Turn work into a better operating system.
Use For
- Retrospectives, lessons learned, closeout learning, reusable templates, SOPs, and process improvements.
- Archive readiness, handover patterns, benefits review, and next-time changes.
- Ongoing company brain content when the intent is process learning, not Pipa configuration.
References
- Load
references/improve-operations.mdfirst. - Use
references/close*.mdfor signoff, handover, lessons, benefits, and archive readiness. - Load
references/examples/improve-operations.mdwhen an example shape helps.
Output Contract
- Lesson or improvement.
- Evidence.
- What changes next time.
- Owner and reuse location or
TBD. - Follow-ups.
Boundaries
- Company brain setup, memory permissions, or tool access goes to
pipa-manage. - Do not declare closure without signoff, handover, archive, or acceptance evidence.
Gotchas
- Do not store memory or update docs externally unless the user asks and the tool/workflow exists.
- Lessons should become a concrete process, artifact, decision, or behavior change.
- Archive and closure claims need evidence or explicit acceptance of gaps.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: lunchpaillola
- Source: lunchpaillola/pipa-skills
- License: MIT
- Homepage: https://usepipa.com
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.