Claude Task Runner

Use the local runner script instead of raw claude -p when the task needs any of these:

• - model switching via INLINECODE1
• durable task state under INLINECODE2
• notification on completion/failure
• structured-output enforcement via JSON Schema
• multi-file artifact validation (--expect-file, --expect-contains, --expect-glob)

Primary script:

• - INLINECODE6

Quick decision

Use this skill when:

• - the user asks to run Claude Code non-interactively / in batch / in background
• you need a coding or analysis task to survive beyond a single shell command
• you want the result judged by actual outputs, not just model text
• tmux interaction is unnecessary or risky

Do not use this skill when:

• - a direct read / edit is simpler
• the user explicitly wants a live interactive tmux session
• the task needs persistent interactive back-and-forth inside Claude Code

Default workflow

1. 1. Pick the model alias.

- GLM-5.1 for architecture / long-context reasoning - minimax-m2.7 for deeper problem solving and robust headless runs

1. 2. Decide whether the task needs validation.
2. If validation is needed, prefer both:

- structured result validation with --json-schema-file - artifact validation with --expect-file, --expect-contains, --expect-glob

1. 4. Run the task with cc-task-runner.sh run or run-file.
2. Inspect with status, then log if anything looks off.
3. Treat missing artifact or structured_output.status=failure as a real failure.

Command patterns

Minimal run

CODEBLOCK0

Write task with permission mode

CODEBLOCK1

Multi-file validation

All --expect-file, --expect-contains, --expect-glob support repeat usage.
--expect-contains binds to the most recent --expect-file before it.

CODEBLOCK2

Meaning:

• - a.txt must exist AND contain "alpha"
• INLINECODE26 must exist (no content check)
• INLINECODE27 glob must match at least one file

Full combo: schema + multi-file + glob

CODEBLOCK3

Prompt from file

CODEBLOCK4

Inspect state

CODEBLOCK5

Validation parameters

Parameter	Repeatable	Binds to	Description
INLINECODE28	✅ yes	self	File must exist after task
INLINECODE29

✅ yes | previous --expect-file | That file must contain text | | --expect-glob <pattern> | ✅ yes | self | Glob must match ≥1 file | | --json-schema-file <file> | ❌ no | self | Enforces structured output | | --permission-mode <mode> | ❌ no | self | bypassPermissions or acceptEdits | | --fallback-model <alias> | ❌ no | self | Retry with this model on failure | | --max-retries <n> | ❌ no | self | Max retry attempts (default: 1) |

Binding order example

CODEBLOCK6

Validation rules

For tasks that must produce files, always provide at least one artifact check.

Preferred combinations:

• - file creation only → INLINECODE38
• exact or critical content → --expect-file + INLINECODE40
• one-or-more generated files → INLINECODE41
• non-file report / analysis → INLINECODE42
• implementation task → schema + artifact checks together

Permission mode: Prefer --permission-mode bypassPermissions in trusted local environments when the task must write files or run Bash. Without it, Claude may ask for manual approval and the task will hang.

Do not trust plain language like "已完成" or "done" without validation.

Exit codes

Code	Meaning
0	Task completed, all validations passed
1

Model/runtime error | | 2 | Artifact validation failed | | 3 | Structured output reported failure |

JSON schema guidance

Keep schemas small. Use them to force a machine-checkable result contract.

Good default schema for most tasks:

• - status: INLINECODE45
• INLINECODE46: short text
• INLINECODE47: optional array
• INLINECODE48: optional
• INLINECODE49: optional

Model notes

Current local environment supports GLM-5.1 headless via:

• - base URL: INLINECODE51
• model id: INLINECODE52

The local cc-switch wrapper already special-cases this. Use the alias GLM-5.1, not a raw model id, when calling the runner.

Failure handling

If a task fails:

1. 1. run INLINECODE55
2. run INLINECODE56
3. identify which layer failed:

- model/runtime error (exit 1)
- artifact validation failure (exit 2)
- structured schema failure (exit 3)

1. 4. either rerun with a stricter prompt or fix the prompt/schema/expectations

If the model says success but artifact validation fails, trust the validator, not the prose.

Files to read when needed

Read these only when you need deeper details:

• - references/runner-usage.md for usage notes and patterns
• INLINECODE58 for a reusable schema template
• INLINECODE59 for a concrete invocation pattern