techsmith-reference-architecture
/techsmith-reference-architecture
Design a controlled architecture for Snagit capture and Camtasia recording/export workers with local scratch, durable manifests, validation, and artifact promotion. Use when moving beyond one-off scripts. Trigger with "TechSmith architecture", "Snagit automation design", or "Camtasia worker topology".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Design a controlled architecture for Snagit capture and Camtasia recording/export workers with local scratch, durable manifests, validation, and artifact promotion. Use when moving beyond one-off scripts. Trigger with "TechSmith architecture", "Snagit automation design", or "Camtasia worker topology".
Triggers from the description
Arguments
/techsmith-reference-architecture [system-context] [diagram-or-design-path]
Original author description
Design a controlled architecture for Snagit capture and Camtasia recording/export workers with local scratch, durable manifests, validation, and artifact promotion. Use when moving beyond one-off scripts. Trigger with "TechSmith architecture", "Snagit automation design", or "Camtasia worker topology".
How it works
- Overview
- Prerequisites
- Tool Discipline
- Current Contract
- Licensing and Authentication
- Instructions
- Approval Boundaries
- Output
- Error Handling
- Examples
SKILL.md preview
--- name: techsmith-reference-architecture description: >- Design a controlled architecture for Snagit capture and Camtasia recording/export workers with local scratch, durable manifests, validation, and artifact promotion. Use when moving beyond one-off scripts. Trigger with "TechSmith architecture", "Snagit automation design", or "Camtasia worker topology". argument-hint: "[system-context] [diagram-or-design-path]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.6.0 author: Jeremy Longshore <jeremy@intentsolutions.io> license: MIT tags: - desktop-automation - techsmith - architecture model: inherit effort: medium compatibility: Designed for Claude Code; TechSmith product execution requires an approved Windows or macOS desktop as documented --- # TechSmith Desktop Media Automation Architecture ## Overview This skill separates orchestration from licensed desktop execution. A control plane stores only job intent and redacted state; approved Windows or macOS workers perform version-pinned product operations on local storage; validators promote immutable outputs to archive or publishing systems after the application closes. ## Prerequisites - Workload classes, data classifications, service objectives, and expected volume - Endpoint and entitlement inventory with product/version/platform capabilities - Storage, network, identity, logging, retention, and incident constraints - Approval owners for capture scope, deployment, activation, and publication ## Tool Discipline 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. ## Current Contract - Snagit COM jobs run only on licensed Windows workers with an interactive desktop. - Camtasia active projects and media remain local and non-synced; promoted outputs are immutable artifacts. - Job manifests carry product version, operation, input hashes, output policy, deadline, and idempotency key. - Workers expose redacted state transitions, not remote arbitrary-shell access or license secrets. ## Licensing and Authentication 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. ## Instructions 1. Discover existing scripts, workers, endpoints, storage paths, product versions, licenses, and downstream consumers. 2. Define job classes and state transitions from accepted through staged, running, validating, promoted, failed, or quarantined. 3. Partition workers by platform, product/version, interactive capability, and data classification. 4. Design local scratch, durable manifests, checksums, output validation, post-close archival, and retention cleanup. 5. Add admission control, per-session capture locks, bounded export workers, health probes, and dead-letter handling. 6. Document trust boundaries, failure modes, rollback, recovery-time objectives, and migration from current scripts. ## Approval Boundaries Do not centralize raw license keys, captures, or project media in the control plane. Do not treat desktop workers as generic remote execution hosts. ## Output Return current and target topology, job/state model, trust boundaries, worker capability matrix, data flow, failure handling, migration stages, and unresolved decisions. ## Error Handling | Condition | Response | |---|---| | Worker capability unknown | Probe version and supported interfaces before assigning a job class. | | Active data crosses to sync storage | Stage locally and promote only after product closure and validation. | | Control plane needs product secrets | Redesign so activation stays endpoint-managed. | | No idempotency boundary | Add durable job and output identities before enabling retries. | ## Examples The example below shows the minimum redacted evidence expected from a successful invocation of this operator workflow. ```text control-plane -> signed job manifest -> licensed local worker -> validator -> immutable artifact store ``` ## Resources - [Skill-specific official documentation](references/official-docs.md) - [Deployment overview](https://support.techsmith.com/hc/en-us/articles/43771074923021-Deploying-TechSmith-Products) - [Camtasia file model](https://support.techsmith.com/hc/en-us/articles/203730028-Working-with-Camtasia-Editor-TSCPROJ-and-TREC-Files)
Files in this package (2)
- SKILL.md 4 KB
- references/official-docs.md 4 KB
Versions
The database has no other skills named techsmith-reference-architecture.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version b8ee0903a47b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100techsmith-ci-integration
Gate Snagit COM and Camtasia automation changes with secretless contract tests plus an explicitly licensed Windows smoke lane. Use when adding CI for TechSmith scripts or deployment assets. Trigger with "TechSmith CI", "Snagit contract tests", or "Camtasia automation checks". - 100techsmith-performance-tuning
Optimize Snagit capture and Camtasia project/export throughput from measured workstation bottlenecks and safe concurrency limits. Use when queues are slow, unstable, or resource-bound. Trigger with "TechSmith performance", "Camtasia export tuning", or "Snagit capture throughput".