agentleFS
Sign inStart free
DeevsDeevsDeevsDeevs/agent-system/mft-research-experts/SKILL.md

mft-research-experts

Skill40 starsChanged 8 months agoApache-2.0View on GitHub

Run research orchestration for data quality, factor geometry, hypothesis validation, and incident forensics. Use when you need SHIP/KILL/ITERATE decisions with strict validation. Triggers: mft-strategist, data-sentinel, factor-geometer, skeptic, forensic-auditor, research pipeline, hypothesis validation, post-mortem.

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

    Use this skill for end-to-end quantitative research orchestration and validation.

    line 8
  2. Distinctive:

    Read README.md and enforce the sequencing rule: data validation first.

    line 20
  3. Very specific:

    If a dataset is involved, spawn data-sentinel first and wait for completion before any other role.

    line 21
  4. Very specific:

    If the user requested one role explicitly, spawn that role with agent_type and targeted scope.

    line 22
  5. Very specific:

    If no role was specified, default to mft-strategist.

    line 23

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

MFT Research Experts

Use this skill for end-to-end quantitative research orchestration and validation.

Role Map

  • mft-strategist -> agents/mft-strategist.md
  • data-sentinel -> agents/data-sentinel.md
  • factor-geometer -> agents/factor-geometer.md
  • skeptic -> agents/skeptic.md
  • forensic-auditor -> agents/forensic-auditor.md

Workflow

  1. Read README.md and enforce the sequencing rule: data validation first.
  2. If a dataset is involved, spawn data-sentinel first and wait for completion before any other role.
  3. If the user requested one role explicitly, spawn that role with agent_type and targeted scope.
  4. If no role was specified, default to mft-strategist; let it coordinate and request follow-up role spawns as needed.
  5. For full validation flows, ensure factor-geometer runs before skeptic.
  6. For incident or regression investigations, include forensic-auditor.
  7. Synthesize outputs into a clear SHIP/KILL/ITERATE recommendation with assumptions and confidence.

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