agentleFS
Sign inStart free
npownpow/claude-skills/gen-crash-test/SKILL.md

gen-crash-test

Skill4 starsChanged 6 months agoApache-2.0View on GitHub

Crash-recovery test for the sagaflow generic interpreter. Multiple sequential tool calls with a sleep in the middle.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run sagaflow doctor. If Temporal is unreachable, stop immediately and report:

    line 27
  2. Distinctive:

    Do NOT attempt an in-session workaround — this skill tests sagaflow, not Claude Code tools.

    line 31
  3. Very specific:

    Use write_artifact with path step1.md content Step 1 complete for $name.

    line 37
  4. Very specific:

    Use bash with command sleep 6 && echo 'slept 6s' and a 30s timeout.

    line 38
  5. Distinctive:

    After step 3, end your turn.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

gen-crash-test

Crash-recovery test for the sagaflow generic interpreter's crash-recovery and sequential tool execution. It requires sagaflow — there is no in-session fallback because the test target is the sagaflow interpreter itself.

Pre-flight check

Run sagaflow doctor. If Temporal is unreachable, stop immediately and report:

gen-crash-test requires a running sagaflow worker (Temporal backend). Run temporal server start-dev and sagaflow worker run, then retry.

Do NOT attempt an in-session workaround — this skill tests sagaflow, not Claude Code tools.

Steps (sagaflow only)

Execute these three steps IN ORDER, one at a time, waiting for each tool result before the next:

  1. Use write_artifact with path step1.md content Step 1 complete for $name.
  2. Use bash with command sleep 6 && echo 'slept 6s' and a 30s timeout.
  3. Use write_artifact with path step3.md content Step 3 complete for $name — all steps survived!.

After step 3, end your turn. One text summary, no more tool calls.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free