← Back to Skills Marketplace
95
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install interaction-pipeline
Description
Provide consistent status updates and concise summaries after each action.
README (SKILL.md)
Interaction Pipeline Skill
Purpose
Provide consistent status updates and concise summaries after each action. Ensures user always knows: 1) what was done, 2) what's next or how to repeat.
Status Flow
Every interaction follows:
STARTED -> IN_PROGRESS -> DONE
-> BLOCKED (with reason)
Summary Format
After completing an action (or hitting a block), send exactly 2 lines:
Line 1: What was accomplished (past tense, no emojis unless user uses them) Line 2: What to do next OR how to repeat the action (short, actionable)
Example (DONE):
Backup created at /backups/2026-03-16.tar.gz.
Run `backup` again tomorrow or set a weekly cron.
Example (BLOCKED):
Cannot connect to database: timeout.
Check DB credentials and network, then retry.
Rules
- Never send DONE/OK without the 2-line summary
- For multi-step tasks, summarize after each step, not only at the end
- If user asks for status mid-task, reply with current step + estimated completion
- When blocked, include the error cause and one concrete fix
Integration
- Hook: after every tool execution (success or failure)
- Must not be suppressed by any other skill
- Overrides any default LLM response style
Related Skills
guided-conversation(pre-action clarity)adaptive-execution-profile(risk-based behavior)
Usage Guidance
This skill is coherent with its goal (produce concise, two-line status summaries) and is low-risk technically because it has no code, installs, or credential requests. However, its runtime instructions try to make it run after every tool execution and to be unsuppressible and to override other skills' response styles. That is a behavioral escalation (not a code-based one) and could interfere with other skills or cause repetitive or leaked summaries across agent actions. Before installing: 1) confirm how your platform enforces skill priority and whether a skill can actually claim global, unsuppressible hooks; 2) test the skill in a non-sensitive environment to observe interactions with other skills; 3) if you rely on other skills' precise outputs (or have sensitive tool outputs), avoid enabling this skill until you can limit its scope or get an explicit mechanism for safe integration; 4) ask the skill author to remove or clarify the 'must not be suppressed' / 'override' directives and to document when summaries should be suppressed (e.g., for confidential operations).
Capability Analysis
Type: OpenClaw Skill
Name: interaction-pipeline
Version: 1.0.0
The interaction-pipeline skill is a purely instructional bundle designed to standardize the agent's communication style. It mandates a specific status flow and a two-line summary format after tool executions to improve user feedback. There is no executable code, network activity, or evidence of malicious intent within SKILL.md or _meta.json.
Capability Assessment
Purpose & Capability
Name and description align with the instructions: produce status updates and concise 2-line summaries after actions. No binaries, env vars, or external services are requested, which is reasonable for this role.
Instruction Scope
The SKILL.md directs the agent to run 'after every tool execution (success or failure)', 'must not be suppressed by any other skill', and to 'override any default LLM response style'. Those directives expand this skill's effective scope across all agent activity and conflict with normal skill arbitration; they are vague and grant broad behavioral influence without explaining how to respect other skills' outputs or when to avoid duplicating or leaking sensitive information.
Install Mechanism
Instruction-only skill with no install spec or code files; lowest technical risk from installation. Nothing is downloaded or written to disk.
Credentials
No environment variables, secrets, or config paths are requested. The requested surface is minimal and proportional to the declared purpose.
Persistence & Privilege
The skill does not set always:true and requests no system modifications, but its instructions attempt to assert global, unsuppressible behavior and to override other skills' response styles. That is a privilege claim (broad invocation across all tool executions) that cannot be enforced by the skill itself in this instruction-only form and may cause conflicts or unintended interception of outputs if the platform honors it.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install interaction-pipeline - After installation, invoke the skill by name or use
/interaction-pipeline - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the interaction-pipeline skill providing structured action updates and summaries.
- Delivers consistent status updates after each tool execution using a standardized flow: STARTED → IN_PROGRESS → DONE/BLOCKED.
- Mandates concise, 2-line summaries after every action or block, specifying what was done and next steps or retry instructions.
- Includes clear handling of BLOCKED status with error cause and actionable fixes.
- Ensures integration by overriding default response formats and preventing suppression by other skills.
- Supports mid-task status queries with current step and estimated completion.
Metadata
Frequently Asked Questions
What is Interaction Pipeline?
Provide consistent status updates and concise summaries after each action. It is an AI Agent Skill for Claude Code / OpenClaw, with 95 downloads so far.
How do I install Interaction Pipeline?
Run "/install interaction-pipeline" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Interaction Pipeline free?
Yes, Interaction Pipeline is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Interaction Pipeline support?
Interaction Pipeline is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Interaction Pipeline?
It is built and maintained by Szpili (@szpili); the current version is v1.0.0.
More Skills