[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VKB82MJMPTB6ZMCHMGKTQ":3,"skill-same:01M77VKB82MJMPTB6ZMCHMGKTQ":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77VKB82MJMPTB6ZMCHMGKTQ","python-pypi-package-builder",null,"End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI. Covers all four build backends (setuptools+setuptools_scm, hatchling, flit, poetry), PEP 440 versioning, semantic versioning, dynamic git-tag versioning, OOP\u002FSOLID design, type hints (PEP 484\u002F526\u002F544\u002F561), Trusted Publishing (OIDC), and the full PyPA packaging flow. Use for: creating Python packages, pip-installable SDKs, CLI tools, framework plugins, pyproject.toml setup, py.typed, setuptools_scm, semver, mypy, pre-commit, GitHub Actions CI\u002FCD, or PyPI publishing.","Reihantt6\u002Fsns-myagent","Reihantt6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219822095?v=4","01M77KK94PV8B7C2D9XWXNS8DJ","Mohamad Reihan tegar prasetya","01M77KK958QFMTHYXGXFV7KZ79",2,"MIT","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI. Covers all four build backends (setuptools+setuptools_scm, hatchling, flit, poetry), PEP 440 versioning, semantic versioning, dynamic git-tag versioning, OOP\u002FSOLID design, type hints (PEP 484\u002F526\u002F544\u002F561), Trusted Publishing (OIDC), and the full PyPA packaging flow. Use for: creating Python packages, pip-installable SDKs, CLI tools, framework plugins, pyproject.toml setup, py.typed, setuptools_scm, semver, mypy, pre-commit, GitHub Actions CI\u002FCD, or PyPI publishing.\"\n---\n# Python PyPI Package Builder Skill\n\nA complete, battle-tested guide for building, testing, linting, versioning, typing, and\npublishing a production-grade Python library to PyPI — from first commit to community-ready\nrelease.\n\n> **AI Agent Instruction:** Read this entire file before writing a single line of code or\n> creating any file. Every decision — layout, backend, versioning strategy, patterns, CI —\n> has a decision rule here. Follow the decision trees in order. This skill applies to any\n> Python package type (utility, SDK, CLI, plugin, data library). Do not skip sections.\n\n---\n\n## Quick Navigation\n\n| Section in this file | What it covers |\n|---|---|\n| [1. Skill Trigger](#1-skill-trigger) | When to load this skill |\n| [2. Package Type Decision](#2-package-type-decision) | Identify what you are building |\n| [3. Folder Structure Decision](#3-folder-structure-decision) | src\u002F vs flat vs monorepo |\n| [4. Build Backend Decision](#4-build-backend-decision) | setuptools \u002F hatchling \u002F flit \u002F poetry |\n| [5. PyPA Packaging Flow](#5-pypa-packaging-flow) | The canonical publish pipeline |\n| [6. Project Structure Templates](#6-project-structure-templates) | Full layouts for every option |\n| [7. Versioning Strategy](#7-versioning-strategy) | PEP 440, semver, dynamic vs static |\n\n| Reference file | What it covers |\n|---|---|\n| `references\u002Fpyproject-toml.md` | All four backend templates, `setuptools_scm`, `py.typed`, tool configs |\n| `references\u002Flibrary-patterns.md` | OOP\u002FSOLID, type hints, core class design, factory, protocols, CLI |\n| `references\u002Ftesting-quality.md` | `conftest.py`, unit\u002Fbackend\u002Fasync tests, ruff\u002Fmypy\u002Fpre-commit |\n| `references\u002Fci-publishing.md` | `ci.yml`, `publish.yml`, Trusted Publishing, TestPyPI, CHANGELOG, release checklist |\n| `references\u002Fcommunity-docs.md` | README, docstrings, CONTRIBUTING, SECURITY, anti-patterns, master checklist |\n| `references\u002Farchitecture-patterns.md` | Backend system (plugin\u002Fstrategy), config layer, transport layer, CLI, backend injection |\n| `references\u002Fversioning-strategy.md` | PEP 440, SemVer, pre-release, setuptools_scm deep-dive, flit static, decision engine |\n| `references\u002Frelease-governance.md` | Branch strategy, branch protection, OIDC, tag author validation, prevent invalid tags |\n| `references\u002Ftooling-ruff.md` | Ruff-only setup (replaces black\u002Fisort), mypy config, pre-commit, asyncio_mode=auto |\n\n**Scaffold script:** run `python skills\u002Fpython-pypi-package-builder\u002Fscripts\u002Fscaffold.py --name your-package-name`\nto generate the entire directory layout, stub files, and `pyproject.toml` in one command.\n\n---\n\n## 1. Skill Trigger\n\nLoad this skill whenever the user wants to:\n\n- Create, scaffold, or publish a Python package or library to PyPI\n- Build a pip-installable SDK, utility, CLI tool, or framework extension\n- Set up `pyproject.toml`, linting, mypy, pre-commit, or GitHub Actions for a Python project\n- Understand versioning (`setuptools_scm`, PEP 440, semver, static versioning)\n- Understand PyPA specs: `py.typed`, `MANIFEST.in`, `RECORD`, classifiers\n- Publish to PyPI using Trusted Publishing (OIDC) or API tokens\n- Refactor an existing package to follow modern Python packaging standards\n- Add type hints, protocols, ABCs, or dataclasses to a Python library\n- Apply OOP\u002FSOLID design patterns to a Python package\n- Choose between build backends (setuptools, hatchling, flit, poetry)\n\n**Also trigger for phrases like:** \"build a Python SDK\", \"publish my library\", \"set up PyPI CI\",\n\"create a pip package\", \"how do I publish to PyPI\", \"pyproject.toml help\", \"PEP 561 typed\",\n\"setuptools_scm version\", \"semver Python\", \"PEP 440\", \"git tag release\", \"Trusted Publishing\".\n\n---\n\n## 2. Package Type Decision\n\nIdentify what the user is building **before** writing any code. Each type has distinct patterns.\n\n### Decision Table\n\n| Type | Core Pattern | Entry Point | Key Deps | Example Packages |\n|---|---|---|---|---|\n| **Utility library** | Module of pure functions + helpers | Import API only | Minimal | `arrow`, `humanize`, `boltons`, `more-itertools` |\n| **API client \u002F SDK** | Class with methods, auth, retry logic | Import API only | `httpx` or `requests` | `boto3`, `stripe-python`, `openai` |\n| **CLI tool** | Command functions + argument parser | `[project.scripts]` or `[project.entry-points]` | `click` or `typer` | `black`, `ruff`, `httpie`, `rich` |\n| **Framework plugin** | Plugin class, hook registration | `[project.entry-points.\"framework.plugin\"]` | Framework dep | `pytest-*`, `django-*`, `flask-*` |\n| **Data processing library** | Classes + functional pipeline | Import API only | Optional: `numpy`, `pandas` | `pydantic`, `marshmallow`, `cerberus` |\n| **Mixed \u002F generic** | Combination of above | Varies | Varies | Many real-world packages |\n\n**Decision Rule:** Ask the user if unclear. A package can combine types (e.g., SDK with a CLI\nentry point) — use the primary type for structural decisions and add secondary type patterns on top.\n\nFor implementation patterns of each type, see `references\u002Flibrary-patterns.md`.\n\n### Package Naming Rules\n\n- PyPI name: all lowercase, hyphens — `my-python-library`\n- Python import name: underscores — `my_python_library`\n- Check availability: https:\u002F\u002Fpypi.org\u002Fsearch\u002F before starting\n- Avoid shadowing popular packages (verify `pip install \u003Cname>` fails first)\n\n---\n\n## 3. Folder Structure Decision\n\n### Decision Tree\n\n```\nDoes the package have 5+ internal modules OR multiple contributors OR complex sub-packages?\n├── YES → Use src\u002F layout\n│         Reason: prevents accidental import of uninstalled code during development;\n│         separates source from project root files; PyPA-recommended for large projects.\n│\n├── NO → Is it a single-module, focused package (e.g., one file + helpers)?\n│         ├── YES → Use flat layout\n│         └── NO (medium complexity) → Use flat layout, migrate to src\u002F if it grows\n│\n└── Is it multiple related packages under one namespace (e.g., myorg.http, myorg.db)?\n          └── YES → Use namespace\u002Fmonorepo layout\n```\n\n### Quick Rule Summary\n\n| Situation | Use |\n|---|---|\n| New project, unknown future size | `src\u002F` layout (safest default) |\n| Single-purpose, 1–4 modules | Flat layout |\n| Large library, many contributors | `src\u002F` layout |\n| Multiple packages in one repo | Namespace \u002F monorepo |\n| Migrating old flat project | Keep flat; migrate to `src\u002F` at next major version |\n\n---\n\n## 4. Build Backend Decision\n\n### Decision Tree\n\n```\nDoes the user need version derived automatically from git tags?\n├── YES → Use setuptools + setuptools_scm\n│         (git tag v1.0.0 → that IS your release workflow)\n│\n└── NO → Does the user want an all-in-one tool (deps + build + publish)?\n          ├── YES → Use poetry (v2+ supports standard [project] table)\n          │\n          └── NO → Is the package pure Python with no C extensions?\n                    ├── YES, minimal config preferred → Use flit\n                    │   (zero config, auto-discovers version from __version__)\n                    │\n                    └── YES, modern & fast preferred → Use hatchling\n                        (zero-config, plugin system, no setup.py needed)\n\nDoes the package have C\u002FCython\u002FFortran extensions?\n└── YES → MUST use setuptools (only backend with full native extension support)\n```\n\n### Backend Comparison\n\n| Backend | Version source | Config | C extensions | Best for |\n|---|---|---|---|---|\n| `setuptools` + `setuptools_scm` | git tags (automatic) | `pyproject.toml` + optional `setup.py` shim | Yes | Projects with git-tag releases; any complexity |\n| `hatchling` | manual or plugin | `pyproject.toml` only | No | New pure-Python projects; fast, modern |\n| `flit` | `__version__` in `__init__.py` | `pyproject.toml` only | No | Very simple, single-module packages |\n| `poetry` | `pyproject.toml` field | `pyproject.toml` only | No | Teams wanting integrated dep management |\n\nFor all four complete `pyproject.toml` templates, see `references\u002Fpyproject-toml.md`.\n\n---\n\n## 5. PyPA Packaging Flow\n\nThis is the canonical end-to-end flow from source code to user install.\n**Every step must be understood before publishing.**\n\n```\n1. SOURCE TREE\n   Your code in version control (git)\n   └── pyproject.toml describes metadata + build system\n\n2. BUILD\n   python -m build\n   └── Produces two artifacts in dist\u002F:\n       ├── *.tar.gz   → source distribution (sdist)\n       └── *.whl      → built distribution (wheel) — preferred by pip\n\n3. VALIDATE\n   twine check dist\u002F*\n   └── Checks metadata, README rendering, and PyPI compatibility\n\n4. TEST PUBLISH (first release only)\n   twine upload --repository testpypi dist\u002F*\n   └── Verify: pip install --index-url https:\u002F\u002Ftest.pypi.org\u002Fsimple\u002F your-package\n\n5. PUBLISH\n   twine upload dist\u002F*          ← manual fallback\n   OR GitHub Actions publish.yml  ← recommended (Trusted Publishing \u002F OIDC)\n\n6. USER INSTALL\n   pip install your-package\n   pip install \"your-package[extra]\"\n```\n\n### Key PyPA Concepts\n\n| Concept | What it means |\n|---|---|\n| **sdist** | Source distribution — your source + metadata; used when no wheel is available |\n| **wheel (.whl)** | Pre-built binary — pip extracts directly into site-packages; no build step |\n| **PEP 517\u002F518** | Standard build system interface via `pyproject.toml [build-system]` table |\n| **PEP 621** | Standard `[project]` table in `pyproject.toml`; all modern backends support it |\n| **PEP 639** | `license` key as SPDX string (e.g., `\"MIT\"`, `\"Apache-2.0\"`) — not `{text = \"MIT\"}` |\n| **PEP 561** | `py.typed` empty marker file — tells mypy\u002FIDEs this package ships type information |\n\nFor complete CI workflow and publishing setup, see `references\u002Fci-publishing.md`.\n\n---\n\n## 6. Project Structure Templates\n\n### A. src\u002F Layout (Recommended default for new projects)\n\n```\nyour-package\u002F\n├── src\u002F\n│   └── your_package\u002F\n│       ├── __init__.py           # Public API: __all__, __version__\n│       ├── py.typed              # PEP 561 marker — EMPTY FILE\n│       ├── core.py               # Primary implementation\n│       ├── client.py             # (API client type) or remove\n│       ├── cli.py                # (CLI type) click\u002Ftyper commands, or remove\n│       ├── config.py             # Settings \u002F configuration dataclass\n│       ├── exceptions.py         # Custom exception hierarchy\n│       ├── models.py             # Data classes, Pydantic models, TypedDicts\n│       ├── utils.py              # Internal helpers (prefix _utils if private)\n│       ├── types.py              # Shared type aliases and TypeVars\n│       └── backends\u002F             # (Plugin pattern) — remove if not needed\n│           ├── __init__.py       # Protocol \u002F ABC interface definition\n│           ├── memory.py         # Default zero-dep implementation\n│           └── redis.py          # Optional heavy implementation\n├── tests\u002F\n│   ├── __init__.py\n│   ├── conftest.py               # Shared fixtures\n│   ├── unit\u002F\n│   │   ├── __init__.py\n│   │   ├── test_core.py\n│   │   ├── test_config.py\n│   │   └── test_models.py\n│   ├── integration\u002F\n│   │   ├── __init__.py\n│   │   └── test_backends.py\n│   └── e2e\u002F                      # Optional: end-to-end tests\n│       └── __init__.py\n├── docs\u002F                         # Optional: mkdocs or sphinx\n├── scripts\u002F\n│   └── scaffold.py\n├── .github\u002F\n│   ├── workflows\u002F\n│   │   ├── ci.yml\n│   │   └── publish.yml\n│   └── ISSUE_TEMPLATE\u002F\n│       ├── bug_report.md\n│       └── feature_request.md\n├── .pre-commit-config.yaml\n├── pyproject.toml\n├── CHANGELOG.md\n├── CONTRIBUTING.md\n├── SECURITY.md\n├── LICENSE\n├── README.md\n└── .gitignore\n```\n\n### B. Flat Layout (Small \u002F focused packages)\n\n```\nyour-package\u002F\n├── your_package\u002F         # ← at root, not inside src\u002F\n│   ├── __init__.py\n│   ├── py.typed\n│   └── ... (same internal structure)\n├── tests\u002F\n└── ... (same top-level files)\n```\n\n### C. Namespace \u002F Monorepo Layout (Multiple related packages)\n\n```\nyour-org\u002F\n├── packages\u002F\n│   ├── your-org-core\u002F\n│   │   ├── src\u002Fyour_org\u002Fcore\u002F\n│   │   └── pyproject.toml\n│   ├── your-org-http\u002F\n│   │   ├── src\u002Fyour_org\u002Fhttp\u002F\n│   │   └── pyproject.toml\n│   └── your-org-cli\u002F\n│       ├── src\u002Fyour_org\u002Fcli\u002F\n│       └── pyproject.toml\n├── .github\u002Fworkflows\u002F\n└── README.md\n```\n\nEach sub-package has its own `pyproject.toml`. They share the `your_org` namespace via PEP 420\nimplicit namespace packages (no `__init__.py` in the namespace root).\n\n### Internal Module Guidelines\n\n| File | Purpose | When to include |\n|---|---|---|\n| `__init__.py` | Public API surface; re-exports; `__version__` | Always |\n| `py.typed` | PEP 561 typed-package marker (empty) | Always |\n| `core.py` | Primary class \u002F main logic | Always |\n| `config.py` | Settings dataclass or Pydantic model | When configurable |\n| `exceptions.py` | Exception hierarchy (`YourBaseError` → specifics) | Always |\n| `models.py` | Data models \u002F DTOs \u002F TypedDicts | When data-heavy |\n| `utils.py` | Internal helpers (not part of public API) | As needed |\n| `types.py` | Shared `TypeVar`, `TypeAlias`, `Protocol` definitions | When complex typing |\n| `cli.py` | CLI entry points (click\u002Ftyper) | CLI type only |\n| `backends\u002F` | Plugin\u002Fstrategy pattern | When swappable implementations |\n| `_compat.py` | Python version compatibility shims | When 3.9–3.13 compat needed |\n\n---\n\n## 7. Versioning Strategy\n\n### PEP 440 — The Standard\n\n```\nCanonical form:  N[.N]+[{a|b|rc}N][.postN][.devN]\n\nExamples:\n  1.0.0          Stable release\n  1.0.0a1        Alpha (pre-release)\n  1.0.0b2        Beta\n  1.0.0rc1       Release candidate\n  1.0.0.post1    Post-release (e.g., packaging fix only)\n  1.0.0.dev1     Development snapshot (not for PyPI)\n```\n\n### Semantic Versioning (recommended)\n\n```\nMAJOR.MINOR.PATCH\n\nMAJOR: Breaking API change (remove\u002Frename public function\u002Fclass\u002Farg)\nMINOR: New feature, fully backward-compatible\nPATCH: Bug fix, no API change\n```\n\n### Dynamic versioning with setuptools_scm (recommended for git-tag workflows)\n\n```bash\n# How it works:\ngit tag v1.0.0          →  installed version = 1.0.0\ngit tag v1.1.0          →  installed version = 1.1.0\n(commits after tag)     →  version = 1.1.0.post1  (suffix stripped for PyPI)\n\n# In code — NEVER hardcode when using setuptools_scm:\nfrom importlib.metadata import version, PackageNotFoundError\ntry:\n    __version__ = version(\"your-package\")\nexcept PackageNotFoundError:\n    __version__ = \"0.0.0-dev\"    # Fallback for uninstalled dev checkouts\n```\n\nRequired `pyproject.toml` config:\n```toml\n[tool.setuptools_scm]\nversion_scheme = \"post-release\"\nlocal_scheme   = \"no-local-version\"   # Prevents +g\u003Chash> from breaking PyPI uploads\n```\n\n**Critical:** always set `fetch-depth: 0` in every CI checkout step. Without full git history,\n`setuptools_scm` cannot find tags and the build version silently falls back to `0.0.0+dev`.\n\n### Static versioning (flit, hatchling manual, poetry)\n\n```python\n# your_package\u002F__init__.py\n__version__ = \"1.0.0\"    # Update this before every release\n```\n\n### Version specifier best practices for dependencies\n\n```toml\n# In [project] dependencies:\n\"httpx>=0.24\"            # Minimum version — PREFERRED for libraries\n\"httpx>=0.24,\u003C1.0\"       # Upper bound only when a known breaking change exists\n\"httpx==0.27.0\"          # Pin exactly ONLY in applications, NOT libraries\n\n# NEVER do this in a library — it breaks dependency resolution for users:\n# \"httpx~=0.24.0\"        # Too tight\n# \"httpx==0.27.*\"        # Fragile\n```\n\n### Version bump → release flow\n\n```bash\n# 1. Update CHANGELOG.md — move [Unreleased] entries to [x.y.z] - YYYY-MM-DD\n# 2. Commit the changelog\ngit add CHANGELOG.md\ngit commit -m \"chore: prepare release vX.Y.Z\"\n# 3. Tag and push — this triggers publish.yml automatically\ngit tag vX.Y.Z\ngit push origin main --tags\n# 4. Monitor GitHub Actions → verify on https:\u002F\u002Fpypi.org\u002Fproject\u002Fyour-package\u002F\n```\n\nFor complete pyproject.toml templates for all four backends, see `references\u002Fpyproject-toml.md`.\n\n---\n\n## Where to Go Next\n\nAfter understanding decisions and structure:\n\n1. **Set up `pyproject.toml`** → `references\u002Fpyproject-toml.md`\n   All four backend templates (setuptools+scm, hatchling, flit, poetry), full tool configs,\n   `py.typed` setup, versioning config.\n\n2. **Write your library code** → `references\u002Flibrary-patterns.md`\n   OOP\u002FSOLID principles, type hints (PEP 484\u002F526\u002F544\u002F561), core class design, factory functions,\n   `__init__.py`, plugin\u002Fbackend pattern, CLI entry point.\n\n3. **Add tests and code quality** → `references\u002Ftesting-quality.md`\n   `conftest.py`, unit\u002Fbackend\u002Fasync tests, parametrize, ruff\u002Fmypy\u002Fpre-commit setup.\n\n4. **Set up CI\u002FCD and publish** → `references\u002Fci-publishing.md`\n   `ci.yml`, `publish.yml` with Trusted Publishing (OIDC, no API tokens), CHANGELOG format,\n   release checklist.\n\n5. **Polish for community\u002FOSS** → `references\u002Fcommunity-docs.md`\n   README sections, docstring format, CONTRIBUTING, SECURITY, issue templates, anti-patterns\n   table, and master release checklist.\n\n6. **Design backends, config, transport, CLI** → `references\u002Farchitecture-patterns.md`\n   Backend system (plugin\u002Fstrategy pattern), Settings dataclass, HTTP transport layer,\n   CLI with click\u002Ftyper, backend injection rules.\n\n7. **Choose and implement a versioning strategy** → `references\u002Fversioning-strategy.md`\n   PEP 440 canonical forms, SemVer rules, pre-release identifiers, setuptools_scm deep-dive,\n   flit static versioning, decision engine (DEFAULT\u002FBEGINNER\u002FMINIMAL).\n\n8. **Govern releases and secure the publish pipeline** → `references\u002Frelease-governance.md`\n   Branch strategy, branch protection rules, OIDC Trusted Publishing setup, tag author\n   validation in CI, tag format enforcement, full governed `publish.yml`.\n\n9. **Simplify tooling with Ruff** → `references\u002Ftooling-ruff.md`\n   Ruff-only setup replacing black\u002Fisort\u002Fflake8, mypy config, pre-commit hooks,\n   asyncio_mode=auto (remove @pytest.mark.asyncio), migration guide.\n","# Python PyPI Package Builder Skill\n\nA complete, battle-tested guide for building, testing, linting, versioning, typing, and\npublishing a production-grade Python library to PyPI — from first commit to community-ready\nrelease.\n\n> **AI Agent Instruction:** Read this entire file before writing a single line of code or\n> creating any file. Every decision — layout, backend, versioning strategy, patterns, CI —\n> has a decision rule here. Follow the decision trees in order. This skill applies to any\n> Python package type (utility, SDK, CLI, plugin, data library). Do not skip sections.\n\n---\n\n## Quick Navigation\n\n| Section in this file | What it covers |\n|---|---|\n| [1. Skill Trigger](#1-skill-trigger) | When to load this skill |\n| [2. Package Type Decision](#2-package-type-decision) | Identify what you are building |\n| [3. Folder Structure Decision](#3-folder-structure-decision) | src\u002F vs flat vs monorepo |\n| [4. Build Backend Decision](#4-build-backend-decision) | setuptools \u002F hatchling \u002F flit \u002F poetry |\n| [5. PyPA Packaging Flow](#5-pypa-packaging-flow) | The canonical publish pipeline |\n| [6. Project Structure Templates](#6-project-structure-templates) | Full layouts for every option |\n| [7. Versioning Strategy](#7-versioning-strategy) | PEP 440, semver, dynamic vs static |\n\n| Reference file | What it covers |\n|---|---|\n| `references\u002Fpyproject-toml.md` | All four backend templates, `setuptools_scm`, `py.typed`, tool configs |\n| `references\u002Flibrary-patterns.md` | OOP\u002FSOLID, type hints, core class design, factory, protocols, CLI |\n| `references\u002Ftesting-quality.md` | `conftest.py`, unit\u002Fbackend\u002Fasync tests, ruff\u002Fmypy\u002Fpre-commit |\n| `references\u002Fci-publishing.md` | `ci.yml`, `publish.yml`, Trusted Publishing, TestPyPI, CHANGELOG, release checklist |\n| `references\u002Fcommunity-docs.md` | README, docstrings, CONTRIBUTING, SECURITY, anti-patterns, master checklist |\n| `references\u002Farchitecture-patterns.md` | Backend system (plugin\u002Fstrategy), config layer, transport layer, CLI, backend injection |\n| `references\u002Fversioning-strategy.md` | PEP 440, SemVer, pre-release, setuptools_scm deep-dive, flit static, decision engine |\n| `references\u002Frelease-governance.md` | Branch strategy, branch protection, OIDC, tag author validation, prevent invalid tags |\n| `references\u002Ftooling-ruff.md` | Ruff-only setup (replaces black\u002Fisort), mypy config, pre-commit, asyncio_mode=auto |\n\n**Scaffold script:** run `python skills\u002Fpython-pypi-package-builder\u002Fscripts\u002Fscaffold.py --name your-package-name`\nto generate the entire directory layout, stub files, and `pyproject.toml` in one command.\n\n---\n\n## 1. Skill Trigger\n\nLoad this skill whenever the user wants to:\n\n- Create, scaffold, or publish a Python package or library to PyPI\n- Build a pip-installable SDK, utility, CLI tool, or framework extension\n- Set up `pyproject.toml`, linting, mypy, pre-commit, or GitHub Actions for a Python project\n- Understand versioning (`setuptools_scm`, PEP 440, semver, static versioning)\n- Understand PyPA specs: `py.typed`, `MANIFEST.in`, `RECORD`, classifiers\n- Publish to PyPI using Trusted Publishing (OIDC) or API tokens\n- Refactor an existing package to follow modern Python packaging standards\n- Add type hints, protocols, ABCs, or dataclasses to a Python library\n- Apply OOP\u002FSOLID design patterns to a Python package\n- Choose between build backends (setuptools, hatchling, flit, poetry)\n\n**Also trigger for phrases like:** \"build a Python SDK\", \"publish my library\", \"set up PyPI CI\",\n\"create a pip package\", \"how do I publish to PyPI\", \"pyproject.toml help\", \"PEP 561 typed\",\n\"setuptools_scm version\", \"semver Python\", \"PEP 440\", \"git tag release\", \"Trusted Publishing\".\n\n---\n\n## 2. Package Type Decision\n\nIdentify what the user is building **before** writing any code. Each type has distinct patterns.\n\n### Decision Table\n\n| Type | Core Pattern | Entry Point | Key Deps | Example Packages |\n|---|---|---|---|---|\n| **Utility library** | Module of pure functions + helpers | Import API only | Minimal | `arrow`, `humanize`, `boltons`, `more-itertools` |\n| **API client \u002F SDK** | Class with methods, auth, retry logic | Import API only | `httpx` or `requests` | `boto3`, `stripe-python`, `openai` |\n| **CLI tool** | Command functions + argument parser | `[project.scripts]` or `[project.entry-points]` | `click` or `typer` | `black`, `ruff`, `httpie`, `rich` |\n| **Framework plugin** | Plugin class, hook registration | `[project.entry-points.\"framework.plugin\"]` | Framework dep | `pytest-*`, `django-*`, `flask-*` |\n| **Data processing library** | Classes + functional pipeline | Import API only | Optional: `numpy`, `pandas` | `pydantic`, `marshmallow`, `cerberus` |\n| **Mixed \u002F generic** | Combination of above | Varies | Varies | Many real-world packages |\n\n**Decision Rule:** Ask the user if unclear. A package can combine types (e.g., SDK with a CLI\nentry point) — use the primary type for structural decisions and add secondary type patterns on top.\n\nFor implementation patterns of each type, see `references\u002Flibrary-patterns.md`.\n\n### Package Naming Rules\n\n- PyPI name: all lowercase, hyphens — `my-python-library`\n- Python import name: underscores — `my_python_library`\n- Check availability: https:\u002F\u002Fpypi.org\u002Fsearch\u002F before starting\n- Avoid shadowing popular packages (verify `pip install \u003Cname>` fails first)\n\n---\n\n## 3. Folder Structure Decision\n\n### Decision Tree\n\n```\nDoes the package have 5+ internal modules OR multiple contributors OR complex sub-packages?\n├── YES → Use src\u002F layout\n│         Reason: prevents accidental import of uninstalled code during development;\n│         separates source from project root files; PyPA-recommended for large projects.\n│\n├── NO → Is it a single-module, focused package (e.g., one file + helpers)?\n│         ├── YES → Use flat layout\n│         └── NO (medium complexity) → Use flat layout, migrate to src\u002F if it grows\n│\n└── Is it multiple related packages under one namespace (e.g., myorg.http, myorg.db)?\n          └── YES → Use namespace\u002Fmonorepo layout\n```\n\n### Quick Rule Summary\n\n| Situation | Use |\n|---|---|\n| New project, unknown future size | `src\u002F` layout (safest default) |\n| Single-purpose, 1–4 modules | Flat layout |\n| Large library, many contributors | `src\u002F` layout |\n| Multiple packages in one repo | Namespace \u002F monorepo |\n| Migrating old flat project | Keep flat; migrate to `src\u002F` at next major version |\n\n---\n\n## 4. Build Backend Decision\n\n### Decision Tree\n\n```\nDoes the user need version derived automatically from git tags?\n├── YES → Use setuptools + setuptools_scm\n│         (git tag v1.0.0 → that IS your release workflow)\n│\n└── NO → Does the user want an all-in-one tool (deps + build + publish)?\n          ├── YES → Use poetry (v2+ supports standard [project] table)\n          │\n          └── NO → Is the package pure Python with no C extensions?\n                    ├── YES, minimal config preferred → Use flit\n                    │   (zero config, auto-discovers version from __version__)\n                    │\n                    └── YES, modern & fast preferred → Use hatchling\n                        (zero-config, plugin system, no setup.py needed)\n\nDoes the package have C\u002FCython\u002FFortran extensions?\n└── YES → MUST use setuptools (only backend with full native extension support)\n```\n\n### Backend Comparison\n\n| Backend | Version source | Config | C extensions | Best for |\n|---|---|---|---|---|\n| `setuptools` + `setuptools_scm` | git tags (automatic) | `pyproject.toml` + optional `setup.py` shim | Yes | Projects with git-tag releases; any complexity |\n| `hatchling` | manual or plugin | `pyproject.toml` only | No | New pure-Python projects; fast, modern |\n| `flit` | `__version__` in `__init__.py` | `pyproject.toml` only | No | Very simple, single-module packages |\n| `poetry` | `pyproject.toml` field | `pyproject.toml` only | No | Teams wanting integrated dep management |\n\nFor all four complete `pyproject.toml` templates, see `references\u002Fpyproject-toml.md`.\n\n---\n\n## 5. PyPA Packaging Flow\n\nThis is the canonical end-to-end flow from source code to user install.\n**Every step must be understood before publishing.**\n\n```\n1. SOURCE TREE\n   Your code in version control (git)\n   └── pyproject.toml describes metadata + build system\n\n2. BUILD\n   python -m build\n   └── Produces two artifacts in dist\u002F:\n       ├── *.tar.gz   → source distribution (sdist)\n       └── *.whl      → built distribution (wheel) — preferred by pip\n\n3. VALIDATE\n   twine check dist\u002F*\n   └── Checks metadata, README rendering, and PyPI compatibility\n\n4. TEST PUBLISH (first release only)\n   twine upload --repository testpypi dist\u002F*\n   └── Verify: pip install --index-url https:\u002F\u002Ftest.pypi.org\u002Fsimple\u002F your-package\n\n5. PUBLISH\n   twine upload dist\u002F*          ← manual fallback\n   OR GitHub Actions publish.yml  ← recommended (Trusted Publishing \u002F OIDC)\n\n6. USER INSTALL\n   pip install your-package\n   pip install \"your-package[extra]\"\n```\n\n### Key PyPA Concepts\n\n| Concept | What it means |\n|---|---|\n| **sdist** | Source distribution — your source + metadata; used when no wheel is available |\n| **wheel (.whl)** | Pre-built binary — pip extracts directly into site-packages; no build step |\n| **PEP 517\u002F518** | Standard build system interface via `pyproject.toml [build-system]` table |\n| **PEP 621** | Standard `[project]` table in `pyproject.toml`; all modern backends support it |\n| **PEP 639** | `license` key as SPDX string (e.g., `\"MIT\"`, `\"Apache-2.0\"`) — not `{text = \"MIT\"}` |\n| **PEP 561** | `py.typed` empty marker file — tells mypy\u002FIDEs this package ships type information |\n\nFor complete CI workflow and publishing setup, see `references\u002Fci-publishing.md`.\n\n---\n\n## 6. Project Structure Templates\n\n### A. src\u002F Layout (Recommended default for new projects)\n\n```\nyour-package\u002F\n├── src\u002F\n│   └── your_package\u002F\n│       ├── __init__.py           # Public API: __all__, __version__\n│       ├── py.typed              # PEP 561 marker — EMPTY FILE\n│       ├── core.py               # Primary implementation\n│       ├── client.py             # (API client type) or remove\n│       ├── cli.py                # (CLI type) click\u002Ftyper commands, or remove\n│       ├── config.py             # Settings \u002F configuration dataclass\n│       ├── exceptions.py         # Custom exception hierarchy\n│       ├── models.py             # Data classes, Pydantic models, TypedDicts\n│       ├── utils.py              # Internal helpers (prefix _utils if private)\n│       ├── types.py              # Shared type aliases and TypeVars\n│       └── backends\u002F             # (Plugin pattern) — remove if not needed\n│           ├── __init__.py       # Protocol \u002F ABC interface definition\n│           ├── memory.py         # Default zero-dep implementation\n│           └── redis.py          # Optional heavy implementation\n├── tests\u002F\n│   ├── __init__.py\n│   ├── conftest.py               # Shared fixtures\n│   ├── unit\u002F\n│   │   ├── __init__.py\n│   │   ├── test_core.py\n│   │   ├── test_config.py\n│   │   └── test_models.py\n│   ├── integration\u002F\n│   │   ├── __init__.py\n│   │   └── test_backends.py\n│   └── e2e\u002F                      # Optional: end-to-end tests\n│       └── __init__.py\n├── docs\u002F                         # Optional: mkdocs or sphinx\n├── scripts\u002F\n│   └── scaffold.py\n├── .github\u002F\n│   ├── workflows\u002F\n│   │   ├── ci.yml\n│   │   └── publish.yml\n│   └── ISSUE_TEMPLATE\u002F\n│       ├── bug_report.md\n│       └── feature_request.md\n├── .pre-commit-config.yaml\n├── pyproject.toml\n├── CHANGELOG.md\n├── CONTRIBUTING.md\n├── SECURITY.md\n├── LICENSE\n├── README.md\n└── .gitignore\n```\n\n### B. Flat Layout (Small \u002F focused packages)\n\n```\nyour-package\u002F\n├── your_package\u002F         # ← at root, not inside src\u002F\n│   ├── __init__.py\n│   ├── py.typed\n│   └── ... (same internal structure)\n├── tests\u002F\n└── ... (same top-level files)\n```\n\n### C. Namespace \u002F Monorepo Layout (Multiple related packages)\n\n```\nyour-org\u002F\n├── packages\u002F\n│   ├── your-org-core\u002F\n│   │   ├── src\u002Fyour_org\u002Fcore\u002F\n│   │   └── pyproject.toml\n│   ├── your-org-http\u002F\n│   │   ├── src\u002Fyour_org\u002Fhttp\u002F\n│   │   └── pyproject.toml\n│   └── your-org-cli\u002F\n│       ├── src\u002Fyour_org\u002Fcli\u002F\n│       └── pyproject.toml\n├── .github\u002Fworkflows\u002F\n└── README.md\n```\n\nEach sub-package has its own `pyproject.toml`. They share the `your_org` namespace via PEP 420\nimplicit namespace packages (no `__init__.py` in the namespace root).\n\n### Internal Module Guidelines\n\n| File | Purpose | When to include |\n|---|---|---|\n| `__init__.py` | Public API surface; re-exports; `__version__` | Always |\n| `py.typed` | PEP 561 typed-package marker (empty) | Always |\n| `core.py` | Primary class \u002F main logic | Always |\n| `config.py` | Settings dataclass or Pydantic model | When configurable |\n| `exceptions.py` | Exception hierarchy (`YourBaseError` → specifics) | Always |\n| `models.py` | Data models \u002F DTOs \u002F TypedDicts | When data-heavy |\n| `utils.py` | Internal helpers (not part of public API) | As needed |\n| `types.py` | Shared `TypeVar`, `TypeAlias`, `Protocol` definitions | When complex typing |\n| `cli.py` | CLI entry points (click\u002Ftyper) | CLI type only |\n| `backends\u002F` | Plugin\u002Fstrategy pattern | When swappable implementations |\n| `_compat.py` | Python version compatibility shims | When 3.9–3.13 compat needed |\n\n---\n\n## 7. Versioning Strategy\n\n### PEP 440 — The Standard\n\n```\nCanonical form:  N[.N]+[{a|b|rc}N][.postN][.devN]\n\nExamples:\n  1.0.0          Stable release\n  1.0.0a1        Alpha (pre-release)\n  1.0.0b2        Beta\n  1.0.0rc1       Release candidate\n  1.0.0.post1    Post-release (e.g., packaging fix only)\n  1.0.0.dev1     Development snapshot (not for PyPI)\n```\n\n### Semantic Versioning (recommended)\n\n```\nMAJOR.MINOR.PATCH\n\nMAJOR: Breaking API change (remove\u002Frename public function\u002Fclass\u002Farg)\nMINOR: New feature, fully backward-compatible\nPATCH: Bug fix, no API change\n```\n\n### Dynamic versioning with setuptools_scm (recommended for git-tag workflows)\n\n```bash\n# How it works:\ngit tag v1.0.0          →  installed version = 1.0.0\ngit tag v1.1.0          →  installed version = 1.1.0\n(commits after tag)     →  version = 1.1.0.post1  (suffix stripped for PyPI)\n\n# In code — NEVER hardcode when using setuptools_scm:\nfrom importlib.metadata import version, PackageNotFoundError\ntry:\n    __version__ = version(\"your-package\")\nexcept PackageNotFoundError:\n    __version__ = \"0.0.0-dev\"    # Fallback for uninstalled dev checkouts\n```\n\nRequired `pyproject.toml` config:\n```toml\n[tool.setuptools_scm]\nversion_scheme = \"post-release\"\nlocal_scheme   = \"no-local-version\"   # Prevents +g\u003Chash> from breaking PyPI uploads\n```\n\n**Critical:** always set `fetch-depth: 0` in every CI checkout step. Without full git history,\n`setuptools_scm` cannot find tags and the build version silently falls back to `0.0.0+dev`.\n\n### Static versioning (flit, hatchling manual, poetry)\n\n```python\n# your_package\u002F__init__.py\n__version__ = \"1.0.0\"    # Update this before every release\n```\n\n### Version specifier best practices for dependencies\n\n```toml\n# In [project] dependencies:\n\"httpx>=0.24\"            # Minimum version — PREFERRED for libraries\n\"httpx>=0.24,\u003C1.0\"       # Upper bound only when a known breaking change exists\n\"httpx==0.27.0\"          # Pin exactly ONLY in applications, NOT libraries\n\n# NEVER do this in a library — it breaks dependency resolution for users:\n# \"httpx~=0.24.0\"        # Too tight\n# \"httpx==0.27.*\"        # Fragile\n```\n\n### Version bump → release flow\n\n```bash\n# 1. Update CHANGELOG.md — move [Unreleased] entries to [x.y.z] - YYYY-MM-DD\n# 2. Commit the changelog\ngit add CHANGELOG.md\ngit commit -m \"chore: prepare release vX.Y.Z\"\n# 3. Tag and push — this triggers publish.yml automatically\ngit tag vX.Y.Z\ngit push origin main --tags\n# 4. Monitor GitHub Actions → verify on https:\u002F\u002Fpypi.org\u002Fproject\u002Fyour-package\u002F\n```\n\nFor complete pyproject.toml templates for all four backends, see `references\u002Fpyproject-toml.md`.\n\n---\n\n## Where to Go Next\n\nAfter understanding decisions and structure:\n\n1. **Set up `pyproject.toml`** → `references\u002Fpyproject-toml.md`\n   All four backend templates (setuptools+scm, hatchling, flit, poetry), full tool configs,\n   `py.typed` setup, versioning config.\n\n2. **Write your library code** → `references\u002Flibrary-patterns.md`\n   OOP\u002FSOLID principles, type hints (PEP 484\u002F526\u002F544\u002F561), core class design, factory functions,\n   `__init__.py`, plugin\u002Fbackend pattern, CLI entry point.\n\n3. **Add tests and code quality** → `references\u002Ftesting-quality.md`\n   `conftest.py`, unit\u002Fbackend\u002Fasync tests, parametrize, ruff\u002Fmypy\u002Fpre-commit setup.\n\n4. **Set up CI\u002FCD and publish** → `references\u002Fci-publishing.md`\n   `ci.yml`, `publish.yml` with Trusted Publishing (OIDC, no API tokens), CHANGELOG format,\n   release checklist.\n\n5. **Polish for community\u002FOSS** → `references\u002Fcommunity-docs.md`\n   README sections, docstring format, CONTRIBUTING, SECURITY, issue templates, anti-patterns\n   table, and master release checklist.\n\n6. **Design backends, config, transport, CLI** → `references\u002Farchitecture-patterns.md`\n   Backend system (plugin\u002Fstrategy pattern), Settings dataclass, HTTP transport layer,\n   CLI with click\u002Ftyper, backend injection rules.\n\n7. **Choose and implement a versioning strategy** → `references\u002Fversioning-strategy.md`\n   PEP 440 canonical forms, SemVer rules, pre-release identifiers, setuptools_scm deep-dive,\n   flit static versioning, decision engine (DEFAULT\u002FBEGINNER\u002FMINIMAL).\n\n8. **Govern releases and secure the publish pipeline** → `references\u002Frelease-governance.md`\n   Branch strategy, branch protection rules, OIDC Trusted Publishing setup, tag author\n   validation in CI, tag format enforcement, full governed `publish.yml`.\n\n9. **Simplify tooling with Ruff** → `references\u002Ftooling-ruff.md`\n   Ruff-only setup replacing black\u002Fisort\u002Fflake8, mypy config, pre-commit hooks,\n   asyncio_mode=auto (remove @pytest.mark.asyncio), migration guide.\n",{"description":7},"main","58843b159d7a4050d6b785a98b908cce505c0b92","agent\u002Fskills\u002Fpython-pypi-package-builder",0,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent","https:\u002F\u002Fgithub.com\u002FReihantt6","reihsns.web.id","2026-08-19 20:08:18",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Reihantt6\u002Fsns-myagent --skill python-pypi-package-builder",{"tool":38,"command":39},"bunx","bunx skills add Reihantt6\u002Fsns-myagent --skill python-pypi-package-builder",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Reihantt6\u002Fsns-myagent --skill python-pypi-package-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,84],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Farchitecture-patterns.md","REFERENCE","参考文档",16148,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002Freferences\u002Farchitecture-patterns.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fci-publishing.md",8050,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002Freferences\u002Fci-publishing.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fcommunity-docs.md",13263,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002Freferences\u002Fcommunity-docs.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Flibrary-patterns.md",18167,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002Freferences\u002Flibrary-patterns.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fpyproject-toml.md",13326,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002Freferences\u002Fpyproject-toml.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Frelease-governance.md",10680,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002Freferences\u002Frelease-governance.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Ftesting-quality.md",6565,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002Freferences\u002Ftesting-quality.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Ftooling-ruff.md",9371,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002Freferences\u002Ftooling-ruff.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fversioning-strategy.md",11193,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002Freferences\u002Fversioning-strategy.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fscaffold.py","SCRIPT","脚本",22563,"https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fpython-pypi-package-builder\u002Fscripts\u002Fscaffold.py",[91,98,105,112,119,126],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M77XDCYZ407XYMF2T4P6F7VT","youtube-transcript","Extract transcripts from YouTube videos. Use when the user asks for a transcript, subtitles, or captions of a YouTube video and provides a YouTube URL (youtube.com\u002Fwatch?v=, youtu.be\u002F, or similar). Supports output with or without timestamps.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-transcript\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M77XD7PBC98J6MXGJJ2TJ8DX","youtube-thumbnail-design","YouTube thumbnail design with specific dimensions, contrast rules, and mobile preview optimization. Covers safe zones, text placement, face expression psychology, and A\u002FB testing. Use for: YouTube thumbnails, video cover images, click-through optimization. Triggers: youtube thumbnail, thumbnail design, video thumbnail, click through rate, ctr optimization, youtube cover, video cover image, thumbnail maker, thumbnail tips, youtube design, video preview image","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-thumbnail-design\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M77XD2541C8HXJ6RHYZP4NGJ","youtube-short-maker","Make YouTube Shorts that hold attention with Pexo — vertical 9:16, fast-paced, hook in the first 3 seconds. Describe your topic and Pexo writes the script, generates the shots, picks the models, and assembles a finished Short with music and captions. Use for YouTube Shorts: \"youtube short\", \"make a youtube short\", \"shorts video\", \"short-form video\". NOT for long-form or landscape video.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fyoutube-short-maker\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M77XCXKVSYK7KTZ3PQBVVGFD","xcode-project-setup","Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fxcode-project-setup\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M77XCR1DV8ZQK2NHWKVY4EWX","x402","Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — \"just use it\" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or \"build it in\" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the user asks about x402, pay-per-use, USDC payments, or wants Browser Use Cloud without an API key. For the free-tier signup (reverse-CAPTCHA → API key), use `browser-use cloud signup` or the `cloud` skill instead.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx402\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M77XCMD3R3ZBZQQSW6E0793B","x-twitter-scraper","Build GitHub Copilot workflows with Xquik X API SDKs, REST endpoints, hosted Apify Actor runs, MCP tools, TweetClaw OpenClaw plugin installs, signed webhooks, tweet search, user lookup, follower exports, media actions, and agent automation.","https:\u002F\u002Fgithub.com\u002FReihantt6\u002Fsns-myagent\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fx-twitter-scraper\u002FSKILL.md",[],[]]