Claude Code・Cursor・Windsurf 向けの python AI Agent Skills 集合。開発者ワークフロー自動化 を重視します。
このコレクションは、Python を“ワークフロー中心”の AI エンジニアリング基盤として捉え直します。コード作成・リファクタリング、スクリプト自動化、出力検証、データパイプライン連携まで、実務で効く開発スキルを重視しています。テスト自動化や CI 向けチェック、統合しやすいユーティリティを優先し、MCP は必要に応じた副次的な実行互換として扱います。Python で本番運用するチームが、速度・信頼性・日々の開発効率を高めるための選定に役立つページです。
Primary Install Bridge
Pick One Skill, Then Take the Install Path
This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.
The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory
Once the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.
Reviewed on 2026-04-17 against Python workflow fit, installation clarity, operator handoff, and day-to-day engineering usefulness. This page is now positioned as an install-first Python entry point instead of a broad language roundup.
We prioritize this page because Python-intent users usually need a shortlist they can install, validate, and carry into real automation and delivery loops quickly.
Trust Signals
- Entries are chosen for practical Python workflow value such as scripting, automation, testing, review, and repeatable execution.
- Selection favors tools with public documentation and clear setup paths that teams can validate before wider rollout.
- The page is curated for repeatable engineering execution, not for vague language keyword coverage or generic repository popularity.
Grouping Logic
- Lead with tools that can enter a Python-centered workflow without adding heavy setup ambiguity.
- Keep the shortlist compact enough for quick comparison while still covering scripting, testing, review, and automation support.
- Use installation as the bridge from Python discovery into validated daily execution.
Maintenance & Review
Last Reviewed
2026-04-17
Cadence
Re-check when install flow, maintainer posture, or Python workflow relevance changes upstream; otherwise review monthly.
Maintained By
Killer-Skills editorial review within the recovery-focused authority queue.
Verification
Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.
Execution Examples
How These Skills Work Together In Practice
Install one Python workflow helper first
Use this page when you want one Python companion that can enter real engineering work without turning evaluation into another endless package comparison.
1. Open the installation docs before opening more Python-related repositories.
2. Choose one tool that best supports scripting, automation, testing, or review work.
3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
4. Only after the base path works, expand the setup across the wider Python workflow.
Tighten a Python automation loop
Treat the collection as an editorial filter when you need Python-adjacent tools that improve engineering quality without overcomplicating the stack.
1. Check whether the tool has stable ownership and visible install guidance.
2. Review CLI behavior so operators know what will be written and synced.
3. Use one validated path before scaling it to more scripts, jobs, or teammates.
4. Document the chosen Python workflow baseline after the first clean rollout.
The component-refactoring skill simplifies high-complexity React components, improving code quality and reducing maintenance efforts for developers. It utilizes patterns and workflows to refactor components, making them more efficient and easier to understand.
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
Guide for implementing oRPC contract-first API patterns in Dify frontend. Trigger when creating or updating contracts in web/contract, wiring router composition, integrating TanStack Query with typed contracts, migrating legacy service calls to oRPC, or deciding whether to call queryOptions directly vs extracting a helper or use-* hook in web/service.
Set up and manage the Sentry development environment using devenv. Handles fresh setup, updating existing environments, starting dev services, and troubleshooting. Use when asked to set up sentry, setup dev environment, get sentry running, start dev server, devenv setup, devservices not working, sentry wont start, or any development environment issue.
Sentry JavaScript frontend bug pattern review based on real production errors. Use when reviewing React/TypeScript frontend code for common bug patterns. Trigger keywords: javascript bug review, frontend errors, react error patterns, sentry frontend bugs.
Work on the Astro website in `www/` for pdit.dev. Use when editing site content, styles, layouts, or components; adding pages or news posts; or running Astro dev/build commands for the website.
If This Page Is Close, Keep Narrowing With Adjacent Authority Pages
Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.
Use These Additional Paths If You Need One More Step To Narrow The Decision
These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.
