CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, highly actionable pattern reference with a genuine one-level-deep bundle split into references/details.md. Its main weakness is token efficiency: it re-explains basic context-manager semantics Claude already knows and carries padded boilerplate in the class examples.

Suggestions

Cut or compress the 'Core Concepts' section — Claude already knows what `with`, `__enter__`/`__exit__`, and exception-suppression semantics do; fold the one non-obvious point (return True suppresses) into the relevant pattern.

Trim per-method docstrings and the duplicate manual-management usage block in Pattern 1, and let the code comments carry behavior notes instead.

Label the pattern list as an explicit navigation summary and add pointers (e.g. 'see references/details.md') to Best Practices items 6-8, whose details live in the reference file.

DimensionReasoningScore

Conciseness

The bulk is executable code, but the "Core Concepts" section explains basic Python semantics Claude already knows — "The `with` statement ensures resources are released automatically, even on exceptions", "`__enter__`/`__exit__` for sync", "Return `True` from `__exit__` to suppress exceptions" — and the class examples pad with per-method docstrings ("Close connection if open") and a redundant manual-management variant. This matches the 3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened') rather than 4, where over-explanation would be only minor.

3 / 5

Actionability

All five pattern sections contain complete, typed, copy-paste-ready Python covering the common cases: class-based sync and async context managers, @contextmanager/@asynccontextmanager with a transaction rollback path, and unconditional multi-resource cleanup. It is not a 4 because there are no real gaps — third-party names (psycopg, asyncpg, TracebackType) are conventional illustrative imports rather than pseudocode or missing steps.

5 / 5

Workflow Clarity

This is a pattern-library skill rather than a multi-step workflow, and its guidance is unambiguous: Quick Start gives an immediately usable template, patterns progress from simple to complex, and Best Practices item 10 says "Test cleanup paths - Verify resources are released on errors". It stops short of 5 because there is no concrete validation example (e.g. a test showing cleanup runs on exception) backing that item, and no decision guidance for choosing among the four patterns beyond one-line hints.

4 / 5

Progressive Disclosure

The bundle is well structured: SKILL.md holds core patterns 1-4 and points to references/details.md, which exists and contains exactly the advertised "## Advanced Patterns" (patterns 5-9), one level deep and clearly signaled ("Read that file when the navigation summary above is insufficient"). It is not a 5 because that signal wording references a 'navigation summary' that is not explicitly labeled, and Best Practices items 6-8 (ExitStack, list+join accumulation, time-to-first-byte metrics) summarize content that lives only in details.md without pointing there — minor organization gaps per the 4 anchor.

4 / 5

Total

16

/

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 description that clearly states what the skill does and gives explicit, natural 'Use when' triggers in third person. Trigger coverage and capability listing are solid, with only minor room for synonyms and action-verb phrasing.

DimensionReasoningScore

Specificity

The description names the domain ("Python resource management") and lists several concrete capability areas — "context managers, cleanup patterns, and streaming" — with only minor gaps in coverage. It falls short of the 5 anchor because the capabilities are topic nouns rather than explicit actions (compare "Extract text and tables... fill forms, merge documents") and omits items the body actually covers such as async context managers and exception suppression.

4 / 5

Completeness

It explicitly answers both questions: the 'what' ("Python resource management with context managers, cleanup patterns, and streaming") and a concrete 'when' with specific trigger phrases ("Use when managing connections, file handles, implementing cleanup logic, or building streaming responses with accumulated state"). This mirrors the 5 anchor's structure of concrete what + explicit trigger-laden when; the 4 anchor applies only when the 'when' is weakly specified, which is not the case here.

5 / 5

Trigger Term Quality

The 'Use when' clause supplies natural phrases users would say — "managing connections, file handles, implementing cleanup logic, or building streaming responses with accumulated state" — plus "context managers" in the what-clause. It is not a 5 because common synonyms and variations are missing (e.g. 'with statement', 'releasing resources', 'resource leaks', 'closing connections'), but coverage is clearly better than the partial keyword set of the 3 anchor.

4 / 5

Distinctiveness Conflict Risk

The Python-specific framing and resource-lifecycle triggers (context managers, cleanup, streaming with accumulated state) give it a clear niche with mostly distinct triggers. It is not a 5 because "streaming responses" and "file handles" could plausibly overlap with a general streaming or file-processing skill, matching the 4 anchor's 'minor overlap risk with closely related 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/python-development/skills/python-resource-management/SKILL.md

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.