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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

The content is highly actionable with complete, executable patterns and a well-signaled one-level reference, but it loses points for restating basic concepts Claude knows and for missing explicit validation/feedback checkpoints in its resource-handling workflows.

Suggestions

Trim or remove the 'Core Concepts' section that re-explains what `with` and `__enter__`/`__exit__` do, since Claude already knows these; let the code examples carry that knowledge.

Add an explicit validation/feedback step for destructive or batch resource operations (e.g., verify cleanup ran, assert no leaked handles) to lift workflow clarity beyond a sequence of usage snippets.

Move one or two of the heavier inline patterns into references/details.md so the SKILL.md body functions more as a lean overview pointing to detail.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clean code, but the 'Core Concepts' section restates basics Claude already knows (e.g., 'The `with` statement ensures resources are released automatically, even on exceptions'), the score-2 anchor for mostly efficient content that could be tightened.	2 / 3
Actionability	All four patterns provide fully executable, copy-paste-ready code (DatabaseConnection, AsyncDatabasePool, @contextmanager, FileProcessor) with concrete usage examples, matching the score-3 anchor of executable, specific examples.	3 / 3
Workflow Clarity	Patterns are sequenced via usage examples but lack explicit validation checkpoints or feedback loops; for resource/database operations the rubric flags missing validation, capping this at the score-2 anchor of steps present but checkpoints missing or implicit.	2 / 3
Progressive Disclosure	The body is well-organized into sections and defers advanced material to a real, well-signaled one-level-deep reference ('Detailed sections ... live in references/details.md'), matching the score-3 anchor of clear overview with one-level-deep navigation.	3 / 3
	Total	10 / 12 Passed

Description

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.

The description is specific, complete, and distinct, explicitly covering both what the skill does and when to use it with natural trigger terms. It hits the top anchor on all four dimensions with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'managing connections, file handles, implementing cleanup logic, or building streaming responses with accumulated state' — matching the score-3 anchor of multiple specific concrete actions rather than a single domain.	3 / 3
Completeness	It answers both what ('Python resource management with context managers, cleanup patterns, and streaming') and when (explicit 'Use when managing connections, file handles, implementing cleanup logic...'), satisfying the score-3 anchor with an explicit trigger clause.	3 / 3
Trigger Term Quality	Natural terms a user would say ('connections', 'file handles', 'cleanup logic', 'streaming responses') are present, giving good coverage; not scored lower since these are genuine user-facing triggers rather than jargon.	3 / 3
Distinctiveness Conflict Risk	'Python resource management' is a clear niche with distinct triggers (context managers, cleanup, streaming state) unlikely to fire for unrelated skills, matching the score-3 anchor of a clear niche with distinct triggers.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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
Commit: 5cc2549

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.