test-task-env-check

Verifying environment variables in a forked skill involves checking that values like CLAUDE_CODE_TASK_LIST_ID are correctly propagated. This skill lists tasks, creates a test task, and lists tasks again to confirm the environment variable is accessible and synchronized.

Task list synchronization fails in a forked environment when the CLAUDE_CODE_TASK_LIST_ID environment variable is not properly propagated. Without this identifier, forked skills cannot access or modify the shared task list, leading to missing context and synchronization errors.

The best way to test task management context propagation is to create a new task with a unique ID and compare the task list before and after the operation. This confirms that the CLAUDE_CODE_TASK_LIST_ID environment variable is accessible and that task list modifications persist correctly.

Yes, you can check task list status before and after operations within a forked context. This skill lists existing tasks, creates a new task with a unique ID, and lists tasks again to document the state changes and confirm that the environment variable is properly propagated.

You need to validate the CLAUDE_CODE_TASK_LIST_ID environment variable when deploying a new skill that relies on task management. Validating it beforehand confirms that the necessary task list ID is available, preventing potential failures due to missing context in the forked environment.