This skill enables Claude to encrypt and decrypt data using various algorithms provided by the encryption-tool plugin. It should be used when the user requests to "encrypt data", "decrypt a file", "generate an encrypted file", or needs to secure sensitive information. This skill supports various encryption methods and ensures data confidentiality. It is triggered by requests related to data encryption, decryption, or general data security needs.
91
44%
Does it follow best practices?
Impact
96%
1.01xAverage score across 12 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/security/encryption-tool/skills/encryption-tool/SKILL.mdFile naming and key management
.enc extension for db.conf
100%
100%
.enc extension for api_keys.conf
100%
100%
No hardcoded key in script
100%
100%
Key via env var or argument
100%
100%
Strong algorithm used
100%
100%
README key instructions
100%
100%
Both files encrypted
100%
100%
Output path documented
100%
100%
No key in README
100%
100%
Algorithm documented
100%
100%
Data integrity verification
Integrity mechanism present
100%
100%
Integrity check on decrypt
100%
100%
Tamper detection raises error
100%
100%
Integrity embedded in payload
100%
100%
Strong algorithm selected
100%
100%
.enc extension on archive
0%
0%
Design doc explains integrity
100%
100%
Demo runs end-to-end
100%
100%
No key hardcoded
37%
0%
Algorithm matches sensitivity
40%
40%
Decryption workflow and file naming
Removes .enc for pipeline.yml
100%
100%
Removes .enc for deploy_config.json
100%
100%
Removes .enc for secrets.env
100%
100%
No hardcoded passphrase
100%
100%
Passphrase via env or arg
100%
100%
Handles all .enc files
100%
100%
Recovery manifest written
100%
100%
Identifies decryption operation
100%
100%
Manifest has correct mappings
66%
100%
Skips non-enc files
100%
100%
Default algorithm selection
Secure default algorithm
100%
100%
No algorithm in task hint
100%
100%
Justification documented
100%
100%
.enc output extension
100%
100%
Key not hardcoded
100%
100%
Key via env or argument
100%
100%
All input files encrypted
100%
100%
Encryption operation identified
100%
100%
Key storage guidance
100%
100%
Reproducible decrypt path
100%
100%
Compliance-based algorithm selection
Compliance-appropriate algorithm
100%
100%
Algorithm rationale documented
100%
100%
Key not hardcoded
100%
100%
Key via env or argument
100%
100%
.enc output extension
100%
100%
Sensitivity classification
100%
100%
Compliance framework mentioned
100%
100%
All records encrypted
100%
100%
Key management guidance
100%
100%
Decrypt instructions present
57%
57%
Encryption in automated pipeline
Encrypt step present
100%
100%
Decrypt step present
100%
100%
Operations correctly identified
100%
100%
.enc extension on encrypted files
100%
100%
Key not hardcoded
100%
100%
Key via env or argument
100%
100%
Strong algorithm used
100%
100%
Pipeline log or summary
100%
100%
Automation script runnable
100%
100%
Decrypted output restored
50%
50%
Key storage note
100%
100%
Asymmetric algorithm selection and output mode
RSA algorithm used
100%
100%
.enc output extension
100%
100%
Public key loaded from file
100%
100%
No private key hardcoded
100%
100%
Decryption script accepts key externally
100%
100%
Encrypt operates on secrets.json
100%
100%
Decrypt reverses encryption
100%
100%
README key instructions
100%
100%
Key storage guidance
50%
100%
Algorithm identified in docs
100%
100%
Console output vs file output for encrypted data
Encrypted output to stdout
100%
100%
Decrypted output to stdout
100%
100%
Secure default algorithm
100%
100%
Key not hardcoded
100%
100%
Key via env or argument
100%
100%
Demo does not hardcode key
100%
100%
Demo encrypt then decrypt
100%
100%
README usage examples
100%
100%
Separate encrypt and decrypt modes
100%
100%
Key storage note in README
100%
100%
Security audit integration with encryption verification
DES flagged as non-compliant
100%
100%
AES entries marked compliant
100%
100%
Tampered file detected
100%
100%
Integrity check per file
100%
100%
Algorithm identified per file
100%
100%
Compliance status per file
100%
100%
All four files reported
100%
100%
README explains integrity method
100%
100%
README compliance criteria
100%
100%
Report is valid JSON
100%
100%
Field-level selective encryption
Only sensitive fields encrypted
100%
100%
Encrypted field values present
100%
100%
Strong algorithm used
100%
100%
Integrity mechanism present
100%
100%
Key not hardcoded
100%
100%
Key via env or argument
100%
100%
.enc extension on output file
60%
100%
Decrypt script or function
100%
100%
Algorithm rationale documented
50%
50%
All PII fields processed
100%
100%
Key management note
66%
100%
Encrypted package for secure sharing
Operation identified as encryption
100%
100%
.enc extension on output
100%
100%
Strong algorithm used
100%
100%
Algorithm chosen for sensitivity
40%
70%
Key generation script or instructions
100%
100%
Key not hardcoded
100%
100%
Key via env or argument
0%
0%
Decrypt instructions in README
100%
100%
Key sharing guidance
100%
100%
Integrity protection present
100%
100%
All files in package encrypted
100%
100%
Key rotation and re-encryption
Decrypt with old key
100%
100%
Re-encrypt with new key
100%
100%
Operations correctly identified
100%
100%
.enc extension on output files
100%
100%
Old key not hardcoded
100%
100%
New key not hardcoded
100%
100%
Keys via env or arguments
100%
100%
Strong algorithm used
100%
100%
README rotation instructions
100%
100%
Rotation log or summary
100%
100%
Original .enc files handled
100%
100%
13d35b8
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.