quality
Validate Python Code Quality
Python projects need consistent formatting, linting, and pre-commit checks before review. This skill guides Claude, Codex, and Claude Code through Black, Ruff, BasedPyright, and pre-commit workflows.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "quality" from https://skillstore.io/skills/byronwilliamscpa-quality.md and its manifest at https://skillstore.io/api/skills/byronwilliamscpa-quality/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "quality". Format the project and report the result.
Expected outcome:
- Applied the formatting workflow with Black and Ruff.
- Formatting completed without remaining style issues.
- Review changed files before committing.
Using "quality". Run quality checks before merge.
Expected outcome:
- Linting found import order and error message issues.
- Type checking completed for source files.
- Pre-commit hooks should be rerun after fixes.
Using "quality". Review our Python quality standards.
Expected outcome:
- The workflow uses an 88 character line length.
- Ruff rules cover blind exceptions, error messages, private access, package files, debugger use, and logging formats.
- Tests and scripts have more relaxed rules.
Security Audit
SafeThe two static findings are false positives from Markdown backtick fences around documented shell commands in SKILL.md. The skill is prompt-only and lists fixed quality-tool commands; no prompt injection, exfiltration intent, or dynamic execution logic was found.
Risk Factors
⚙️ External commands (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/byronwilliamscpa-quality/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/byronwilliamscpa-quality?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/byronwilliamscpa-quality?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/byronwilliamscpa-quality/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/byronwilliamscpa-quality.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
ByronWilliamsCPA. (2026). quality security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/byronwilliamscpa-quality/audits/8BibTeX citation
@techreport{byronwilliamscpa-byronwilliamscpa-quality-2026,
author = {ByronWilliamsCPA},
title = {quality security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/byronwilliamscpa-quality/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "quality security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "ByronWilliamsCPA"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/byronwilliamscpa-quality/audits/8"
identifiers:
- type: other
value: "skillstore:byronwilliamscpa-quality:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Prepare a Python Pull Request
Format code, run lint checks, and verify pre-commit hooks before requesting review.
Check Repository Standards
Confirm that project code follows documented Python quality rules and naming expectations.
Run Pre-Commit Before Release
Validate all configured hooks before a release branch or deployment review.
Try These Prompts
Use the quality skill to format this Python project. Report which formatter steps ran and whether files changed.
Use the quality skill to run lint checks and apply safe automatic fixes. Summarize remaining issues for manual review.
Use the quality skill to run type checking and all pre-commit hooks. Explain any failures with file-level guidance.
Use the quality skill to review the repository quality workflow. Compare formatting, linting, type checking, and pre-commit coverage.
Best Practices
- Run formatting before linting so style changes are stable.
- Review automatic fixes before committing them.
- Use the same tool versions in local and continuous integration checks.
Avoid
- Running fixes without reviewing changed files.
- Ignoring type checker failures because tests pass.
- Changing lint rules only to silence current errors.
Frequently Asked Questions
What languages does this skill focus on?
Can it install missing tools?
Does it change source files automatically?
Can it replace code review?
Does it include type checking?
Can it run all pre-commit hooks?
Developer Details
Author
ByronWilliamsCPALicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
dd4a3ef9f20ddf38830950b4bb713df96b431fd6
Maintenance freshness
7/18/2026
Usage
8 downloads · 196 views
File structure
📄 SKILL.md