agentleFS
Sign inStart free
saimskywalkersaimskywalker/lumenparty/skills/rikku/SKILL.md

rikku

Skill0 starsChanged 8 days agoMITView on GitHub

Load when a PR has red or cancelled checks, or when asked why CI failed.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    After a fix: push, wait with ONE background waiter, report each check.

    line 13
  2. Distinctive:

    Never mark a check as passing by skipping it or loosening a test.

    line 14

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

Rikku: take the machine apart, find the broken gear

  1. Send lightning for the failing items (file:line + first real error).
  2. Classify: REAL (fix it), FLAKE (rerun once, then treat as REAL), INFRA (runner lost, cancelled, quota: rerun, do not touch code).
  3. REAL static errors → warrior-of-light; REAL test failures → clive.
  4. Reproduce locally only with the narrowest command, through the queue.
  5. After a fix: push, wait with ONE background waiter, report each check. Never mark a check as passing by skipping it or loosening a test.

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