heredoc-file-write

Use shell heredoc syntax as a workaround when write_file fails on complex TypeScript/JSX/code files with encoding or escaping issues

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/heredoc-file-write/SKILL.md

Quality

Content

85%

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 executable heredoc examples and a clear, verified workflow in a well-organized single file. Its main weakness is verbosity from redundant example scenarios and restated sections that could be tightened.

Suggestions

Trim the three near-identical example scenarios to one representative example, or consolidate them into a compact multi-snippet block, to reduce redundant tokens.

Remove or fold the 'Core Technique' section into Step 2 and the 'Advantages Over write_file' section into the limitations/troubleshooting context, since both restate content already covered in the steps.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of basic-concept explanations Claude already knows, but it is padded with three near-identical example scenarios and a 'Core Technique'/'Advantages Over write_file' section that restates the step-by-step content, fitting the score-2 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It provides fully executable, copy-paste-ready heredoc commands across .tsx, .json, and .sh examples with specific quoting rules, matching the score-3 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The four-step sequence is clear and includes an explicit verification step (Step 4: check file exists, verify content) plus a Troubleshooting section for error recovery, meeting the score-3 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor for a single-purpose skill.	3 / 3
Progressive Disclosure	The skill is a single self-contained file with no bundle references needed, organized into well-labeled sections (When to Use, Steps, Examples, Limitations, Troubleshooting) with no nested references, giving easy navigation as expected at the score-3 level.	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 cleanly answers both what the skill does and when to use it, with a distinct, narrowly-scoped trigger. It is slightly held back by naming only one concrete action and by missing a few common user phrasings of the trigger.

Suggestions

Add one or two more concrete actions (e.g., 'create or overwrite files reliably') to lift specificity toward the multiple-actions anchor.

Include common user-facing trigger variations such as 'file write error', 'unknown error', or 'can't create file' alongside 'write_file fails' for broader trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('complex TypeScript/JSX/code files') and a single concrete action ('Use shell heredoc syntax as a workaround'), but it does not list multiple distinct actions, so it stops short of the score-3 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	It clearly states both what ('Use shell heredoc syntax as a workaround') and an explicit when trigger ('when write_file fails on complex TypeScript/JSX/code files with encoding or escaping issues'), satisfying the score-3 'clearly answers both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	It surfaces relevant natural phrases ('write_file fails', 'encoding or escaping issues'), but misses common variations a user might say such as 'file write error', 'unknown error', or 'can't create file', matching the score-2 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The trigger is narrowly scoped to write_file failures with encoding/escaping issues on code files, giving it a clear niche that is unlikely to conflict with other skills, matching the score-3 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 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: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/heredoc-file-write/SKILL.md
Commit: c5a9c4b

Reviewed: 2 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.