Skip to content
TrustedSkillsbeta
Back to all skills

Python Standards

Checked
akaszubski·vlatest·backend

Enforces PEP 8 and common Python style guidelines in backend code for improved readability and maintainability.

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 akaszubski/autonomous-dev --skill python-standards -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

akaszubski

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 akaszubski/autonomous-dev at 34311ec486.

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

Commit
34311ec486
Manifest
plugins/autonomous-dev/skills/python-standards/SKILL.md
Scanned
1 file, 204 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, akaszubski-python-standards, provides automated enforcement of Python coding standards. It can analyze existing codebases to identify violations and automatically refactor them to adhere to established style guides like PEP 8. This ensures consistency and improves the readability and maintainability of Python projects.

When to use it

  • Codebase cleanup: When inheriting a large, messy Python project that lacks consistent formatting.
  • New project initialization: To automatically format new code from the start, preventing style drift.
  • Automated pull request checks: Integrate into CI/CD pipelines to ensure all contributions adhere to coding standards.
  • Team onboarding: Help new developers quickly understand and contribute to a project's coding style.

Key capabilities

  • PEP 8 compliance enforcement
  • Codebase analysis for style violations
  • Automated code refactoring

Example prompts

  • "Analyze this Python file for PEP 8 violations: [file content]"
  • "Automatically format this Python script to adhere to coding standards: [script content]"
  • "Check the entire project directory /path/to/project for style issues."

Tips & gotches

The skill requires a working Python environment. Ensure that any dependencies required by the analyzed code are available, or the analysis might be inaccurate.