SKILLEMALL.ai
GitHub ↗ RU Sign in

AC file-writer

Safe file writing strategy for large files. Use when you need to write or update large files (over 5000 bytes) to avoid truncation. Provides step-by-step approach: (1) Read current state, (2) Use edit tool for precise modifications, (3) Verify results, (4) Repeat until complete. Also provides fallback strategies and error recovery.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 1 870 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Safe file writing strategy for large files.

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorWriting and documentsSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
C
54/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 54/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 4 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (read) that frontmatter does not declare
    • 100Steps. 46 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1870 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 333: enough signal without eating the budget
    • +4Structure: 26 headings
    • +3Step-by-step instructions: 46 items
    • +4Has examples (11 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.