Skip to content
TrustedSkillsbeta
Back to all skills

M12 Lifecycle

Checked
zhanghandong·vlatest·other

M12 Lifecycle manages asset lifecycles, optimizing maintenance and reducing downtime by tracking equipment status & schedules effectively.

Repository

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 actionbook/rust-skills --skill m12-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

zhanghandong

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 zhanghandong/rust-skills at 5c40d3ad78.

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

Commit
5c40d3ad78
Manifest
skills/m12-lifecycle/SKILL.md
Scanned
1 file, 170 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

The m12-lifecycle skill manages the lifecycle of AI agents, including initialization, execution, and termination processes. It ensures that agents are properly set up, run efficiently, and cleanly shut down when no longer needed.

When to use it

  • When deploying AI agents for long-running tasks that require stable operation.
  • During development to test agent behavior across different lifecycle stages.
  • To ensure resource cleanup after an agent completes its task or encounters errors.
  • For managing multiple agents in parallel, ensuring each follows a defined lifecycle.

Key capabilities

  • Initialization of AI agents with configurable parameters.
  • Execution control for starting and stopping agent processes.
  • Graceful termination to release resources and save state.
  • Error handling during the lifecycle stages.

Example prompts

  • "Initialize an AI agent with default settings."
  • "Terminate all running agents after completing their tasks."
  • "Restart the agent if it fails during execution."

Tips & gotchas

  • Ensure that your environment supports the required dependencies for agent initialization.
  • Use proper error logging to diagnose issues during lifecycle transitions.