CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/python-development/skills/python-resource-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, code-rich skill body that splits advanced material into a genuine reference file and provides executable patterns. It loses points for restating basic Python concepts, lacking import completeness, and offering no validation workflow for a topic where cleanup-correctness is the whole point.

Suggestions

Trim the 'Core Concepts' section: drop bullets that restate Python basics Claude already knows (e.g., what `with` does, that `__exit__` always runs), keeping only non-obvious guidance.

Make each code snippet import-complete (add imports for Connection, TracebackType, IO, psycopg, asyncpg) so examples are truly copy-paste ready.

Convert the details.md pointer into a markdown link (e.g., 'See [references/details.md](references/details.md) for advanced patterns') and rephrase the navigation hint for clarity.

DimensionReasoningScore

Conciseness

Mostly code-driven and efficient, but the 'Core Concepts' section restates basics Claude already knows ('The `with` statement ensures resources are released automatically', '__exit__ always runs', 'Return `True` from `__exit__` to suppress exceptions'). Not a 4 because several of these concept bullets are unnecessary padding rather than trimmable single instances.

3 / 5

Actionability

Provides multiple complete, mostly executable class- and decorator-based examples covering sync/async context managers and cleanup. Not a 5 because some referenced types (Connection, TracebackType, IO) and libraries (psycopg, asyncpg) appear in snippets without their imports, leaving minor copy-paste gaps.

4 / 5

Workflow Clarity

Organized as a pattern catalog ('When to Use' → 'Quick Start' → 'Fundamental Patterns') with no explicit multi-step sequence or validation checkpoints. Not a 4 because there is no feedback/validate loop, and not lower because the patterns are individually clear.

3 / 5

Progressive Disclosure

Overview patterns live in SKILL.md while advanced patterns are split into the real, one-level-deep references/details.md, with an explicit pointer ('Detailed sections ... live in references/details.md'). Not a 5 because the reference is mentioned in backticks rather than as a clickable markdown link and the 'navigation summary above' phrasing is slightly awkward.

4 / 5

Total

14

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states both capability and trigger conditions with concrete, natural keywords. Minor gaps in granular action coverage and synonym terms keep it just short of maximum.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'context managers, cleanup patterns, and streaming' plus 'managing connections, file handles, implementing cleanup logic, or building streaming responses with accumulated state' — with only minor coverage gaps (e.g., async managers, ExitStack not named). Not a 5 because the actions are broad categories rather than a maximally granular list.

4 / 5

Completeness

Explicitly 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') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a Python developer would say — 'context managers', 'cleanup', 'streaming', 'connections', 'file handles' — giving good keyword coverage. Not a 5 because common synonyms like 'with statement', 'resource leaks', or 'connection pools' are absent.

4 / 5

Distinctiveness Conflict Risk

'Python resource management' is a clear niche with distinct triggers (context managers, cleanup, streaming), giving mostly-distinct scope with minor overlap risk against general Python skills. Not a 5 because 'file handles' and 'connections' are broad enough to overlap with I/O or database skills.

4 / 5

Total

17

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.