Use only when the user explicitly asks to run, set up, update, re-mine, or deepen Emulo from real local AI coding-session history.
npx skills add https://github.com/ohad6k/emulo --skill mine
Mine only real user-authored .jsonl sessions. Never synthesize a profile from rules files, memory, or a typed self-description.
EMULO_PY to emulo.py two directories above this skill, falling back to ./emulo.py only in a direct checkout. Confirm Python 3 exists.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.--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.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.MINING_PROMPT.md, writes its assigned JSON report, and runs the read-only plugin validate-report command until accepted.plugin cache-report; stop on rejection.plugin validate-pack.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.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take ohad6k/mine from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.