Pipa improve operations
Skill lunchpaillola/pipa-skills/skills/pipa-improve-operations
Operational skills for the agents people already use.
npx -y skills add lunchpaillola/pipa-skills --skill pipa-improve-operationsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when the user wants Pipa to improve how the service business runs: retrospectives, lessons, SOPs, templates, reusable processes, archive readiness, closeout learning, and operational improvements.
SKILL.md
1.4 KB, as published. Nobody here has run it
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.