TrueCrypt CLI

Use installed TrueCrypt on Windows to mount, dismount, inspect, and automate legacy TrueCrypt containers or encrypted partitions from the command line. Trigg...

Security Scan

This instruction-only skill is internally consistent with its stated purpose (guiding use of an installed TrueCrypt CLI on Windows), requests no extra credentials or installs, and contains sensible safety guidance about password exposure.

Purpose & Capability

Name/description match the runtime instructions: the SKILL.md and command cookbook only reference locating and using TrueCrypt.exe on Windows and producing mount/dismount commands. Nothing requested is unrelated to operating the TrueCrypt CLI.

Instruction Scope

Instructions are narrowly scoped to detecting TrueCrypt, crafting safe example commands, and advising caution (e.g., warning about /p exposing passwords). They do not instruct reading unrelated files, exfiltrating data, or calling external endpoints.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only, so nothing is written to disk or fetched during install.

Credentials

The skill requires no environment variables, credentials, or config paths. Example commands mention supplying passwords on the command line but consistently warn about the risk and recommend safer alternatives.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request persistent privileges or modify other skills or system-wide settings.

Assessment

This skill is coherent and low-risk in terms of what it asks for, but remember: TrueCrypt is discontinued and may have security issues. Do not put real passwords into saved scripts or use the /p switch unless you accept the risk that the password can be seen in process listings, logs, or shell history. Ask the assistant to prepare commands first and confirm before executing anything on your system. If you are concerned about long-term security, consider discussing migration to VeraCrypt with the user only if they are open to it — the skill correctly avoids forcing that recommendation when the user explicitly asked for TrueCrypt guidance.

Use this skill when the user explicitly wants to work with installed TrueCrypt on Windows, especially version 7.1a, instead of being redirected to VeraCrypt.

Workflow

1. Confirm that TrueCrypt.exe exists before giving machine-specific commands.
2. Prefer the full executable path in examples to avoid PATH issues.
3. Ask only for the minimum needed details:
   • volume path or device path
   • target drive letter
   • whether a keyfile is used
   • whether the operation must be non-interactive
4. Prefer non-destructive operations first: detect install path, dismount, or prepare a command without running it.
5. Warn before using /p because command-line passwords may be exposed to process listings, logs, or shell history.
6. If built-in help does not print to the console, rely on known command patterns and cautious validation instead of pretending the CLI is self-documenting.

Quick checks

First, locate the binary. Common paths:

C:\Program Files\TrueCrypt\TrueCrypt.exe
C:\Program Files (x86)\TrueCrypt\TrueCrypt.exe

PowerShell check:

$tc = @(
  'C:\Program Files\TrueCrypt\TrueCrypt.exe',
  'C:\Program Files (x86)\TrueCrypt\TrueCrypt.exe'
) | Where-Object { Test-Path $_ } | Select-Object -First 1

If nothing is found there, fall back to Get-Command TrueCrypt.exe.

Safe command patterns

Use the cookbook in references/commands.md for exact examples.

High-confidence operations:

• mount a volume with /v and /l
• dismount one letter with /d X
• dismount all with /d
• use /q for quiet mode
• use /k for keyfiles when needed
• use /m for mount options when explicitly required

Prefer examples like:

"C:\Program Files\TrueCrypt\TrueCrypt.exe" /v "C:\path\container.tc" /l X /q

"C:\Program Files\TrueCrypt\TrueCrypt.exe" /d X /q

"C:\Program Files\TrueCrypt\TrueCrypt.exe" /d /q

Safety and communication rules

• Do not casually recommend migrating to VeraCrypt if the user explicitly asked for TrueCrypt help; answer the TrueCrypt question first.
• Do mention that TrueCrypt is discontinued when security or long-term maintenance is relevant.
• Do not put a real password into saved scripts unless the user explicitly requests that tradeoff.
• For destructive or risky actions, prepare the command and ask before executing it.
• If uncertain about a rare switch, say so plainly and stick to the known-safe command surface.

Outputs to provide

Depending on the request, provide one of these:

• exact one-line mount or dismount command
• PowerShell or batch wrapper
• install-detection command
• short explanation of each switch used
• a cautious test plan for validating a container without exposing secrets