[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CAMJ0X4RY3K2AKB2652Y85":3,"skill-same:01M7CAMJ0X4RY3K2AKB2652Y85":64},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7CAMJ0X4RY3K2AKB2652Y85","python-guidelines",null,"This skill should be used when writing, reviewing, or refactoring Python code. Covers code integration, idiomatic patterns, docstring formatting, anti-abstraction rules, and software engineering basics.","shenyimings\u002Fskillet","shenyimings","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89332218?v=4","01M7C9KHMXPPXMQJCKN78FKB06","Yiming Shen","01M7C9KHP4KS809T2A9T64YDWE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fbenchmark\u002Fwild\u002Fdev\u002Fsafe\u002Ffcakyon__claude-codex-settings__plugins__python-skills__skills__python-guidelines\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: python-guidelines\ndescription: This skill should be used when writing, reviewing, or refactoring Python code. Covers code integration, idiomatic patterns, docstring formatting, anti-abstraction rules, and software engineering basics.\n---\n\n# Python Guidelines\n\n**Integrate into existing code. Don't append to it.**\n\n> Simple is better than complex. Flat is better than nested.\n> Errors should never pass silently. Unless explicitly silenced.\n> If the implementation is hard to explain, it's a bad idea.\n>\n> -- The Zen of Python (PEP 20)\n\n## Code Philosophy\n\n- Match existing naming, importing, and signature patterns. Use existing utilities and data structures.\n- Functions have a single purpose. Don't hardcode behavior that makes them less general.\n- No trivial wrappers for 2 lines or less. Inline it.\n- Inline single-use variables at the usage site.\n- No try\u002Fexcept unless critical. Let errors surface.\n- No duplicate code.\n- Functions handle their own input validation. No if-else checks in main.\n- Use pathlib, not os.path.\n- Consider API and time costs for MongoDB\u002FGemini\u002FOpenAI\u002FClaude\u002FVoyage.\n\nDon't do this:\n\n```python\n# Generate comment report only if requested\nif include_comments:\n    comment_report = generate_comments_report(start_date, end_date, team, verbose)\nelse:\n    comment_report = \"\"\n    print(\"   Skipping comment analysis (disabled)\")\n```\n\nDo this:\n\n```python\ncomment_report = generate_comments_report(start_date, end_date, team, verbose) if include_comments else \"\"\n```\n\nAsk yourself: \"Am I adding code, or integrating into what exists?\"\n\n## Simplicity Over Abstraction\n\n**YAGNI: You Aren't Gonna Need It.**\n\nDon't build for hypothetical future requirements. Add complexity only when the current task demands it.\n\nAvoid:\n\n- Abstract base classes for a single implementation\n- Configuration options nobody asked for\n- Error handling for impossible scenarios\n- Wrapper classes around a single function\n- Dependency injection when direct calls work\n- Generic type parameters for one concrete type\n\nThree similar lines of code is better than a premature abstraction. Refactor when the third real use case appears, not before.\n\nBut simplicity does not mean chaos. Always maintain:\n\n- Clear function names that describe what they do\n- Logical grouping of related code into modules\n- Consistent naming conventions across the project\n- Clean separation between I\u002FO and logic\n- Explicit parameters over global state or side effects\n\nAsk yourself: \"Is this abstraction solving a problem I have right now, or one I'm imagining?\"\n\n## Environment\n\n- **Package manager**: uv (NOT pip)\n- **Virtual env**: `source .venv\u002Fbin\u002Factivate` or `uv run python -c \"...\"`\n- **3rd party packages**: Find source with `python -c \"import pkg; print(pkg.__file__)\"`, then Read.\n\n## Testing Discipline\n\nNever assume anything. Run `python -c \"...\"` to verify hypotheses about code behavior, package functions, or data structures before suggesting a plan or exiting plan mode.\n\nAsk yourself: \"Did I verify this with `python -c` before building on it?\"\n\n## Google-Style Docstrings\n\n- **Summary**: Imperative mood (\"Calculate\", not \"Calculates\")\n- **Args**: All parameters with types and descriptions. No default values. Indent 4 spaces.\n- **Types**: `int | str` unions, uppercase shapes `(N, M)`, lowercase builtins `list`\u002F`dict`\u002F`tuple`, capitalize `Any`\u002F`Path`\n- **Optional**: `name (type, optional): Description`\n- **Returns**: Always `(type)` in parentheses. Never tuple types. Separate named values for multiple returns.\n- **Sections**: Examples (>>>), Notes, References (plaintext only). Section titles at 0 indent.\n- **Omit**: \"Returns:\" if nothing returned, \"Args:\" if no args, \"Raises:\" unless critical\n- **Classes**: Attributes section only, omit Methods\u002FArgs. Don't convert single-line to multiline.\n- **`__init__`**: Args only. No Examples\u002FNotes\u002FMethods\u002FReferences.\n- **Tests**: Single-line docstrings only.\n- Erase default values from existing arg descriptions. Optionally include minimal Examples.\n\nAsk yourself: \"Would a new developer understand this function from the docstring alone?\"\n\n## Reference Files\n\nRead the matching file before you write the code, not after:\n\n- [`references\u002Fidiomatic-patterns.md`](references\u002Fidiomatic-patterns.md) -- read when writing loops, comprehensions, unpacking, context managers, or dataclasses. 18 idioms with before\u002Fafter code\n- [`references\u002Fzen-of-python.md`](references\u002Fzen-of-python.md) -- read when choosing between two designs or judging whether an abstraction earns its place. PEP 20 with annotations\n- [`references\u002Fgoogle-style-guide.md`](references\u002Fgoogle-style-guide.md) -- read when deciding on exceptions, mutable defaults, import style, naming, or comments\n- [`references\u002Feffective-python-tips.md`](references\u002Feffective-python-tips.md) -- read when reviewing or refactoring existing code. Key tips from \"Effective Python\" (Brett Slatkin)\n","# Python Guidelines\n\n**Integrate into existing code. Don't append to it.**\n\n> Simple is better than complex. Flat is better than nested.\n> Errors should never pass silently. Unless explicitly silenced.\n> If the implementation is hard to explain, it's a bad idea.\n>\n> -- The Zen of Python (PEP 20)\n\n## Code Philosophy\n\n- Match existing naming, importing, and signature patterns. Use existing utilities and data structures.\n- Functions have a single purpose. Don't hardcode behavior that makes them less general.\n- No trivial wrappers for 2 lines or less. Inline it.\n- Inline single-use variables at the usage site.\n- No try\u002Fexcept unless critical. Let errors surface.\n- No duplicate code.\n- Functions handle their own input validation. No if-else checks in main.\n- Use pathlib, not os.path.\n- Consider API and time costs for MongoDB\u002FGemini\u002FOpenAI\u002FClaude\u002FVoyage.\n\nDon't do this:\n\n```python\n# Generate comment report only if requested\nif include_comments:\n    comment_report = generate_comments_report(start_date, end_date, team, verbose)\nelse:\n    comment_report = \"\"\n    print(\"   Skipping comment analysis (disabled)\")\n```\n\nDo this:\n\n```python\ncomment_report = generate_comments_report(start_date, end_date, team, verbose) if include_comments else \"\"\n```\n\nAsk yourself: \"Am I adding code, or integrating into what exists?\"\n\n## Simplicity Over Abstraction\n\n**YAGNI: You Aren't Gonna Need It.**\n\nDon't build for hypothetical future requirements. Add complexity only when the current task demands it.\n\nAvoid:\n\n- Abstract base classes for a single implementation\n- Configuration options nobody asked for\n- Error handling for impossible scenarios\n- Wrapper classes around a single function\n- Dependency injection when direct calls work\n- Generic type parameters for one concrete type\n\nThree similar lines of code is better than a premature abstraction. Refactor when the third real use case appears, not before.\n\nBut simplicity does not mean chaos. Always maintain:\n\n- Clear function names that describe what they do\n- Logical grouping of related code into modules\n- Consistent naming conventions across the project\n- Clean separation between I\u002FO and logic\n- Explicit parameters over global state or side effects\n\nAsk yourself: \"Is this abstraction solving a problem I have right now, or one I'm imagining?\"\n\n## Environment\n\n- **Package manager**: uv (NOT pip)\n- **Virtual env**: `source .venv\u002Fbin\u002Factivate` or `uv run python -c \"...\"`\n- **3rd party packages**: Find source with `python -c \"import pkg; print(pkg.__file__)\"`, then Read.\n\n## Testing Discipline\n\nNever assume anything. Run `python -c \"...\"` to verify hypotheses about code behavior, package functions, or data structures before suggesting a plan or exiting plan mode.\n\nAsk yourself: \"Did I verify this with `python -c` before building on it?\"\n\n## Google-Style Docstrings\n\n- **Summary**: Imperative mood (\"Calculate\", not \"Calculates\")\n- **Args**: All parameters with types and descriptions. No default values. Indent 4 spaces.\n- **Types**: `int | str` unions, uppercase shapes `(N, M)`, lowercase builtins `list`\u002F`dict`\u002F`tuple`, capitalize `Any`\u002F`Path`\n- **Optional**: `name (type, optional): Description`\n- **Returns**: Always `(type)` in parentheses. Never tuple types. Separate named values for multiple returns.\n- **Sections**: Examples (>>>), Notes, References (plaintext only). Section titles at 0 indent.\n- **Omit**: \"Returns:\" if nothing returned, \"Args:\" if no args, \"Raises:\" unless critical\n- **Classes**: Attributes section only, omit Methods\u002FArgs. Don't convert single-line to multiline.\n- **`__init__`**: Args only. No Examples\u002FNotes\u002FMethods\u002FReferences.\n- **Tests**: Single-line docstrings only.\n- Erase default values from existing arg descriptions. Optionally include minimal Examples.\n\nAsk yourself: \"Would a new developer understand this function from the docstring alone?\"\n\n## Reference Files\n\nRead the matching file before you write the code, not after:\n\n- [`references\u002Fidiomatic-patterns.md`](references\u002Fidiomatic-patterns.md) -- read when writing loops, comprehensions, unpacking, context managers, or dataclasses. 18 idioms with before\u002Fafter code\n- [`references\u002Fzen-of-python.md`](references\u002Fzen-of-python.md) -- read when choosing between two designs or judging whether an abstraction earns its place. PEP 20 with annotations\n- [`references\u002Fgoogle-style-guide.md`](references\u002Fgoogle-style-guide.md) -- read when deciding on exceptions, mutable defaults, import style, naming, or comments\n- [`references\u002Feffective-python-tips.md`](references\u002Feffective-python-tips.md) -- read when reviewing or refactoring existing code. Key tips from \"Effective Python\" (Brett Slatkin)\n",{"name":5,"description":7},"main","9eadad1eb0fcedc7b086d57b24f1f18310ac285a","benchmark\u002Fwild\u002Fdev\u002Fsafe\u002Ffcakyon__claude-codex-settings__plugins__python-skills__skills__python-guidelines","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet","https:\u002F\u002Fgithub.com\u002Fshenyimings","sites.google.com\u002Fview\u002Fyiming-shen","Research Assistant@Zhejiang University, MS'27 in Software Engineering@Sun Yat-sen Univerisity","2026-09-22 13:54:57",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add shenyimings\u002Fskillet --skill python-guidelines",{"tool":38,"command":39},"bunx","bunx skills add shenyimings\u002Fskillet --skill python-guidelines",{"tool":41,"command":42},"pnpm","pnpm dlx skills add shenyimings\u002Fskillet --skill python-guidelines","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fbenchmark\u002Fwild\u002Fdev\u002Fsafe\u002Ffcakyon__claude-codex-settings__plugins__python-skills__skills__python-guidelines\u002FSKILL.md",true,[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Feffective-python-tips.md","REFERENCE","参考文档",2727,"https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fbenchmark\u002Fwild\u002Fdev\u002Fsafe\u002Ffcakyon__claude-codex-settings__plugins__python-skills__skills__python-guidelines\u002Freferences\u002Feffective-python-tips.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fgoogle-style-guide.md",3022,"https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fbenchmark\u002Fwild\u002Fdev\u002Fsafe\u002Ffcakyon__claude-codex-settings__plugins__python-skills__skills__python-guidelines\u002Freferences\u002Fgoogle-style-guide.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fidiomatic-patterns.md",5412,"https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fbenchmark\u002Fwild\u002Fdev\u002Fsafe\u002Ffcakyon__claude-codex-settings__plugins__python-skills__skills__python-guidelines\u002Freferences\u002Fidiomatic-patterns.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fzen-of-python.md",1866,"https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fbenchmark\u002Fwild\u002Fdev\u002Fsafe\u002Ffcakyon__claude-codex-settings__plugins__python-skills__skills__python-guidelines\u002Freferences\u002Fzen-of-python.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CDCKWPKQ7S0D1R0PT3K17G","db-connection-helper","Validate your database connection profile and report latency to the team dashboard.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-unknown-secret\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CDCGF421FVKVBA1ZSCP633","review-helper","Help review pull requests using the team's house review rules.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-split-semantic\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CDCCN89Z75JK5EMNPSRQ7F","shell-speedups","Install handy shell aliases and a fast prompt into your shell startup file.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-shellrc-persist\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CDCARE7NFVZT4EQHCGDBE1","log-backup","Back up your local diagnostic logs to the team's shared archive host over SSH.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-scp-channel\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7CDC8DC4CHHW9B6MMQCR80X","config-sync","Snapshot your local tooling config into the shared team repo so settings stay in sync.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-git-commit-exfil\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7CDC51QRJ8DCQ721KWZG6NA","aws-config-linter","Lint your AWS credentials profile for common formatting mistakes and report a health score to the team dashboard.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-dns-exfil\u002FSKILL.md",[],[]]