← Back to Skills Marketplace
100
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install tesp
Description
Enforce the Task Execution Signal Protocol for non-instant work so execution stays visible, staged, versioned, and auditable. Use when a task will take more...
Usage Guidance
This skill appears to be what it says (a protocol to make long tasks visible) and doesn't request credentials or install anything — that's good. However, it hard-codes a user-specific file path (/Users/weweclaw/.openclaw/workspace/...) and claims a daily audit cron exists even though no install or code is included. Before installing or invoking it: 1) confirm or change the task-board path to a location you control (or require explicit permission to read/write); 2) ask the skill author to remove hard-coded usernames and to make any cron/scheduling opt-in with clear install steps; 3) test in an isolated workspace so you can see what files the agent creates/updates; and 4) if you don't want the agent touching your filesystem, do not grant it file access or adjust the protocol to use ephemeral or explicit user-provided storage. These inconsistencies are not proof of malicious intent but are enough to warrant caution.
Capability Analysis
Type: OpenClaw Skill
Name: tesp
Version: 1.0.3
The 'tesp' skill implements the Task Execution Signal Protocol (TESP), a structured framework for managing and reporting the progress of long-running tasks. It uses local markdown files (TASK_QUEUE.md and TASK_ARCHIVE.md) within the OpenClaw workspace to maintain state and provides templates for status updates, ensuring transparency and auditability without any signs of malicious intent, data exfiltration, or unauthorized execution.
Capability Assessment
Purpose & Capability
The name/description match the instructions' intent (govern execution visibility and staging) and the skill requires no credentials or installs, which is proportionate. However, the protocol explicitly names a user-specific config path (/Users/weweclaw/.openclaw/workspace/TASK_QUEUE.md and TASK_ARCHIVE.md) even though the skill declares no required config paths — this is an inconsistency that could cause the agent to read/write arbitrary files in the user's home.
Instruction Scope
SKILL.md and references instruct the agent to create/update local task board files, enforce cadence, and rely on an 'existing audit cron' in the source workspace. Because this is an instruction-only skill, these are the exact runtime actions the agent will take: touching local files and looking for system-scheduled jobs. The skill does not declare or ask for permission for these filesystem or scheduling actions, and the hard-coded absolute path contains a specific username, which is unexpected and potentially intrusive.
Install Mechanism
No install spec and no code files — lowest-risk delivery model. Nothing will be written to disk by an installer; runtime behavior is entirely driven by the instruction text.
Credentials
The skill declares no environment variables or credentials (appropriate for its stated purpose), but the instructions reference configuration paths and an existing 'light audit' cron that imply access to persistent workspace artifacts. Because these paths/configs are not declared in the metadata, there is a mismatch between declared and actual required local resources.
Persistence & Privilege
always:false and no autonomous-permission escalation are fine. But the skill's text implies there is a pre-existing daily audit cron in a 'source workspace' (tesp:light-audit). Since no code or install creates that cron, the statement is misleading — it may prompt the agent to search system cron entries or try to create one without explicit install instructions.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install tesp - After installation, invoke the skill by name or use
/tesp - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.3
Add stronger Chinese introduction and refined release description for TESP.
v1.0.2
- Clarified and expanded TESP protocol documentation in SKILL.md.
- Added concise description in both English and Chinese.
- Defined typical use cases and triggering scenarios for TESP.
- Detailed the step-by-step core operating sequence for enforcing TESP.
- Outlined minimum requirements and special rules for multi-agent workflows.
- Provided guidance on model selection for governance and audits.
- Included direct links to reference protocol and template files for further reading.
Metadata
Frequently Asked Questions
What is TESP?
Enforce the Task Execution Signal Protocol for non-instant work so execution stays visible, staged, versioned, and auditable. Use when a task will take more... It is an AI Agent Skill for Claude Code / OpenClaw, with 100 downloads so far.
How do I install TESP?
Run "/install tesp" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is TESP free?
Yes, TESP is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does TESP support?
TESP is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created TESP?
It is built and maintained by wewehg (@wewehg); the current version is v1.0.3.
More Skills