[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KT5Z9FBDTYDNBTBHF1498":3,"skill-same:01M77KT5Z9FBDTYDNBTBHF1498":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M77KT5Z9FBDTYDNBTBHF1498","LESecureLocal",null,"LESecure Local\u002FOn-Prem — encrypt and decrypt data, files, and folders using the LE desktop tool with layered locks (pin, password, MFA, time lock, geo-location).","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fl\u002Flesecurelocal\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: LESecureLocal\ndescription: LESecure Local\u002FOn-Prem — encrypt and decrypt data, files, and folders using the LE desktop tool with layered locks (pin, password, MFA, time lock, geo-location).\ntriggers:\n  - LESecure Local\n  - LESecure Desktop\n  - LESecure On-Prem\n  - LE local\n  - LE desktop\n  - encrypt file\n  - decrypt file\n  - encrypt folder\n  - decrypt folder\n  - what's my current location\n  - what is my current location\n  - whereami\n  - where am i\n  - current location\n---\n\n# LESecureLocal — LESecure Local \u002F On-Prem Skills\n\nEncrypt and decrypt **plain text, files, and folders** using the LE desktop binary. No API key is needed — everything runs locally. No data leaves your machine.\n\n## Project Links\n\n| Resource | URL |\n|---|---|\n| Source code & documentation | \u003Chttps:\u002F\u002Fgithub.com\u002FSPAlgorithm\u002FLE> |\n| Cloud alternative | LESecureCl skill (uses the LESecure API) |\n\n## ROUTING RULES (MANDATORY)\n\n- **Files and folders MUST always use LESecure Local.** Never use LESecure Cloud for file\u002Ffolder encryption. If the user asks to encrypt files\u002Ffolders via cloud, inform them: \"File\u002Ffolder encryption is only supported via LESecure Local (desktop).\" and use this skill.\n- **Safe-by-default flags for files\u002Ffolders.** Always pass `-z` (force overwrite) and — when the target is a directory — `-n` (recursive). **Never pass `-c` (clean\u002Fdelete source) or `-j` (trio = `-z -c -n`) without explicit user confirmation**, because both delete the original file after encrypting. See the \"Destructive Flags\" rules below.\n- **For plain text**, ask the user: \"Would you like to use **LESecure Cloud** (API) or **LESecure Local** (desktop)?\" and proceed accordingly.\n- **Current location queries** — when the user asks \"what's my current location\", \"whereami\", \"where am I\", or any equivalent, run `LE -7` and share the output. No other flags are needed. **Note:** `LE -7` accesses device GPS — this is a privacy-sensitive operation. On first use in a session, inform the user: \"This will query your device's GPS location via LE.\" Proceed only after acknowledgment.\n\n## Destructive Flags — `-c` and `-j` (MANDATORY)\n\n- `-c` (clean) **deletes the source file after encryption or decryption**. It is irreversible in-place data loss.\n- `-j` is a trio that **includes `-c`**, so it is also destructive.\n- Never silently add `-c` or `-j`. Before using either, ask the user explicitly, e.g.: \"This will delete the source `\u003Cfile>` after the operation. Confirm with 'yes, delete source' to proceed.\"\n- If the user does not confirm, use only `-z` (and `-n` for folders). The source stays on disk.\n- When the user explicitly asks for `-j` or \"clean\u002Fdelete source after\", use `-j` and state in the response that the source was removed.\n\n## Binary Location (configuration)\n\nThe skill looks for the `LE` binary in this order:\n\n1. The `LE_BIN` environment variable, if set (e.g., `export LE_BIN=\u002Fopt\u002Fle\u002FLE`).\n2. `LE` on `PATH` (via `command -v LE`).\n3. A user-supplied path if neither of the above resolves. In that case, **ask the user** for the binary path — do not guess or hardcode.\n\nIn examples below, `LE` is used as a shorthand for whichever path resolves. When actually invoking, expand it to the full resolved path so the command is reproducible.\n\n```bash\n# Resolve once, then reuse\nLE_BIN=\"${LE_BIN:-$(command -v LE)}\"\n\"$LE_BIN\" --help\n```\n\n## Date & Time Rules (MANDATORY)\n\nAll date\u002Ftime handling for this skill follows these rules — no exceptions:\n\n1. **Always use EST\u002FEDT (America\u002FNew_York)** to calculate and send dates. The LE tool interprets `-l` and `-r` in EST\u002FEDT.\n2. **Start time (`-l`) = current EST + 2 minutes** by default. This buffer prevents the \"date must be in future\" error.\n3. **End time (`-r`) = start time + the user's requested duration**.\n4. **Cross-platform time computation.** Prefer Python because `date` flag syntax differs between BSD (macOS) and GNU (Linux). Python 3 is available on both.\n\n   **Input safety:** The `\u003CN>` duration value is passed as `sys.argv[1]` and cast via `int()` inside the Python script — any non-integer input raises `ValueError` and the script exits without executing. **Never concatenate or interpolate user input directly into the `python3 -c` string.** Always pass values as positional arguments (`sys.argv`).\n\n   ```bash\n   # Start time (now + 2 minutes, EDT\u002FEST) — no user input needed\n   python3 -c \"from datetime import datetime,timedelta; from zoneinfo import ZoneInfo; print((datetime.now(ZoneInfo('America\u002FNew_York'))+timedelta(minutes=2)).strftime('%Y\u002F%m\u002F%d %H:%M'))\"\n\n   # End time (now + 2 min + N minutes) — N is passed as argv[1], cast to int()\n   python3 -c \"import sys; from datetime import datetime,timedelta; from zoneinfo import ZoneInfo; N=int(sys.argv[1]); print((datetime.now(ZoneInfo('America\u002FNew_York'))+timedelta(minutes=2+N)).strftime('%Y\u002F%m\u002F%d %H:%M'))\" \u003CN>\n\n   # End time (now + 2 min + N hours) — N is passed as argv[1], cast to int()\n   python3 -c \"import sys; from datetime import datetime,timedelta; from zoneinfo import ZoneInfo; N=int(sys.argv[1]); print((datetime.now(ZoneInfo('America\u002FNew_York'))+timedelta(minutes=2,hours=N)).strftime('%Y\u002F%m\u002F%d %H:%M'))\" \u003CN>\n   ```\n   Fallback (`date`) — only if Python is unavailable:\n   - macOS\u002FBSD: `TZ=America\u002FNew_York date -v+2M \"+%Y\u002F%m\u002F%d %H:%M\"`\n   - Linux\u002FGNU: `TZ=America\u002FNew_York date -d '+2 minutes' \"+%Y\u002F%m\u002F%d %H:%M\"`\n5. **Always display the window back to the user in EDT\u002FEST**.\n\n## Two Modes\n\n### 1. PlainText Mode (`--PlainText` \u002F `-p`)\n\nEncrypt\u002Fdecrypt inline strings. The LE binary expects the data wrapped in triple single quotes (`'''...'''`).\n\n#### Input Sanitization (MANDATORY)\n\n**Never interpolate raw user input directly into the shell command.** The `'''...'''` quoting breaks if the data contains single quotes, enabling shell injection. Before building the command:\n\n1. **Validate:** reject or escape any single quotes (`'`) in the user's plaintext. Replace each `'` with `'\\''` (end quote, escaped literal quote, reopen quote).\n2. **Alternatively, use a shell variable** to isolate user data from the command string:\n   ```bash\n   # Store user data in a variable — shell expansion is safe inside triple quotes\n   LEDATA='user provided text here'\n   LE -e \"'''${LEDATA}'''\" \u003CLOCK_FLAGS> --PlainText\n   ```\n3. **Never use `eval`** or backtick interpolation with user-supplied text.\n\n```bash\n# Encrypt (with sanitized data)\nLE -e '''\u003CSANITIZED_DATA>''' \u003CLOCK_FLAGS> --PlainText\n\n# Decrypt (encrypted output is safe — no special chars)\nLE -d '''\u003CENCRYPTED_DATA>''' \u003CLOCK_FLAGS> --PlainText\n```\n\n### 2. File \u002F Folder Mode\n\nDefault flags (safe):\n- **File:** `-z`\n- **Folder:** `-z -n`\n\nDestructive extras (only with explicit user confirmation, see rules above): add `-c` to also delete the source, or use `-j` (= `-z -c -n`).\n\n```bash\n# Safe file encrypt \u002F decrypt (source file preserved)\nLE -e \u003CFILE>   \u003CLOCK_FLAGS> -z\nLE -d \u003CFILE.letxt> \u003CLOCK_FLAGS> -z\n\n# Safe folder encrypt \u002F decrypt (source folder preserved)\nLE -e \u003CFOLDER> \u003CLOCK_FLAGS> -z -n\nLE -d \u003CFOLDER> \u003CLOCK_FLAGS> -z -n\n\n# Destructive — only after explicit user confirmation\nLE -e \u003CFILE_OR_FOLDER> \u003CLOCK_FLAGS> -j\n```\n\n**Naming notes:**\n- Encrypted files get a `.le` prefix on the extension (e.g., `example.txt` becomes `example.letxt`); use the `.letxt` filename when decrypting.\n- For folders, the individual files inside get the `.le` prefix on their extensions. The folder name itself stays the same.\n\n## Available Locks\n\n| Flag | Lock Type | Value | Example |\n|------|-----------|-------|---------|\n| `-1` | Pin\u002FCode | Numeric string | `\"1122\"` |\n| `-w` | Password | Password file (`.letxt`) or passphrase | `pass.letxt` |\n| `-2` | MFA | Phone number (E.164) | `\"+19199870623\"` |\n| `-3` | OTP | OTP code for decryption | `\"123456\"` |\n| `-l` | Time lock start | `YYYY\u002FMM\u002FDD HH:MM` | `\"2026\u002F04\u002F12 17:41\"` |\n| `-r` | Time lock end | `YYYY\u002FMM\u002FDD HH:MM` | `\"2027\u002F04\u002F12 17:36\"` |\n| `-b` | Location lock — use existing `.lecsv` key file (**encrypt only**; omit on decrypt) | Path to `.lecsv` file | `location.lecsv` |\n| `-v` | Location lock — create a new `.lecsv` key file from a GPS CSV (switch, no value) | (no value) | `-v` |\n\n### Additional Flags\n\n| Flag | Purpose | Safety |\n|------|---------|--------|\n| `-z` | Force — overwrite existing encrypted file | Safe |\n| `-n` | Recursive — process folders recursively | Safe |\n| `-c` | Clean — **delete source after encrypt\u002Fdecrypt** | DESTRUCTIVE — opt-in with confirmation |\n| `-j` | Trio = `-z -c -n` — **includes delete-source** | DESTRUCTIVE — opt-in with confirmation |\n| `-i` | Get info on an encrypted file | Safe (read only) |\n| `-o` | Specify output file name | Safe |\n| `-7` | Print the device's current GPS location (no other flags needed) | PRIVACY-SENSITIVE — requires user consent on first use |\n\n## MFA Workflow\n\n1. **Encrypt with MFA**: Use `-2 \"+1XXXXXXXXXX\"` to register the phone number.\n2. **Decrypt with MFA**: First run decrypt with `-4 \u003Cencrypted_file>` to trigger OTP delivery, then run again with `-3 \u003COTP_CODE>`.\n\n## Examples\n\n### PlainText — Pin only\n```bash\nLE -e '''hello world''' -1 \"1234\" --PlainText\nLE -d '''\u003CENCRYPTED>''' -1 \"1234\" --PlainText\n```\n\n### PlainText — All locks\n```bash\nLE -e '''secret data''' -w pass.letxt -1 \"1122\" -2 \"+19199870623\" -l \"2026\u002F04\u002F12 17:41\" -r \"2027\u002F04\u002F12 17:36\" --PlainText\n```\n\n### File — Pin only (safe, source preserved)\n```bash\nLE -e \u002Fpath\u002Fto\u002Fmyfile.txt -1 \"1234\" -z\nLE -d \u002Fpath\u002Fto\u002Fmyfile.letxt -1 \"1234\" -z\n```\n\n### Folder — Pin + Password (safe, sources preserved)\n```bash\nLE -e \u002Fpath\u002Fto\u002Fmy_folder -w pass.letxt -1 \"1234\" -z -n\nLE -d \u002Fpath\u002Fto\u002Fmy_folder -w pass.letxt -1 \"1234\" -z -n\n```\n\n### File — destructive (user asked to delete source)\n```bash\n# Only after explicit user confirmation\nLE -e \u002Fpath\u002Fto\u002Fmyfile.txt -1 \"1234\" -j\n```\n\n### Get info on encrypted file\n```bash\nLE -i \u002Fpath\u002Fto\u002Fmyfile.letxt\n```\n\n### Get current device location\nRequires user consent on first use in a session (privacy-sensitive — accesses device GPS).\n```bash\nLE -7\n```\n\n## Workflow\n\n1. **Determine the mode:** PlainText (`--PlainText`) for inline strings, or File\u002FFolder for files and directories.\n2. **Resolve the binary** via `$LE_BIN`, `command -v LE`, or ask the user.\n3. **Gather lock inputs:** Which locks to apply and their values.\n4. **Pick safe defaults:** `-z` for files; `-z -n` for folders. Do not add `-c` or `-j` unless the user explicitly confirmed source deletion.\n5. **Build the command** with the appropriate flags.\n6. **Execute via Bash** and return the result.\n7. **For decryption**, remind the user they need the same lock values used during encryption.\n\n## Important Notes\n\n- No API key is needed — LE runs entirely locally.\n- Phone numbers for MFA (`-2`) must be in E.164 format.\n- Time lock dates use `YYYY\u002FMM\u002FDD HH:MM` format. Follow the Date & Time Rules above.\n- Time locks require both `-l` (start) and `-r` (end).\n- The password file (`.letxt`) should be an encrypted password file created with `LE -e pass.txt -q`.\n- Geo-location locks work in two stages: **create a key file once**, then **reuse it** to lock as many files\u002Ffolders as you want.\n\n  **Stage 1 — Create the `.lecsv` key file from a GPS CSV (`-v`):**\n  - Input: a plain CSV of GPS locations with distance (e.g., `location.csv`).\n  - `-v` is a switch (no value); LE produces `location.lecsv` alongside the input.\n  - MUST be paired with `-1` (pin) or `-2` (MFA) — otherwise LE errors with \"Either Pin or MFA should be enabled for Password\u002FLocation file\".\n  ```bash\n  LE -e location.csv -v -1 1122 -z\n  LE -e location.csv -v -2 \"+1YourPhoneNumber\" -z\n  ```\n\n  **Stage 2 — Use the `.lecsv` key file to lock files\u002Ffolders (`-b`):**\n  - `-b \u003Cpath.lecsv>` is used **only on encryption**.\n  - **On decryption, do NOT pass `-b`** — LE reads the embedded location reference from the encrypted file itself. Just run `LE -d \u003Cfile> -z`.\n  - No pin\u002FMFA pairing required — the key file is self-contained.\n  ```bash\n  # Encrypt (pass -b with the key file)\n  LE -e example.txt -b location.lecsv -z\n\n  # Decrypt (do NOT pass -b)\n  LE -d example.letxt -z\n  ```\n","# LESecureLocal — LESecure Local \u002F On-Prem Skills\n\nEncrypt and decrypt **plain text, files, and folders** using the LE desktop binary. No API key is needed — everything runs locally. No data leaves your machine.\n\n## Project Links\n\n| Resource | URL |\n|---|---|\n| Source code & documentation | \u003Chttps:\u002F\u002Fgithub.com\u002FSPAlgorithm\u002FLE> |\n| Cloud alternative | LESecureCl skill (uses the LESecure API) |\n\n## ROUTING RULES (MANDATORY)\n\n- **Files and folders MUST always use LESecure Local.** Never use LESecure Cloud for file\u002Ffolder encryption. If the user asks to encrypt files\u002Ffolders via cloud, inform them: \"File\u002Ffolder encryption is only supported via LESecure Local (desktop).\" and use this skill.\n- **Safe-by-default flags for files\u002Ffolders.** Always pass `-z` (force overwrite) and — when the target is a directory — `-n` (recursive). **Never pass `-c` (clean\u002Fdelete source) or `-j` (trio = `-z -c -n`) without explicit user confirmation**, because both delete the original file after encrypting. See the \"Destructive Flags\" rules below.\n- **For plain text**, ask the user: \"Would you like to use **LESecure Cloud** (API) or **LESecure Local** (desktop)?\" and proceed accordingly.\n- **Current location queries** — when the user asks \"what's my current location\", \"whereami\", \"where am I\", or any equivalent, run `LE -7` and share the output. No other flags are needed. **Note:** `LE -7` accesses device GPS — this is a privacy-sensitive operation. On first use in a session, inform the user: \"This will query your device's GPS location via LE.\" Proceed only after acknowledgment.\n\n## Destructive Flags — `-c` and `-j` (MANDATORY)\n\n- `-c` (clean) **deletes the source file after encryption or decryption**. It is irreversible in-place data loss.\n- `-j` is a trio that **includes `-c`**, so it is also destructive.\n- Never silently add `-c` or `-j`. Before using either, ask the user explicitly, e.g.: \"This will delete the source `\u003Cfile>` after the operation. Confirm with 'yes, delete source' to proceed.\"\n- If the user does not confirm, use only `-z` (and `-n` for folders). The source stays on disk.\n- When the user explicitly asks for `-j` or \"clean\u002Fdelete source after\", use `-j` and state in the response that the source was removed.\n\n## Binary Location (configuration)\n\nThe skill looks for the `LE` binary in this order:\n\n1. The `LE_BIN` environment variable, if set (e.g., `export LE_BIN=\u002Fopt\u002Fle\u002FLE`).\n2. `LE` on `PATH` (via `command -v LE`).\n3. A user-supplied path if neither of the above resolves. In that case, **ask the user** for the binary path — do not guess or hardcode.\n\nIn examples below, `LE` is used as a shorthand for whichever path resolves. When actually invoking, expand it to the full resolved path so the command is reproducible.\n\n```bash\n# Resolve once, then reuse\nLE_BIN=\"${LE_BIN:-$(command -v LE)}\"\n\"$LE_BIN\" --help\n```\n\n## Date & Time Rules (MANDATORY)\n\nAll date\u002Ftime handling for this skill follows these rules — no exceptions:\n\n1. **Always use EST\u002FEDT (America\u002FNew_York)** to calculate and send dates. The LE tool interprets `-l` and `-r` in EST\u002FEDT.\n2. **Start time (`-l`) = current EST + 2 minutes** by default. This buffer prevents the \"date must be in future\" error.\n3. **End time (`-r`) = start time + the user's requested duration**.\n4. **Cross-platform time computation.** Prefer Python because `date` flag syntax differs between BSD (macOS) and GNU (Linux). Python 3 is available on both.\n\n   **Input safety:** The `\u003CN>` duration value is passed as `sys.argv[1]` and cast via `int()` inside the Python script — any non-integer input raises `ValueError` and the script exits without executing. **Never concatenate or interpolate user input directly into the `python3 -c` string.** Always pass values as positional arguments (`sys.argv`).\n\n   ```bash\n   # Start time (now + 2 minutes, EDT\u002FEST) — no user input needed\n   python3 -c \"from datetime import datetime,timedelta; from zoneinfo import ZoneInfo; print((datetime.now(ZoneInfo('America\u002FNew_York'))+timedelta(minutes=2)).strftime('%Y\u002F%m\u002F%d %H:%M'))\"\n\n   # End time (now + 2 min + N minutes) — N is passed as argv[1], cast to int()\n   python3 -c \"import sys; from datetime import datetime,timedelta; from zoneinfo import ZoneInfo; N=int(sys.argv[1]); print((datetime.now(ZoneInfo('America\u002FNew_York'))+timedelta(minutes=2+N)).strftime('%Y\u002F%m\u002F%d %H:%M'))\" \u003CN>\n\n   # End time (now + 2 min + N hours) — N is passed as argv[1], cast to int()\n   python3 -c \"import sys; from datetime import datetime,timedelta; from zoneinfo import ZoneInfo; N=int(sys.argv[1]); print((datetime.now(ZoneInfo('America\u002FNew_York'))+timedelta(minutes=2,hours=N)).strftime('%Y\u002F%m\u002F%d %H:%M'))\" \u003CN>\n   ```\n   Fallback (`date`) — only if Python is unavailable:\n   - macOS\u002FBSD: `TZ=America\u002FNew_York date -v+2M \"+%Y\u002F%m\u002F%d %H:%M\"`\n   - Linux\u002FGNU: `TZ=America\u002FNew_York date -d '+2 minutes' \"+%Y\u002F%m\u002F%d %H:%M\"`\n5. **Always display the window back to the user in EDT\u002FEST**.\n\n## Two Modes\n\n### 1. PlainText Mode (`--PlainText` \u002F `-p`)\n\nEncrypt\u002Fdecrypt inline strings. The LE binary expects the data wrapped in triple single quotes (`'''...'''`).\n\n#### Input Sanitization (MANDATORY)\n\n**Never interpolate raw user input directly into the shell command.** The `'''...'''` quoting breaks if the data contains single quotes, enabling shell injection. Before building the command:\n\n1. **Validate:** reject or escape any single quotes (`'`) in the user's plaintext. Replace each `'` with `'\\''` (end quote, escaped literal quote, reopen quote).\n2. **Alternatively, use a shell variable** to isolate user data from the command string:\n   ```bash\n   # Store user data in a variable — shell expansion is safe inside triple quotes\n   LEDATA='user provided text here'\n   LE -e \"'''${LEDATA}'''\" \u003CLOCK_FLAGS> --PlainText\n   ```\n3. **Never use `eval`** or backtick interpolation with user-supplied text.\n\n```bash\n# Encrypt (with sanitized data)\nLE -e '''\u003CSANITIZED_DATA>''' \u003CLOCK_FLAGS> --PlainText\n\n# Decrypt (encrypted output is safe — no special chars)\nLE -d '''\u003CENCRYPTED_DATA>''' \u003CLOCK_FLAGS> --PlainText\n```\n\n### 2. File \u002F Folder Mode\n\nDefault flags (safe):\n- **File:** `-z`\n- **Folder:** `-z -n`\n\nDestructive extras (only with explicit user confirmation, see rules above): add `-c` to also delete the source, or use `-j` (= `-z -c -n`).\n\n```bash\n# Safe file encrypt \u002F decrypt (source file preserved)\nLE -e \u003CFILE>   \u003CLOCK_FLAGS> -z\nLE -d \u003CFILE.letxt> \u003CLOCK_FLAGS> -z\n\n# Safe folder encrypt \u002F decrypt (source folder preserved)\nLE -e \u003CFOLDER> \u003CLOCK_FLAGS> -z -n\nLE -d \u003CFOLDER> \u003CLOCK_FLAGS> -z -n\n\n# Destructive — only after explicit user confirmation\nLE -e \u003CFILE_OR_FOLDER> \u003CLOCK_FLAGS> -j\n```\n\n**Naming notes:**\n- Encrypted files get a `.le` prefix on the extension (e.g., `example.txt` becomes `example.letxt`); use the `.letxt` filename when decrypting.\n- For folders, the individual files inside get the `.le` prefix on their extensions. The folder name itself stays the same.\n\n## Available Locks\n\n| Flag | Lock Type | Value | Example |\n|------|-----------|-------|---------|\n| `-1` | Pin\u002FCode | Numeric string | `\"1122\"` |\n| `-w` | Password | Password file (`.letxt`) or passphrase | `pass.letxt` |\n| `-2` | MFA | Phone number (E.164) | `\"+19199870623\"` |\n| `-3` | OTP | OTP code for decryption | `\"123456\"` |\n| `-l` | Time lock start | `YYYY\u002FMM\u002FDD HH:MM` | `\"2026\u002F04\u002F12 17:41\"` |\n| `-r` | Time lock end | `YYYY\u002FMM\u002FDD HH:MM` | `\"2027\u002F04\u002F12 17:36\"` |\n| `-b` | Location lock — use existing `.lecsv` key file (**encrypt only**; omit on decrypt) | Path to `.lecsv` file | `location.lecsv` |\n| `-v` | Location lock — create a new `.lecsv` key file from a GPS CSV (switch, no value) | (no value) | `-v` |\n\n### Additional Flags\n\n| Flag | Purpose | Safety |\n|------|---------|--------|\n| `-z` | Force — overwrite existing encrypted file | Safe |\n| `-n` | Recursive — process folders recursively | Safe |\n| `-c` | Clean — **delete source after encrypt\u002Fdecrypt** | DESTRUCTIVE — opt-in with confirmation |\n| `-j` | Trio = `-z -c -n` — **includes delete-source** | DESTRUCTIVE — opt-in with confirmation |\n| `-i` | Get info on an encrypted file | Safe (read only) |\n| `-o` | Specify output file name | Safe |\n| `-7` | Print the device's current GPS location (no other flags needed) | PRIVACY-SENSITIVE — requires user consent on first use |\n\n## MFA Workflow\n\n1. **Encrypt with MFA**: Use `-2 \"+1XXXXXXXXXX\"` to register the phone number.\n2. **Decrypt with MFA**: First run decrypt with `-4 \u003Cencrypted_file>` to trigger OTP delivery, then run again with `-3 \u003COTP_CODE>`.\n\n## Examples\n\n### PlainText — Pin only\n```bash\nLE -e '''hello world''' -1 \"1234\" --PlainText\nLE -d '''\u003CENCRYPTED>''' -1 \"1234\" --PlainText\n```\n\n### PlainText — All locks\n```bash\nLE -e '''secret data''' -w pass.letxt -1 \"1122\" -2 \"+19199870623\" -l \"2026\u002F04\u002F12 17:41\" -r \"2027\u002F04\u002F12 17:36\" --PlainText\n```\n\n### File — Pin only (safe, source preserved)\n```bash\nLE -e \u002Fpath\u002Fto\u002Fmyfile.txt -1 \"1234\" -z\nLE -d \u002Fpath\u002Fto\u002Fmyfile.letxt -1 \"1234\" -z\n```\n\n### Folder — Pin + Password (safe, sources preserved)\n```bash\nLE -e \u002Fpath\u002Fto\u002Fmy_folder -w pass.letxt -1 \"1234\" -z -n\nLE -d \u002Fpath\u002Fto\u002Fmy_folder -w pass.letxt -1 \"1234\" -z -n\n```\n\n### File — destructive (user asked to delete source)\n```bash\n# Only after explicit user confirmation\nLE -e \u002Fpath\u002Fto\u002Fmyfile.txt -1 \"1234\" -j\n```\n\n### Get info on encrypted file\n```bash\nLE -i \u002Fpath\u002Fto\u002Fmyfile.letxt\n```\n\n### Get current device location\nRequires user consent on first use in a session (privacy-sensitive — accesses device GPS).\n```bash\nLE -7\n```\n\n## Workflow\n\n1. **Determine the mode:** PlainText (`--PlainText`) for inline strings, or File\u002FFolder for files and directories.\n2. **Resolve the binary** via `$LE_BIN`, `command -v LE`, or ask the user.\n3. **Gather lock inputs:** Which locks to apply and their values.\n4. **Pick safe defaults:** `-z` for files; `-z -n` for folders. Do not add `-c` or `-j` unless the user explicitly confirmed source deletion.\n5. **Build the command** with the appropriate flags.\n6. **Execute via Bash** and return the result.\n7. **For decryption**, remind the user they need the same lock values used during encryption.\n\n## Important Notes\n\n- No API key is needed — LE runs entirely locally.\n- Phone numbers for MFA (`-2`) must be in E.164 format.\n- Time lock dates use `YYYY\u002FMM\u002FDD HH:MM` format. Follow the Date & Time Rules above.\n- Time locks require both `-l` (start) and `-r` (end).\n- The password file (`.letxt`) should be an encrypted password file created with `LE -e pass.txt -q`.\n- Geo-location locks work in two stages: **create a key file once**, then **reuse it** to lock as many files\u002Ffolders as you want.\n\n  **Stage 1 — Create the `.lecsv` key file from a GPS CSV (`-v`):**\n  - Input: a plain CSV of GPS locations with distance (e.g., `location.csv`).\n  - `-v` is a switch (no value); LE produces `location.lecsv` alongside the input.\n  - MUST be paired with `-1` (pin) or `-2` (MFA) — otherwise LE errors with \"Either Pin or MFA should be enabled for Password\u002FLocation file\".\n  ```bash\n  LE -e location.csv -v -1 1122 -z\n  LE -e location.csv -v -2 \"+1YourPhoneNumber\" -z\n  ```\n\n  **Stage 2 — Use the `.lecsv` key file to lock files\u002Ffolders (`-b`):**\n  - `-b \u003Cpath.lecsv>` is used **only on encryption**.\n  - **On decryption, do NOT pass `-b`** — LE reads the embedded location reference from the encrypted file itself. Just run `LE -d \u003Cfile> -z`.\n  - No pin\u002FMFA pairing required — the key file is self-contained.\n  ```bash\n  # Encrypt (pass -b with the key file)\n  LE -e example.txt -b location.lecsv -z\n\n  # Decrypt (do NOT pass -b)\n  LE -d example.letxt -z\n  ```\n",{"name":5,"triggers":24,"description":7},[25,26,27,28,29,30,31,32,33,34,35,36,37,38],"LESecure Local","LESecure Desktop","LESecure On-Prem","LE local","LE desktop","encrypt file","decrypt file","encrypt folder","decrypt folder","what's my current location","what is my current location","whereami","where am i","current location","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fl\u002Flesecurelocal",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill LESecureLocal",{"tool":54,"command":55},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill LESecureLocal",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill LESecureLocal","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fl\u002Flesecurelocal\u002FSKILL.md",true,[],[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]