Preqstation

preqstation

Use this skill for natural-language requests to execute PREQSTATION-related work with local CLI engines.

Trigger condition

Trigger this skill when the user asks to:

• start, continue, or complete a PREQSTATION task
• run coding work in a project workspace
• use claude, codex, or gemini for implementation
• mentions preq or preqstation anywhere in the message (case-insensitive)

No fixed prefix is required.

Input interpretation

Parse from user message:

1. engine

• if explicitly provided: claude, codex, or gemini
• default: claude

2. task

• first token matching <KEY>-<number> (example: PRJ-284)
• optional

3. cwd (required to execute)

• if absolute path is explicitly provided, use it
• else resolve by project key from MEMORY.md
• else if task prefix key matches a MEMORY.md project key, use that path
• if unresolved, return a short failure asking for project key or absolute path

4. objective

• use the user request as the execution objective

MEMORY.md resolution

• Read MEMORY.md from this repository root.
• Use the Projects table (key | cwd | note).
• Match project keys case-insensitively.
• If user asks to add/update project path mapping, update MEMORY.md first, then confirm.

MEMORY.md update rules

• Keep mappings in the Projects table only.
• Add or update using this row format: | <key> | <absolute-path> | <note> |.
• Use one row per key. If a key already exists, replace that row.
• Always store absolute paths (no relative paths).

Prompt rendering (required template)

Do not forward raw user text directly. Render this template:

Task ID: <task or N/A>
Project Key: <project key or N/A>
User Objective: <objective>
Execution Requirements:
1) Work only inside <cwd>.
2) Complete the requested work.
3) After completion, return a short completion summary.

Engine commands

Claude Code

claude --dangerously-skip-permissions -p "<rendered_prompt>"

Codex CLI

codex exec --dangerously-bypass-approvals-and-sandbox "<rendered_prompt>"

Gemini CLI

GEMINI_SANDBOX=false gemini -p "<rendered_prompt>"

Output policy

Return only a short completion summary.

Success format:

completed: <task or N/A> via <engine> at <cwd>

Failure format:

failed: <task or N/A> via <engine> at <cwd or N/A> - <short reason>

Do not dump raw stdout/stderr unless user explicitly asks.

Scope boundaries

• OpenClaw handles messenger routing, auth, and channel/webhook behavior.
• This skill only defines local CLI execution behavior and MEMORY mapping usage.