Menu
View and manage ClarionCOM configuration settings including Clarion installation path and default project folder
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Analyze Clarion code generation traces to find recurring failure patterns. Uses evidence-gating (2+ occurrences) to identify real issues. Suggests improvements for the /clarion skill. Triggers on '/clarion-analyze', 'analyze clarion traces', 'what mistakes am I making'.
Benchmark Clarion code generation quality by running test prompts and scoring the output. Measures improvement over time. Triggers on '/clarion-benchmark', 'benchmark clarion', 'test clarion code quality'.
Convert a Clarion dictionary from one file driver to another (e.g., TopSpeed to SQLite). Exports the dictionary to .dctx, transforms driver settings, regenerates GUIDs, creates a new .dct from blank template, and prepares for import. User must perform the final import manually in the IDE.
Create Clarion IDE addins with proper project structure, templates, and SharpDevelop integration. Use when creating new IDE tools, pads, embeditor toolbar buttons, or menu commands for the Clarion IDE.
Clarion language programming reference with syntax rules, data types, control structures, Windows API integration patterns, and template-authoring gotchas (#AT,
Compile C# COM projects for Clarion using MSBuild with correct paths, error handling, and build verification. Supports public releases with changelog management. Auto-applies for building .NET Framework COM components. Verification steps use parallel execution.
| name | clarioncom-config |
| description | View and manage ClarionCOM configuration settings including Clarion installation path and default project folder |
| version | 1.0.0 |
Use the helper script to get CLARIONCOM_HOME (avoids shell escaping issues):
powershell -ExecutionPolicy Bypass -Command "& ([Environment]::GetFolderPath('ApplicationData') + '\ClarionCOM\scripts\clarioncom-env.ps1') home"
If NOT_INSTALLED: Stop and tell user:
ClarionCOM is not installed. Please run Install-ClarionCOM.ps1 from the ClarionCOM distribution folder.
This skill helps you view and update ClarionCOM settings stored in ~/.clarioncom.env.
Read the configuration file directly:
powershell -ExecutionPolicy Bypass -Command "Get-Content ([Environment]::GetFolderPath('UserProfile') + '\.clarioncom.env')"
Parse and display the settings in a formatted way:
ClarionCOM Configuration
========================
Config file: C:\Users\{username}\.clarioncom.env
CLARION_PATH: C:\Clarion12
CLARIONCOM_HOME: C:\Users\{username}\AppData\Roaming\ClarionCOM
DEFAULT_PROJECT_FOLDER: H:\DevLaptop
CLARIONCOM_VERSION: 2.5.0
Also validate that CLARION_PATH exists:
powershell -Command "if (Test-Path 'C:\Clarion12') { Write-Host '[OK] Path exists' -ForegroundColor Green } else { Write-Host '[WARNING] Path does not exist!' -ForegroundColor Red }"
Use AskUserQuestion to present options:
Question: "What would you like to do?" Header: "Config" Options:
3.1 Ask for new path:
Use AskUserQuestion:
User can also select "Other" to provide a custom path.
3.2 Validate path exists:
powershell -Command "if (Test-Path '{NewPath}') { 'EXISTS' } else { 'NOT_FOUND' }"
3.3 If NOT_FOUND:
3.4 If EXISTS (or user chose to save anyway), update the config:
powershell -ExecutionPolicy Bypass -Command "& ([Environment]::GetFolderPath('ApplicationData') + '\ClarionCOM\scripts\clarioncom-env.ps1') clarion-write '{NewPath}'"
3.5 Confirm the change:
Read back the value to confirm:
powershell -ExecutionPolicy Bypass -Command "& ([Environment]::GetFolderPath('ApplicationData') + '\ClarionCOM\scripts\clarioncom-env.ps1') clarion"
Display: "Clarion path updated to: {NewPath}"
3.1 Ask for new folder:
Use AskUserQuestion:
3.2 Validate folder exists:
powershell -Command "if (Test-Path '{NewFolder}') { 'EXISTS' } else { 'NOT_FOUND' }"
3.3 If NOT_FOUND:
3.4 Update the config file:
Read current content, update the line, and write back:
powershell -ExecutionPolicy Bypass -Command "$envPath = [Environment]::GetFolderPath('UserProfile') + '\.clarioncom.env'; $content = Get-Content $envPath; $content = $content -replace '^DEFAULT_PROJECT_FOLDER=.*', 'DEFAULT_PROJECT_FOLDER={NewFolder}'; Set-Content $envPath $content"
3.5 Confirm the change:
Display: "Default project folder updated to: {NewFolder}"
After any changes, display the updated configuration:
Configuration Updated
=====================
CLARION_PATH: C:\Clarion12 [OK - exists]
DEFAULT_PROJECT_FOLDER: H:\DevLaptop [OK - exists]
These settings will be used for future /clarioncom-build and /clarioncom-deploy operations.
For users who want to quickly check or set values without the interactive workflow:
View current Clarion path:
powershell -ExecutionPolicy Bypass -Command "& ([Environment]::GetFolderPath('ApplicationData') + '\ClarionCOM\scripts\clarioncom-env.ps1') clarion"
Set Clarion path directly:
powershell -ExecutionPolicy Bypass -Command "& ([Environment]::GetFolderPath('ApplicationData') + '\ClarionCOM\scripts\clarioncom-env.ps1') clarion-write 'C:\Clarion12'"
View all settings:
powershell -ExecutionPolicy Bypass -Command "Get-Content ([Environment]::GetFolderPath('UserProfile') + '\.clarioncom.env')"
If config file doesn't exist:
If CLARIONCOM_HOME is not set:
This skill is standalone and does not invoke other skills. It modifies the same configuration file used by:
/clarioncom-build - Uses CLARION_PATH for file copying/clarioncom-deploy - Uses CLARION_PATH for file copying/ClarionCOM - Reads CLARION_PATH during initializationChanges made here take effect immediately for subsequent skill invocations.