agentleFS
ohad6kohad6k/emulo/skills/mine/SKILL.md

mine

Skill292 starsChanged 4 months agoMITView on GitHub

Use only when the user explicitly asks to run, set up, update, re-mine, or deepen Emulo from real local AI coding-session history.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. dcbruck/claude-skills★ 1same name
    2. hurleywgly/skills★ 1same name
    3. Jaxsonman/Crucible★ 0same name
    4. wulfmeister/nookplot-bot★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    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. Very specific:

    Only when the user explicitly asks for a quick preview, run preflight and prepare with --preview.

    line 12
  2. Very specific:

    Run one fast worker for each uncached selected segment.

    line 14
  3. Very specific:

    Run one strongest-available reducer over only the validated reports and the combined reducer contract.

    line 16
  4. Distinctive:

    Every prepared mode requires explicit approval of its displayed plan.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Emulo mine

Mine only real user-authored .jsonl sessions. Never synthesize a profile from rules files, memory, or a typed self-description.

  1. Resolve EMULO_PY to emulo.py two directories above this skill, falling back to ./emulo.py only in a direct checkout. Confirm Python 3 exists.
  2. The full-history quality default reads all eligible history. Run read-only python "$EMULO_PY" plugin preflight, show valid sessions, post-dedupe source tokens, selected source tokens, cache hits, planned worker calls, and planned reducer calls, then wait for explicit cost approval before model work.
  3. Only when the user explicitly asks for a quick preview, run preflight and prepare with --preview. Say this exactly before approval: Quick preview creates a starter profile from selected history, not the full profile. Never call preview the default, the full profile, or equivalent in quality to full-history mining.
  4. Retain the displayed approval_hash. Run python "$EMULO_PY" plugin prepare --approved-plan-hash HASH with the exact approved mode. If the hash changed, show the new plan and obtain approval again. Retain the exact run_id, selected segment/report paths, and pack_path.
  5. Run one fast worker for each uncached selected segment. Each reads only its segment and the per-segment contract in MINING_PROMPT.md, writes its assigned JSON report, and runs the read-only plugin validate-report command until accepted.
  6. Cache each accepted report with plugin cache-report; stop on rejection.
  7. Run one strongest-available reducer over only the validated reports and the combined reducer contract. It writes the complete assigned pack and self-validates with plugin validate-pack.
  8. Activate only the validated pack with plugin activate, then run plugin status and render the card. Report active version, domain states, selected source tokens, actual worker/reducer passes, cache reuse, and targeted-deepen instructions.

Every prepared mode requires explicit approval of its displayed plan. Installation itself scans no logs and schedules zero mining calls. An identical update schedules zero additional Emulo mining calls, although the host task still has normal interaction overhead.

Adaptive receipt/scout stages are experimental and excluded from the Plugin release path. Run --stage A only when a developer explicitly requests experimental adaptive-recall testing; never select it automatically or use it for release calibration.

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.