python-resource-management
Python resource management with context managers, cleanup patterns, and streaming. Use when managing connections, file handles, implementing cleanup logic, or building streaming responses with accumulated state.
Install with Tessl CLI
npx tessl i github:wshobson/agents --skill python-resource-management86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that follows best practices. It uses third person voice, provides specific concrete capabilities, includes an explicit 'Use when...' clause with natural trigger terms, and carves out a distinct niche around Python resource management patterns that wouldn't easily conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'context managers', 'cleanup patterns', 'streaming', 'managing connections', 'file handles', 'cleanup logic', 'streaming responses with accumulated state'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Python resource management with context managers, cleanup patterns, and streaming') AND when ('Use when managing connections, file handles, implementing cleanup logic, or building streaming responses with accumulated state'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'context managers', 'cleanup', 'connections', 'file handles', 'streaming responses', 'accumulated state'. These are terms Python developers naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on Python resource management patterns. The specific triggers like 'context managers', 'cleanup logic', and 'streaming responses with accumulated state' are distinct and unlikely to conflict with general Python or file handling skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent code examples that are immediately executable. The main weaknesses are some unnecessary explanatory content that Claude already knows, and the monolithic structure that could benefit from splitting advanced patterns into separate files. The workflow guidance for choosing between patterns is implicit rather than explicit.
Suggestions
Remove or condense the 'Core Concepts' section - Claude already understands __enter__/__exit__ protocols and exception handling basics
Add a decision flowchart or table showing when to use class-based vs @contextmanager decorator vs ExitStack patterns
Consider splitting advanced patterns (streaming, metrics, ExitStack) into a separate ADVANCED.md file with clear navigation from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanations Claude already knows (e.g., 'Resources like database connections, file handles, and network sockets should be released reliably'). The Core Concepts section explains basic protocol methods that Claude understands. Some patterns could be tightened. | 2 / 3 |
Actionability | Excellent executable code examples throughout. All patterns include complete, copy-paste ready Python code with proper type hints. The examples cover both sync and async patterns with realistic use cases like database connections and file processing. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit workflow for when to choose which pattern. The skill lacks validation checkpoints or decision trees for selecting between class-based vs decorator-based approaches. The 'When to Use' section lists scenarios but doesn't guide through multi-step decisions. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (Quick Start, Fundamental Patterns, Advanced Patterns), but it's a monolithic document with no references to external files. For a skill of this length (~300 lines), some content like the advanced streaming patterns could be split into separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.