Skip to content
TrustedSkillsbeta
Back to all skills

Python Code Style

Checked
wshobson·vlatest·backend·MIT

Enforces consistent Python code style (PEP 8, black formatting) to improve readability and maintainability in backend 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 wshobson/agents --skill python-code-style -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

wshobson

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 wshobson/agents at 46891e7e60.

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

Commit
46891e7e60
Manifest
plugins/python-development/skills/python-code-style/SKILL.md
Scanned
1 file, 329 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 python-code-style skill ensures Python code adheres to best practices and style guidelines, such as PEP 8 formatting. It helps maintain readability, consistency, and proper structure in Python scripts by enforcing conventions like indentation, naming, and spacing.

When to use it

  • Before committing code to a version control system to ensure clean formatting.
  • When collaborating on projects with multiple developers who follow shared style rules.
  • To automate the process of checking and fixing code style issues during development.
  • As part of continuous integration pipelines to enforce quality standards.

Key capabilities

  • Enforces PEP 8 compliance for Python code.
  • Automatically detects and fixes common style issues like incorrect indentation or spacing.
  • Provides feedback on naming conventions and structure.

Example prompts

  • "Check my Python script for PEP 8 compliance."
  • "Format this Python function according to best practices."
  • "Identify any style issues in the following code snippet."

Tips & gotchas

  • Ensure your environment has the necessary tools (like flake8 or black) installed for accurate checks.
  • Some formatting rules may conflict with project-specific conventions, so review and adjust settings as needed.