lkn
/
agent-skills
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

execute: update skills for execute_tool removal 

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Levi Neely 2026-04-16 21:18:18 +02:00
parent bc1d8377c1
commit 051bac4183
2 changed files with 8 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
execute-pipe/SKILL.md
View File

@ -1,7 +1,7 @@
---
name: execute-pipe
intent: parallel, pipeline, pipe, fan-out, concurrent, batch, etl, transform, compose
description: Compose execute_code and execute_tool into sequential pipelines with optional parallel fan-out stages. Use for multi-step data processing, parallel independent operations, and ETL workflows.
description: Compose execute_code into sequential pipelines with optional parallel fan-out stages using execute_pipe. Use for multi-step data processing, parallel independent operations, and ETL workflows.
---
# Execute Pipeline Patterns
@ -14,9 +14,8 @@ The primitives stay simple. Complexity lives in the data schema and the skill (h
| Tool | What it does |
|---|---|
| `execute_code` | Run one or more code snippets. Multiple steps run in parallel; single step returns raw output. |
| `execute_code` | Run one or more steps. Steps may be inline `{code}` or named `{tool, args}` scripts. Multiple steps run in parallel; single step returns raw output. |
| `execute_pipe` | Chain stages sequentially, piping stdout → stdin. Each stage: `{code}`, `{tool, args}`, or `{parallel: [steps]}`. |
| `execute_tool` | Run a named script from `ollie/t`. Used inside `execute_pipe` as a `{tool}` stage. |
## execute_code: parallel fan-out
@ -120,4 +119,4 @@ If normalization requires multiple steps, extract it as a named tool in `ollie/t
| N independent operations, same output schema | `execute_code` parallel steps, or `execute_pipe` parallel stage |
| N operations feeding one transform | `execute_pipe` with parallel first stage |
| Multi-step data transform | `execute_pipe` sequential stages |
| Reusable transform logic | `execute_tool` or named script in `ollie/t` |
| Reusable transform logic | `{tool}` step in `execute_code`, or named script in `ollie/t` as a pipe stage |

21
pcloudcc-testing/SKILL.md
View File

@ -70,31 +70,22 @@ Load pcloudcc-testing skill. Test the affected code path with unit tests, fault
Spawn testing agent:
```
Tool: execute_tool
tool: spawn_agent.sh
args: ["<your-id>", "<cwd>", "<system-prompt-above>"]
sandbox: default
execute_code: steps=[{tool: "spawn_agent.sh", args: ["<your-id>", "<cwd>", "<system-prompt-above>"]}]
```
Send test request:
```
Tool: execute_tool
tool: send_message.sh
args: ["<your-id>", "<testing-agent-id>", "PROMPT_REQUEST", "Validate fix", "Bug: <desc>\nFix: <changes>\nFiles: <list>\nBranch: <name>"]
execute_code: steps=[{tool: "send_message.sh", args: ["<your-id>", "<testing-agent-id>", "PROMPT_REQUEST", "Validate fix", "Bug: <desc>\nFix: <changes>\nFiles: <list>\nBranch: <name>"]}]
```
Read response (user notifies when ready):
```
Tool: execute_tool
tool: check_inbox.sh
args: ["<your-id>"]
execute_code: steps=[{tool: "check_inbox.sh", args: ["<your-id>"]}]
```
Kill testing agent:
```
Tool: execute_tool
tool: kill_agent.sh
args: ["<testing-agent-id>"]
execute_code: steps=[{tool: "kill_agent.sh", args: ["<testing-agent-id>"]}]
```
### Testing Agent Workflow
@ -106,9 +97,7 @@ args: ["<testing-agent-id>"]
5. Verify fix (old fails, new passes)
6. Report:
```
Tool: execute_tool
tool: send_message.sh
args: ["<your-id>", "<requester-id>", "PROMPT_RESPONSE", "Validation complete", "Status: completed|failed\n<evidence>"]
execute_code: steps=[{tool: "send_message.sh", args: ["<your-id>", "<requester-id>", "PROMPT_RESPONSE", "Validation complete", "Status: completed|failed\n<evidence>"]}]
```
**FUSE testing**: Use `execute_elevated_bash` to start the daemon outside the sandbox (see Sandbox Escape section above). No user intervention required.