CtrlK
BlogDocsLog inGet started
Tessl Logo

python-heredoc-fallback

Use shell Python heredoc as fallback when code sandbox fails

68

Quality

81%

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

87%

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

The content is lean, highly actionable, and well-organized for a single-pattern skill. The one gap is the absence of an explicit verify/validation checkpoint for the file-writing examples.

Suggestions

Add an explicit validation checkpoint after file-generation examples (e.g., verify the output file exists and is non-empty with `ls -la output_graph.png` and assert on size) to create a feedback loop.

Promote the "Add print statements" best practice into a concrete verify-and-retry step for the core pattern.

DimensionReasoningScore

Conciseness

The body is code-forward and lean, assuming Claude's knowledge of Python and heredocs without explaining basic concepts, so every section earns its place.

3 / 3

Actionability

Provides three complete, executable heredoc examples (matplotlib, python-docx, file ops) plus explicit syntax rules and a troubleshooting table, making it copy-paste ready.

3 / 3

Workflow Clarity

The single-pattern flow (When to Use -> Core Pattern -> examples) is clear, but file-generation operations lack an explicit validation/verify checkpoint beyond print statements, which caps clarity per the batch/file-operations rule.

2 / 3

Progressive Disclosure

A single well-organized SKILL.md under ~130 lines with no need for external references, satisfying the simple-skill exception for the top anchor; no bundle files are present.

3 / 3

Total

11

/

12

Passed

Description

75%

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 concise and clearly states both what and when with a distinct, narrowly-scoped trigger. Its main weakness is limited action coverage and slightly jargon-heavy trigger terms.

Suggestions

Expand the action clause beyond one action (e.g., "Run Python code, generate graphs, and create documents via shell heredoc") to lift specificity to the top anchor.

Add more natural trigger terms a user might say, such as "when the code sandbox is down or won't connect" alongside "code sandbox fails".

DimensionReasoningScore

Specificity

States one concrete action ("Use shell Python heredoc as fallback") and a trigger ("when code sandbox fails"), but lists only a single action rather than multiple specific concrete actions, so it sits below the top anchor.

2 / 3

Completeness

It explicitly states both what to do (shell Python heredoc as fallback) and when to use it (when code sandbox fails), satisfying the explicit-trigger requirement for the top anchor.

3 / 3

Trigger Term Quality

Includes relevant but jargon-leaning terms ("code sandbox fails", "heredoc", "fallback") and misses common user phrasings, matching the "some relevant keywords but missing common variations" anchor.

2 / 3

Distinctiveness Conflict Risk

Targets a narrow niche (sandbox-failure heredoc fallback) with a distinct trigger unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

10

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
HKUDS/OpenSpace
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.