Skip to content
TrustedSkillsbeta
Back to all skills

M01 Ownership

Checked
actionbook·vlatest·backend

This skill establishes clear ownership and accountability for tasks within a workflow, streamlining processes and improving team responsibility.

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 m01-ownership -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

actionbook

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 actionbook/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/m01-ownership/SKILL.md
Scanned
5 files, 1,058 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

The m01-ownership skill enables AI agents to manage project ownership states within the Rust ecosystem. It allows agents to track who is responsible for specific codebases, issues, or tasks, ensuring clear accountability during development workflows.

When to use it

  • Assigning primary responsibility for a new feature or module to a specific developer.
  • Transferring maintenance duties when a project moves from active development to long-term support.
  • Clarifying ownership boundaries in multi-agent teams working on the same Rust repository.
  • Resolving disputes over who should address a critical bug by verifying current stewardship records.

Key capabilities

  • Identifies and registers the owner of specific software assets.
  • Updates ownership metadata to reflect team changes or role shifts.
  • Provides a clear audit trail for decision-making authority on code changes.

Example prompts

  • "Update the ownership record for the auth-service module to Jane Doe."
  • "Who currently owns the database migration scripts in this repository?"
  • "Transfer ownership of the legacy API integration task from Alex to Sam."

Tips & gotchas

Ensure you have write permissions to the target repository before attempting to modify ownership records, as these changes often require administrative access. This skill is designed specifically for Rust projects; using it with non-Rust codebases may result in unrecognized metadata formats.