CtrlK
BlogDocsLog inGet started
Tessl Logo

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

62

Quality

73%

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 ./benchmarks/gdpval/skills/heredoc-file-write/SKILL.md
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.

The skill is highly actionable with executable heredoc examples and a clear sequenced workflow including verification. Its main weakness is conciseness, with several padded sections and redundant examples that could be tightened.

Suggestions

Trim the "Advantages Over write_file" section and consolidate the three example scenarios into one representative example plus a brief note on adapting for JSON/shell.

Avoid restating the description verbatim in the "When to Use This Skill" section; reference it or keep only the trigger conditions.

Strengthen the verification step with a content-equality check (e.g., compare against expected output) rather than only ls/cat inspection.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete examples, but the "Advantages Over write_file" section, three full example scenarios, and repetition of the description add padding that could be trimmed.

3 / 5

Actionability

Provides fully executable, copy-paste-ready heredoc commands with quoted-delimiter rules, covering TypeScript/JSX, JSON, and shell script cases.

5 / 5

Workflow Clarity

Four sequenced steps include an explicit verification checkpoint (Step 4: Verify File Creation) and a Troubleshooting feedback section, though the verification is light (ls/cat) rather than a robust validate-fix-retry loop.

4 / 5

Progressive Disclosure

Single SKILL.md with well-organized sections and no nested references; no bundle files exist, so structure is appropriate, though the inlined examples and advantages section could be slimmed for a tighter overview.

4 / 5

Total

16

/

20

Passed

Description

71%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.

The description clearly answers both what and when with a concrete, distinct trigger, but is light on action breadth and natural keyword variations. It is well-targeted for its narrow fallback purpose.

Suggestions

Broaden specificity by naming additional concrete actions (e.g., create files with special characters, preserve exact formatting) beyond the single heredoc workaround.

Add natural trigger synonyms users might say, such as "file write errors", "can't write file", or "special characters in code", to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("Use shell heredoc syntax as a workaround") but offers only that single action, matching the 1-2 concrete actions anchor rather than comprehensive coverage.

3 / 5

Completeness

Explicitly states what to do (use heredoc syntax as a workaround) and when (when write_file fails on complex TypeScript/JSX/code files with encoding or escaping issues), with concrete trigger phrases for both.

5 / 5

Trigger Term Quality

Includes relevant phrases like "write_file fails" and "encoding or escaping issues", but lacks common synonyms or file-extension variations users might naturally say, so keyword coverage is partial.

3 / 5

Distinctiveness Conflict Risk

The write_file-failure fallback trigger is a distinct niche with minimal overlap, though it could marginally intersect general shell/file-writing skills.

4 / 5

Total

15

/

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
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.