agentleFS
Sign inStart free
proffesor-for-testingproffesor-for-testing/agentic-qe/.agents/skills/aqe-ruflo/SKILL.md

aqe-ruflo

Skill515 starsChanged 22 days agoMITView on GitHub

Add optional Ruflo development-time orchestration to an Agentic QE workflow. Use when a task benefits from coordinated swarms, persistent cross-session memory, routing, or Ruflo hooks. Do not use for a one-shot edit, and never add Ruflo to shipped AQE runtime dependencies.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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. Distinctive:

    Keep the ownership boundary explicit:

    line 8
  2. Very specific:

    Never import Ruflo from product code or add ruflo, claude-flow, or @claude-flow/cli as an AQE runtime dependency.

    line 13
  3. Distinctive:

    Before using Ruflo, confirm that multi-agent coordination is worth its overhead.

    line 16
  4. Distinctive:

    Prefer a small, risk-selected QE fleet over activating every agent.

    line 17
  5. Distinctive:

    Use the installed Ruflo MCP tools when available.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Orchestrate AQE with Ruflo

Keep the ownership boundary explicit:

  • AQE owns quality specialization, test evidence, gates, and verdicts.
  • Ruflo owns development-time task coordination, handoffs, hooks, routing, and cross-session orchestration memory.
  • Never import Ruflo from product code or add ruflo, claude-flow, or @claude-flow/cli as an AQE runtime dependency.

Before using Ruflo, confirm that multi-agent coordination is worth its overhead. Prefer a small, risk-selected QE fleet over activating every agent.

For projects that explicitly want Ruflo, initialize or inspect it through its external CLI:

npx ruflo doctor
npx ruflo discover-plugins

Use the installed Ruflo MCP tools when available. Treat their absence as graceful degradation: AQE quality workflows must continue to work without Ruflo installed.

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