AgentStack
SKILL verified MIT Self-run

Writing Python

skill-alexei-led-cc-thingz-writing-python · by alexei-led

Idiomatic Python 3.12+ development. Use when writing Python code, CLI

No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add skill-alexei-led-cc-thingz-writing-python

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Writing Python? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Python Development

Use this only for Python 3.12+ code. Keep language-agnostic rules out of this skill.

Read First

Read [principles.md](references/principles.md) before generating or changing Python code.

Core Rules

  • Prefer existing project patterns over these defaults.
  • Inspect the project Python target before using 3.12-only syntax.
  • Prefer stdlib and existing dependencies before adding packages.
  • Validate untyped boundary input before it spreads.

Comments and Docstrings

  • Prefer clear names and small functions over explanatory comments.
  • Add comments only for non-obvious constraints, invariants, side effects, tradeoffs, or public contracts.
  • Keep comments short. Move longer rationale to docs, issue links, or design notes.
  • Do not comment obvious code or restate the syntax.
  • Keep tests readable without comments; add one only for unobvious fixtures, timing, concurrency, or regression context.
  • Use docstrings for public or non-obvious modules, classes, functions, and methods. Do not restate the signature.

Conditional References

  • [patterns.md](references/patterns.md) — read for module design, typing, async, config, file I/O, and error patterns.
  • [cli.md](references/cli.md) — read before writing or changing Python CLIs.
  • [testing.md](references/testing.md) — read before adding or reshaping Python tests; treat slow tests as feedback-loop defects.

Verification

Run project-configured tests, lint, format, and type checks. Prefer focused pytest commands for the edit loop, then the broader project command before final output. Prefer pytest, ruff, and pyright when present.

If a tool is not configured, say so and run the closest available gate. If a check fails, diagnose the cause, make a targeted fix, and rerun the relevant check.

Python-Specific Failure Cases

  • No clear project root: locate pyproject.toml before editing or choosing commands.
  • Unknown Python target: inspect pyproject.toml, .python-version, CI, or lockfiles before using 3.12-only syntax.
  • Type checker reports missing attributes: check imports, package exports, and runtime shape before loosening types.

Final Response

Include:

  • changed files
  • checks run and results
  • checks skipped with reasons
  • remaining risks or follow-ups

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.