Skill python-services
✓ VerifiedMenyediakan pola untuk membangun CLI tools, beban kerja paralel asinkron, layanan backend FastAPI, dan sistem background job di Python.
- Bintang GitHub
- 36
- File
- 2
- Commit terakhir
- 11 Nov 2026
- Lisensi
- MIT
- Tool yang diizinkan
- —
Apa fungsi skill python-services?
Menyediakan pola untuk membangun CLI tools, beban kerja paralel asinkron, layanan backend FastAPI, dan sistem background job di Python.
Ringkasan dibuat dari SKILL.md skill ini.
Tentang skill python-services
Developer yang membangun infrastruktur berbasis Python dapat menggunakan skill ini untuk mengimplementasikan pola standar untuk CLI tools, layanan backend, dan beban kerja asinkron. Skill ini memberikan panduan spesifik mengenai tooling modern seperti uv untuk manajemen dependency, ruff untuk linting, dan ty untuk type checking. Saat sebuah agent memuat skill ini, ia dapat menghasilkan kode terstruktur untuk aplikasi FastAPI menggunakan repository patterns, SQLAlchemy AsyncSession, dan Pydantic settings untuk konfigurasi.
Skill ini juga mencakup model eksekusi yang kompleks, termasuk asyncio untuk tugas I/O-bound dan multiprocessing untuk komputasi CPU-bound. Tersedia juga template untuk sistem background job menggunakan Celery atau Dramatiq, dengan penekanan pada idempotency dan logika retry menggunakan tenacity. Untuk sistem yang siap produksi, skill ini menyertakan instruksi untuk observability melalui structlog dan Prometheus, guna memastikan agent menghasilkan kode yang mampu melakukan distributed tracing dan structured logging.
Apa yang bisa dilakukan agent dengannya
- 1Implementasi konkurensi I/O asinkronMenulis kode untuk menangani banyak panggilan jaringan secara bersamaan sambil membatasi rate request.
Ditulis dari SKILL.md milik skill tersebut. Setiap use case diverifikasi dengan kutipan darinya.
Cara install skill python-services
Setiap perintah menyalin folder skill ke direktori skills client. Restart client atau mulai sesi baru untuk memuatnya.Install skill python-services di Claude Code
~/.claude/skills/python-services/SKILL.md
$ npx degit iliaal/whetstone/distillery/generated-skills/python-services ~/.claude/skills/python-servicesInstall skill python-services di Claude Code (project)
.claude/skills/python-services/SKILL.md
$ npx degit iliaal/whetstone/distillery/generated-skills/python-services .claude/skills/python-servicesInstall skill python-services di Codex
~/.agents/skills/python-services/SKILL.md
$ npx degit iliaal/whetstone/distillery/generated-skills/python-services ~/.agents/skills/python-servicesInstall skill python-services di Gemini CLI
~/.gemini/skills/python-services/SKILL.md
$ npx degit iliaal/whetstone/distillery/generated-skills/python-services ~/.gemini/skills/python-servicesInstall skill python-services di Claude.ai
npx degit iliaal/whetstone/distillery/generated-skills/python-services python-services && zip -r python-services.zip python-services # claude.ai → Customize → Skills → + → Create skill → Upload a skill → python-services.zip
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos cek otomatis kami. Ini bukan audit keamanan: baca skripnya sebelum membiarkan agent menjalankannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauiliaal/whetstone/distillery/generated-skills/python-services is public and reachablegithub.com/iliaal/whetstone/tree/HEAD/distillery/generated-s ↗Lolos
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit 2026-11-11github.com/iliaal/whetstone/commits ↗Lolos
- Skrip tanpa unduh-lalu-jalankan atau pencurian kredensialNo scripts in the skill folderLolos
- Tidak ada instruksi tersembunyi di SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/iliaal/whetstone/blob/HEAD/distillery/generated-s ↗Lolos
- Tool yang diizinkan otomatis dibatasiNo pre-approved tools; the agent asks before using onegithub.com/iliaal/whetstone/blob/HEAD/distillery/generated-s ↗Lolos
- SKILL.md mengikuti format Agent SkillsValid name and description; says when to use it; 159 linesgithub.com/iliaal/whetstone/blob/HEAD/distillery/generated-s ↗Lolos
SKILL.md
Lihat di GitHubPython Services & CLI
Modern Tooling
| Tool | Replaces | Purpose |
|---|---|---|
| uv | pip, virtualenv, pyenv, pipx | Package/dependency management |
| ruff | flake8, black, isort | Linting + formatting |
| ty | mypy, pyright | Type checking (Astral, faster) |
uv init --package myprojectfor distributable packages,uv initfor appsuv add <pkg>,uv add --group dev <pkg>, never edit pyproject.toml deps manuallyuv run <cmd>instead of activating venvsuv.lockgoes in version control- Use
[dependency-groups](PEP 735) for dev/test/docs, not[project.optional-dependencies] - PEP 723 inline metadata for standalone scripts with deps
ruff check --fix . && ruff format .for lint+format in one pass
CLI Tools
Entry points in pyproject.toml:
[project.scripts]
my-tool = "my_package.cli:main"
Click (recommended for complex CLIs):
import click
@click.group()
@click.version_option()
def cli(): ...
@cli.command()
@click.argument("name")
@click.option("--count", default=1, type=int)
def greet(name: str, count: int):
for _ in range(count):
click.echo(f"Hello, {name}!")
def main():
cli()
argparse for simple CLIs — subparsers for subcommands, parser.add_argument("--output", "-o").
Use src/ layout. Include py.typed for type hints. importlib.resources.files() for package data access.
Parallelism
| Workload | Approach |
|---|---|
| Many concurrent I/O calls | asyncio (gather, create_task) |
| CPU-bound computation | multiprocessing.Pool or concurrent.futures.ProcessPoolExecutor |
| Mixed I/O + CPU | asyncio.to_thread() to offload blocking work |
| Simple scripts, few connections | Stay synchronous |
Key rule: Stay fully sync or fully async within a call path.
asyncio patterns:
asyncio.gather(*tasks)for concurrent I/O — usereturn_exceptions=Truefor partial failure toleranceasyncio.Semaphore(n)to limit concurrency (rate limiting external APIs)asyncio.wait_for(coro, timeout=N)for timeoutsasyncio.Queuefor producer-consumerasyncio.Lockwhen coroutines share mutable state- Never block the event loop:
asyncio.to_thread(sync_fn)for sync libs,aiohttp/httpx.AsyncClientfor HTTP - Handle
CancelledError— always re-raise after cleanup - Async generators (
async for) for streaming/pagination
multiprocessing for CPU-bound:
from concurrent.futures import ProcessPoolExecutor
with ProcessPoolExecutor(max_workers=4) as pool:
results = list(pool.map(cpu_task, items))
FastAPI Services
Project structure:
app/
├── api/v1/endpoints/ # Route handlers
├── core/ # config.py, security.py, database.py
├── models/ # SQLAlchemy models
├── schemas/ # Pydantic request/response
├── services/ # Business logic
├── repositories/ # Data access (generic CRUD base)
└── main.py # Lifespan, middleware, router includes
Lifespan for startup/shutdown: @asynccontextmanager async def lifespan(app):
Configuration — pydantic_settings.BaseSettings with model_config = {"env_file": ".env"}. Required fields = no default (fails fast at boot). env_nested_delimiter = "__" for grouped config. secrets_dir for Docker/K8s mounted secrets.
Dependency injection — Depends(get_db) for sessions, Depends(get_current_user) for auth. Override in tests: app.dependency_overrides[get_db] = mock_db.
Async DB — SQLAlchemy AsyncSession with asyncpg. Session-per-request via async with AsyncSessionLocal() as session: yield session.
Repository pattern — Generic BaseRepository[ModelType, CreateSchema, UpdateSchema] with get/get_multi/create/update/delete. Service layer holds business logic, routes stay thin.
Background Jobs
- Return job ID immediately, process async. Client polls
/jobs/{id}for status - Celery:
@app.task(bind=True, max_retries=3, autoretry_for=(ConnectionError,))— exponential backoff:raise self.retry(countdown=2**self.request.retries * 60) - Alternatives: Dramatiq (modern Celery), RQ (simple Redis), cloud-native (SQS+Lambda, Cloud Tasks)
- Idempotency is mandatory — tasks may retry. Use idempotency keys for external calls, check-before-write, upsert patterns
- Dead letter queue for permanently failed tasks after max retries
- Task workflows:
chain(a.s(), b.s())for sequential,group(...)for parallel,chord(group, callback)for fan-out/fan-in
Resilience
Retries with tenacity:
from tenacity import retry, stop_after_attempt, wait_exponential_jitter, retry_if_exception_type
@retry(
retry=retry_if_exception_type((ConnectionError, TimeoutError)),
stop=stop_after_attempt(5) | stop_after_delay(60),
wait=wait_exponential_jitter(initial=1, max=30),
before_sleep=log_retry_attempt,
)
def call_api(url: str) -> dict: ...
- Retry only transient errors: network, 429/502/503/504. Never retry 4xx (except 429), auth errors, validation errors
- Every network call needs a timeout
@fail_safe(default=[])decorator for non-critical paths — return cached/default on failure- Stack decorators:
@traced @with_timeout(30) @retry(...)— separate infra from business logic
Observability
- structlog for JSON structured logging. Configure once at startup with
JSONRenderer,TimeStamper,merge_contextvars - Correlation IDs — generate at ingress (
X-Correlation-IDheader), bind tocontextvars, propagate to downstream calls - Log levels: DEBUG=diagnostics, INFO=operations, WARNING=anomalies handled, ERROR=failures needing attention. Never log expected behavior at ERROR
- Prometheus metrics — track latency (Histogram), traffic (Counter), errors (Counter), saturation (Gauge). Keep label cardinality bounded (no user IDs)
- OpenTelemetry for distributed tracing across services
Discipline
- For non-trivial changes, pause and ask: "is there a more elegant way?" Skip for obvious fixes.
- Simplicity first — every change as simple as possible, impact minimal code
- Only touch what's necessary — avoid introducing unrelated changes
- No hacky workarounds — if a fix feels wrong, step back and implement the clean solution
Error Handling
- Validate inputs at boundaries before expensive ops. Report all errors at once when possible
- Use specific exceptions:
ValueError,TypeError,KeyError, not bareException raise ServiceError("upload failed") from e— always chain to preserve debug trail- Convert external data to domain types (enums, Pydantic models) at system boundaries
- Batch processing:
BatchResult(succeeded={}, failed={})— don't let one item abort the batch - Pydantic
BaseModelwithfield_validatorfor complex input validation
Berkas dalam skill ini
2Pertanyaan seputar skill python-services
Bagaimana cara install skill python-services di Claude Code?
Jalankan npx degit iliaal/whetstone/distillery/generated-skills/python-services ~/.claude/skills/python-services. Claude Code memuat skill dari ~/.claude/skills (semua proyek) atau .claude/skills (satu proyek) dan menggunakan skill saat deskripsinya cocok dengan tugas.
Client mana saja yang bisa menggunakan skill python-services?
Client apa pun yang membaca format Agent Skills: Claude Code, Codex, Gemini CLI, dan claude.ai (unggah sebagai ZIP). Script dalam skill hanya berjalan di client yang mengizinkan eksekusi kode.