Skip to content
TrustedSkillsbeta
Back to all skills

Coding Guidelines

Checked
actionbook·vlatest·backend

Generates code adhering to ActionBook's style guide, ensuring consistency and maintainability across projects.

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 coding-guidelines -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/coding-guidelines/SKILL.md
Scanned
3 files, 118 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

Coding Guidelines

What it does

This skill provides structured coding guidelines specifically tailored for Rust development. It helps AI agents maintain consistent code quality, adhere to language best practices, and follow project-specific standards during generation.

When to use it

  • Enforcing strict formatting and style rules in Rust projects before merging pull requests.
  • Guiding AI agents to write idiomatic Rust code that leverages ownership and borrowing correctly.
  • Ensuring new team members or automated tools align with established architectural patterns.
  • Reducing technical debt by standardizing error handling and module organization across the codebase.

Key capabilities

  • Enforces Rust-specific coding standards and conventions.
  • Promotes idiomatic usage of language features like lifetimes and traits.
  • Maintains consistency in project structure and file organization.
  • Supports integration into CI/CD pipelines for automated code review.

Example prompts

  • "Generate a new Rust module for user authentication following the project's coding guidelines."
  • "Refactor this existing function to align with our established error handling patterns."
  • "Review the provided code snippet and suggest changes to meet the team's style guide requirements."

Tips & gotchas

Ensure your project has a well-defined set of Rust conventions before enabling this skill, as it relies on clear standards to be effective. Limit its scope to Rust-specific tasks to avoid confusion when working with other languages in mixed-stack projects.