secretcodex_skill

This skill generates creative codename options and encodes or decodes messages using classic and hybrid ciphers with user-controlled keys.
  • Python

2.6k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill secretcodex

  • _meta.json277 B
  • README.md8.8 KB
  • SKILL.md19.3 KB

Overview

This skill generates memorable code names and encodes/decodes secret messages using classic and advanced ciphers. It blends nostalgic decoder-ring fun with practical key management and layered encryption methods for secure, playful, or educational uses. It provides clear keys and sharing guidance so trusted parties can exchange messages reliably.

How this skill works

You provide the message, desired cipher(s), and a key (or request a generated key). The skill supports single ciphers (Caesar, ROT13, Atbash, Pigpen), intermediate methods (Polybius, Vigenère, Rail Fence), advanced options (Playfair, Columnar Transposition, One-Time Pad) and hybrid pipelines (e.g., Vigenère → Rail Fence). It can also produce creative code names with tones and phonetic spellings and returns encoding steps so recipients can decode manually.

When to use it

  • Creating code names for projects, teams, or events
  • Sending private messages where manual key sharing is acceptable
  • Teaching cryptography basics and practical shifting/translation rules
  • Adding layered puzzles or mystery elements to games and scavenger hunts
  • Protecting sensitive short notes when strong key management is in place

Best practices

  • Choose the right cipher for the risk: simple ciphers for fun, Playfair or hybrids for stronger secrecy, one-time pad for maximum security
  • Manage keys separately from ciphertext—never send key and message on the same channel
  • Use long, non-obvious keywords or truly random one-time keys when security matters
  • Change keys regularly and never reuse one-time-pad keys
  • Provide phonetic spellings for code names when voice clarity matters

Example use cases

  • Operation naming: generate 5–10 operation or personnel codenames with meanings and phonetics
  • Private meetup: encode meeting details with Vigenère using a keyword previously shared in person
  • Scavenger hunt: create progressive clues using Caesar, Rail Fence, then Playfair for increasing difficulty
  • Educational lab: demonstrate frequency attacks on Caesar and resilience improvements using Playfair or double encryption
  • Secure short notes: use one-time pad keys exchanged in person for maximum confidentiality

FAQ

Yes. Layering ciphers (for example Vigenère followed by Rail Fence) increases complexity. Decode steps must be reversed in order by the recipient.

How do I share keys safely?

Prefer in-person exchange or a separate secure channel. Never transmit a key and its ciphertext on the same platform. Use pre-arranged secrets for ongoing use.

Is one-time pad always unbreakable?

Only if the pad is truly random, at least as long as the message, used once, and kept secret. Poor randomness or reuse destroys its security.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational