encrypting-and-decrypting-data

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill encrypting-and-decrypting-data

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.

57%

Overall

Validation — 88%

Implementation — 20%

Activation — 90%

SKILL.md

Review

Evals

Validation

88%

Warnings & errors only

Criteria	Description	Result
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning

	Total	14 / 16 Passed

Implementation

20%

This skill content is overly verbose and lacks actionable, executable guidance. It describes what the encryption-tool plugin does conceptually but provides no concrete code, commands, or plugin invocation syntax. The workflow steps are too abstract and missing critical details like key handling, error recovery, and validation.

Suggestions

Add concrete, executable examples showing actual plugin invocation syntax (e.g., the exact command or API call to encrypt a file with AES)

Remove explanatory content about what encryption is and why it's useful - Claude already knows this

Include specific key management workflow: how to provide keys, where they're stored, how to handle missing keys

Add validation steps and error handling guidance (e.g., what to do if decryption fails, how to verify encryption succeeded)

Dimension	Reasoning	Score
Conciseness	The content is verbose and explains concepts Claude already knows (what encryption is, why to use it). Phrases like 'empowers Claude', 'seamlessly', and 'ensuring confidentiality and integrity' are filler. The 'When to Use This Skill' section restates obvious information.	1 / 3
Actionability	No executable code or concrete commands are provided. The examples describe what 'the skill will' do in abstract terms rather than showing actual plugin invocations, API calls, or command syntax. There's no copy-paste ready guidance.	1 / 3
Workflow Clarity	Steps are listed in a sequence, but there are no validation checkpoints, no error handling guidance, and no feedback loops. Key management is mentioned in best practices but not integrated into the workflow. The decryption example assumes keys are 'available or prompted for' without specifying how.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but everything is inline in one file. There are no references to external documentation for advanced topics like algorithm details, key management guides, or API reference. The content could benefit from splitting detailed guidance into separate files.	2 / 3
	Total	6 / 12 Passed

Activation

90%

This is a solid skill description that clearly communicates when to use it with explicit trigger terms and good coverage of user language. The main weakness is the lack of specific concrete actions - it mentions 'various algorithms' and 'various encryption methods' without specifying which ones (e.g., AES, RSA, file types supported). The description is functional but could be more precise about capabilities.

Suggestions

Replace vague phrases like 'various algorithms' and 'various encryption methods' with specific examples (e.g., 'AES-256, RSA, symmetric/asymmetric encryption')

Add concrete actions beyond encrypt/decrypt such as 'generate encryption keys', 'hash passwords', or specific file format support

Dimension	Reasoning	Score
Specificity	Names the domain (encryption/decryption) and mentions 'various algorithms' and 'encryption-tool plugin', but lacks specific concrete actions like 'AES-256 encryption', 'RSA key generation', or specific file format handling.	2 / 3
Completeness	Clearly answers both what (encrypt/decrypt data using various algorithms) and when (explicit 'Use when' equivalent with 'should be used when' and 'triggered by' clauses listing specific user requests).	3 / 3
Trigger Term Quality	Includes good natural trigger terms users would say: 'encrypt data', 'decrypt a file', 'generate an encrypted file', 'secure sensitive information', 'data encryption', 'decryption', 'data security needs'.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on encryption/decryption operations with distinct triggers like 'encrypt', 'decrypt', 'encrypted file' - unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Reviewed

16 days ago

Table of Contents

Validation Implementation Activation

Is this your skill?

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.