agentleFS
Sign inStart free
kvantatechkvantatech/RedLine/.github/skills/apply-ws2-conventions/SKILL.md

apply-ws2-conventions

Skill1 starsChanged 3 months agoMITView on GitHub

Type: skill (deterministic) · Used by: perf-author · Status: STUB (P0 scaffold — not yet implemented) - Input: an authored k6 script file. - Ensure: shared/utils import present; Mimir tags set (environment, test_file, test_type, run_id, branch); Prometheus-RW + OTLP output configured; exit-non-zero-on-breach checklist applied. - Output: the script, conformed to the WS2 template. Pure templating — no model judgement, fixed rules only.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Ensure: shared/utils import present.

    line 10

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

apply-ws2-conventions

Apply WS2 template conventions — tags, Prometheus output, exit-code checklist.

Type: skill (deterministic) · Used by: perf-author · Status: STUB (P0 scaffold — not yet implemented)

Prompt

Apply WS2 template conventions to an authored script deterministically.

  • Input: an authored k6 script file.
  • Ensure: shared/utils import present; Mimir tags set (environment, test_file, test_type, run_id, branch); Prometheus-RW + OTLP output configured; exit-non-zero-on-breach checklist applied.
  • Output: the script, conformed to the WS2 template.

Pure templating — no model judgement, fixed rules only.

Tools

none — deterministic (plain code)

Data

  • Reads/writes: the authored script file (in the working PR branch)

Notes

Activation: P4. Pure templating. Hard rule: the exit-non-zero-on-breach checklist must be present so a threshold breach exits non-zero (exit code 97 is a FAIL). p95 is the percentile used in threshold conventions.

Frozen skill registry: AGENTS.md in this repo

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