Activate Pro license for vault-analyze features

VerifiedSafe

Validates a Pro license key against the API and saves to settings.

Sby Skills Guide Bot
ProductivityIntermediate
7/23/2026
Claude CodeCursorWindsurf
#license-activation#pro-features#validation#obsidian-plugin

Recommended for

Automated summary

Activates or deactivates a Pro license for vault-analyze features by validating a license key against a remote API and updating local settings.

Strengths

  • Validates license key format and checks against API with machine ID binding
  • Supports offline grace period with cached validation for up to 7 days
  • Handles deactivation cleanly by clearing license data from settings

Limitations

  • Requires internet connectivity for first activation and subsequent re-validation
  • License key format is fixed and cannot be customized
  • Machine limit of 3 may require management through external portal
When to use it

Use when you need to unlock Pro features of vault-analyze by entering a license key or deactivate an existing license.

When not to use it

Do not use if you have no license key, if you are permanently offline, or if you are not using the vault-analyze plugin.

Security analysis

Safe
Quality score90/100

The skill only reads system info (hostname, username) to generate a non-sensitive machine ID, makes an HTTPS API call for license validation, and writes to a local settings file. No destructive or exfiltrating actions beyond the intended license activation process.

No concerns found

How this analysis is made

Examples

Activate Pro license
Activate the vault-analyze Pro license with key OE-ABC12-DEF34-GHI56-JKL78.
Deactivate Pro license
Deactivate the vault-analyze Pro license.

name: vault-activate description: Activate Pro license for vault-analyze features. Validates license key against API and saves to settings. model: inherit user-invocable: true context: fork arguments: key: type: string description: "License key (format: OE-XXXXX-XXXXX-XXXXX-XXXXX)" required: true deactivate: type: boolean description: "Remove license and disable Pro features" allowed-tools: filesystem: [Read, Write] network: [WebFetch] cli: [Bash]

$ARGUMENTS

License Activation

Activate Pro features by validating a license key against the API.

License Key Format

OE-XXXXX-XXXXX-XXXXX-XXXXX

Where X is alphanumeric (A-Z, 0-9, excluding ambiguous chars I/O/0/1).

Activation Flow

  1. Validate format: Check key matches OE-[A-Z0-9]{5}-[A-Z0-9]{5}-[A-Z0-9]{5}-[A-Z0-9]{5}

  2. Generate machine ID: Create stable ID from system:

    echo "m-$(echo "$(hostname)-$(whoami)" | md5 | cut -c1-12)"
    
  3. Call validation API:

    POST https://api.obsidian-explorer.jhavens.tech/v1/license/validate
    Content-Type: application/json
    
    {
      "license_key": "OE-XXXXX-XXXXX-XXXXX-XXXXX",
      "machine_id": "m-abc123def456"
    }
    
  4. Handle response:

    • valid: true → Update settings.json, report success
    • valid: false → Report reason (invalid, expired, machine_limit)
  5. Update settings.json:

    {
      "pro_enabled": true,
      "pro_license_key": "OE-XXXXX-XXXXX-XXXXX-XXXXX"
    }
    

Settings Location

Plugin settings: ./settings.json (relative to plugin root)

Deactivation

When deactivate=true:

  1. Read current settings.json
  2. Set pro_enabled: false
  3. Clear pro_license_key: ""
  4. Report deactivation complete

Machine Limit

Licenses support up to 3 machines. If limit reached:

  • API returns valid: false, reason: "Machine limit reached"
  • User must manage machines via customer portal

Offline Behavior

If API unreachable:

  • Check for cached validation at ~/.obsidian-explorer/license-cache.json
  • 7-day offline grace period if previously validated

Output

Success:

Pro license activated!
Type: lifetime
Expires: never
Machines: 1/3

Failure:

License validation failed: Machine limit reached

Manage your devices at: https://obsidian-explorer.jhavens.tech/account

Deactivation:

Pro license deactivated. Pro features disabled.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/activate-pro-license-for-vault-analyze-features-mrwakbcv/download' --output '.skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv/SKILL.md.part' && mv '.skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv/SKILL.md.part' '.skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv/SKILL.md' && test -s '.skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/vault-activate' && cp -R '.skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv' '.claude/skills/vault-activate'

Cursor
test -f '.skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv/SKILL.md' && test -s '.skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/vault-activate' && cp -R '.skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv' '.cursor/skills/vault-activate'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv'

openskills read 'activate-pro-license-for-vault-analyze-features-mrwakbcv'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/activate-pro-license-for-vault-analyze-features-mrwakbcv/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills