secret-tasks

Generate keys, configure recipients, create encrypted task plans, and decrypt tasks using the Safe CLI.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/smithclay/skills --skill secret-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-tasks
Source: https://github.com/smithclay/skills/tree/main/plugins/secret-tasks/skills/secret-tasks
Command: npx skills add https://github.com/smithclay/skills --skill secret-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides secure, encrypted task management by enabling users to generate cryptographic keypairs, configure access for recipients, create encrypted task plans, and decrypt task content for authorized teams.

Core Features & Use Cases

  • Generate keypairs for encryption and decryption using the safe CLI.
  • Configure private keys and manage a list of recipients who can decrypt tasks.
  • Create encrypted task plans and store them safely, enabling multi-agent orchestration.
  • Decrypt and reveal task descriptions when authorized, ensuring confidentiality.

Quick Start

Activate the secret-tasks skill with triggers like secret tasks or encrypted tasks, then follow the workflow to generate a keypair, configure the private key, add recipients, create an encrypted plan, and decrypt a task using the safe CLI.

Frequently Asked Questions about secret-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I encrypt task plans for a multi-user team workflow?

To encrypt task plans for multi-user workflows, you generate cryptographic keypairs, configure authorized recipients, and create encrypted task files using the safe CLI. This ensures confidential task descriptions are only accessible to designated key holders.

What is the safe CLI used for in secure task management?

The safe CLI is used for secure task management to generate encryption keypairs, configure private keys, manage recipient lists, and decrypt authorized task content. It relies on local key storage and JSON task files configured with YAML frontmatter.

Can I manage recipient access for encrypted tasks without sharing private keys?

Yes, you can manage recipient access for encrypted tasks by configuring the list of authorized recipients who can decrypt content. This controlled access approach allows multi-agent orchestration without directly sharing your private key.

Do I need to install the safe CLI before setting up encrypted tasks?

Yes, you need the safe CLI installed and appropriate environment setup to operate encrypted task management. The skill relies on the safe CLI tool and local key storage to generate keypairs and decrypt JSON task files.

How does decryption work for authorized team members in a secure task plan?

Decryption works by allowing authorized key holders to reveal encrypted task descriptions using the safe CLI. Team members must have their private keys configured locally to decrypt the JSON task files and access the confidential content.