agentleFS
Sign inStart free
GitHubKnown publishergithub/squad/.github/skills/gh-aw-reliability/SKILL.md

gh-aw-reliability

Skill3.4k starsChanged 2 months agoMITView on GitHub

Validate GitHub Agentic Workflow contracts through compiled artifacts and realistic mutations

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Use this skill when creating or changing Squad GitHub Agentic Workflow sources, safe outputs, authorization, or prompt inputs.

    line 11
  2. Distinctive:

    Treat workflow source, compiled lock output, and declared safe outputs as a single contract.

    line 17
  3. Distinctive:

    Test a realistic mutation of the live source and prove the relevant gate fails.

    line 26

≈ “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

Context

Use this skill when creating or changing Squad GitHub Agentic Workflow sources, safe outputs, authorization, or prompt inputs. Prompt prose can look correct while the compiled workflow does nothing or authorizes the wrong action.

Patterns

  • Treat workflow source, compiled lock output, and declared safe outputs as a single contract.
  • Strict-compile the workflow and inspect the emitted artifact; a zero exit code alone is not enough when a specific handler, input, or protected-file rule is required.
  • Enumerate all call sites when changing parsing, normalization, ownership binding, or command routing.
  • Bind authorization, labels, and mutable actions to committed provenance rather than an unverified working-tree claim.
  • Fail closed when the compiler, required tool, or evidence needed to prove the contract is unavailable.
  • Test a realistic mutation of the live source and prove the relevant gate fails.

Examples

test/gh-aw-deps-worker-workflow.test.ts mutates a real worker source, runs the compiler, then asserts on the compiled protected-files contract. test/gh-aw-activate-roster-binding.test.ts checks roster-derived authorization behavior.

Anti-Patterns

  • Validating only prompt text or a hand-built configuration object
  • Letting unavailable workflow tooling silently skip a protection gate
  • Testing one parser helper while leaving an alternate command-dispatch caller untested
  • Minting labels or authorization from role prose instead of committed roster evidence

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