executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
techsmith-core-workflow-bManage a controlled Camtasia batch export using local standalone projects and the installed version's modern exporter. Use when producing approved project queues without legacy CamtasiaProducer assumptions. Trigger with "Camtasia batch export", "produce Camtasia projects", or "Camtasia render queue".
Independent GitHub snapshot · Automated classification · Original documentation governs
name: techsmith-core-workflow-b description: >- Manage a controlled Camtasia batch export using local standalone projects and the installed version's modern exporter. Use when producing approved project queues without legacy CamtasiaProducer assumptions. Trigger with "Camtasia batch export", "produce Camtasia projects", or "Camtasia render queue". argument-hint: "[project-manifest] [output-directory]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.6.0 author: Jeremy Longshore jeremy@intentsolutions.io license: MIT tags:
This skill builds a reproducible export manifest while respecting Camtasia's desktop boundaries. It stages standalone projects on a local non-synced drive, validates media and version compatibility, and uses the modern Batch Export experience or a command contract explicitly verified for the installed release.
Use Read, Glob, and Grep to inspect local scripts, manifests, logs, and tests. Use WebFetch only for current primary TechSmith documentation. Use Write or Edit only after confirming the target repository file and approval boundary.
CamtasiaProducer.exe exists.TechSmith desktop activation is not API authentication. Resolve individual sign-in versus business-key or approved offline activation before execution. Redact all keys, account identifiers, activation artifacts, and sensitive endpoint details.
Do not rewrite TSCPROJ internals, run active projects from synchronized storage, or silently substitute an export preset. A failed project must not block evidence for completed items.
Return the pinned Camtasia version, manifest digest, local scratch path, per-project result, preset, media validation, promotion state, and cleanup.
| Condition | Response |
|---|---|
| Project newer than workstation | Move the job to the matching or newer approved Camtasia version. |
| Missing media | Restore a standalone/zipped project or original local paths before export. |
| Legacy exporter requested | Reject the plan and select the modern exporter supported by the installed release. |
| Output validation fails | Keep the output quarantined and preserve project-specific diagnostics. |
The example below shows the minimum redacted evidence expected from a successful invocation of this operator workflow.
project=release-demo.tscproj; version=2026.x; storage=local; preset=approved-mp4; validation=pass