---
name: techsmith-install-auth
description: >-
  Select and verify the supported Snagit or Camtasia install, license, activation, connectivity, and Snagit COM-registration path. Use when provisioning a workstation or resolving activation ambiguity. Trigger with "install TechSmith", "activate Snagit", or "configure Camtasia license".
argument-hint: "[product] [operating-system] [license-model]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.6.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
  - desktop-automation
  - techsmith
  - setup
model: inherit
effort: medium
compatibility: Designed for Claude Code; TechSmith product execution requires an approved Windows or macOS desktop as documented
title: techsmith-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/techsmith-install-auth
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/official-docs.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/techsmith-install-auth/references/official-docs.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/techsmith-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/techsmith-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/techsmith-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/techsmith-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/techsmith-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/techsmith-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# TechSmith Installation and Activation Decision

## Overview

This skill treats activation as a product and entitlement decision, not API authentication. Individual subscriptions activate by account sign-in, while business licenses use a software key and support managed deployment and, where documented, offline activation.

## Prerequisites

- Product, operating system, target version, architecture, and system requirements
- Authoritative entitlement owner and license model: individual, business, or legacy
- Approved installer source and endpoint-management channel
- Connectivity, proxy, offline-use, update, and connected-feature policy

## 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

- Individual subscriptions require the purchasing account to sign in and do not use a software key.
- Business subscriptions use software keys; approved offline activation is a business-license path.
- Subscription software normally needs initial activation connectivity and periodic verification within the vendor's current interval.
- Snagit COM should register during Windows installation; `SnagitCapture.exe /register` is an elevated recovery, not a default step.

## 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. Resolve product/version and confirm the entitlement before downloading or installing anything.
2. Choose standard interactive installation, managed Windows MSI/MST, documented macOS deployment, or approved offline activation.
3. Verify installer origin and checksum, then install through the approved endpoint channel.
4. Activate by individual sign-in, managed business key, or the documented offline exchange without logging secret material.
5. Confirm product launch, displayed version/license state, and required connectivity.
6. For Windows Snagit automation, create the COM object; use vendor registration recovery only if creation fails and approval is recorded.

## Approval Boundaries

Never paste a license key into chat, source control, a public CI variable, or diagnostic output. Do not convert an individual subscription into an unattended shared-worker credential.

## Output

Return product/version, installer hash, deployment mode, redacted license model, activation result, connectivity disposition, COM probe result where applicable, and owner.

## Error Handling

| Condition | Response |
|---|---|
| Entitlement cannot be confirmed | Stop before installation and contact the license owner. |
| Individual sign-in unavailable | Do not substitute a shared account; resolve assignment or use an authorized business license. |
| Offline activation requested for individual plan | Reject the path and explain the documented business-license requirement. |
| COM registration recovery fails | Capture redacted install/version evidence and escalate to TechSmith support. |

## Examples

The example below shows the minimum redacted evidence expected from a successful invocation of this operator workflow.

```text
product=Snagit; platform=Windows; license=business-key(redacted); install=managed; com_probe=pass
```

## Resources

- [Skill-specific official documentation](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/techsmith-install-auth/references/official-docs.md)
- [Activation overview](https://support.techsmith.com/hc/en-us/articles/45353457739149-How-to-Activate-Snagit-or-Camtasia)
- [Deployment overview](https://support.techsmith.com/hc/en-us/articles/43771074923021-Deploying-TechSmith-Products)
