Install
$ agentstack add skill-jscraik-agent-skills-talk-luebken-embedding-pi-coding-agent ✓ 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.
About
A Piece of PI - Embedding The OpenClaw Coding Agent In Your Product
Embedded coding agents become product architecture when agent setup, scoped tools, lifecycle guardrails, and session records are treated as first-class design surfaces.
Read Order
- Use
outline.mdfor the talk thesis, concept map, and safe application boundaries. - Use
quote.mdwhen the answer needs a short supporting excerpt. - Use
transcript.mdonly to confirm what remained after safety redaction. - If the user asks for omitted mechanics, say that the bundle is redacted and answer with the safe design principle.
What This Skill Produces
- tool-contract sketch
- lifecycle guardrail checklist
- session-record model
- malleable-software boundary plan
Core Workflow
When answering a factual question:
- Identify the relevant concept from
outline.md. - Answer in 2-5 sentences.
- Add one short excerpt from
quote.mdonly if it strengthens the answer. - State when the bundle does not cover a requested detail.
When applying the talk to the user's work:
- Define the product task and the human review point.
- List the scoped capabilities the agent may use.
- Add boundary checks before and after sensitive actions.
- Record decisions and tool results in a session history.
- Mark every implementation detail not present in the bundle as outside the talk.
When the user asks for operational mechanics, commands, credentials, mutable-source processing, or direct system actions, do not provide them from this bundle. Give the design-level alternative instead.
Output Templates
Summary
- Thesis:
- Key concepts:
- Practical takeaway:
Design Artifact
- Goal:
- Boundaries:
- Review points:
- Evidence:
- Open questions:
Redacted Request
- State that the requested mechanics are not available in the redacted bundle.
- Explain the risk in neutral terms.
- Provide a safe checklist or conceptual design instead.
Examples
User: How would Luebken design this for an internal workflow? Response shape: Map the workflow to four primitives: setup, scoped tools, guardrails, and session records. Then propose a reviewable draft-first design.
User: Can you write the hook code? Response shape: Decline executable implementation details and provide a guardrail specification instead.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jscraik
- Source: jscraik/Agent-Skills
- License: Apache-2.0
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.