Skip to content
TrustedSkillsbeta
Back to all skills

Token Lifecycle

Checked
rustydotwtf·vlatest·security·MIT

Manages token creation, usage, and destruction – crucial for secure and efficient blockchain applications and decentralized systems.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add whetstoneresearch/doppler-skills --skill token-lifecycle -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

rustydotwtf

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned rustydotwtf/doppler-skills at 4f654fea1f.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 382 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill manages the lifecycle of tokens, likely within a larger system or application. It provides capabilities for creating, tracking, and potentially expiring or reclaiming these tokens. The specific purpose of the tokens is not defined but could represent access keys, temporary identifiers, or other forms of digital representation. It allows agents to interact with token management processes in an automated fashion.

When to use it

  • Automated API Access: Granting and revoking temporary access to APIs based on specific conditions.
  • Session Management: Creating and managing user sessions within an application, associating tokens with individual users.
  • Resource Allocation: Assigning limited-use resources (e.g., database connections) via unique tokens.
  • Secure Data Transfer: Generating tokens for secure file transfers or data access requests.

Key capabilities

  • Token creation
  • Token tracking
  • Token expiration/reclamation

Example prompts

  • "Create a token with an expiry time of 24 hours."
  • "Track the usage of token ABC-123."
  • "List all tokens expiring within the next week."

Tips & gotchas

The specific implementation and capabilities will depend on the underlying system managing these tokens. Ensure the agent has appropriate permissions to interact with the token management infrastructure.