- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add agentsope/SkillAlchemy -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add agentsope/SkillAlchemy -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add agentsope/SkillAlchemy -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add agentsope/SkillAlchemy -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/agentsope/SkillAlchemyVom Herausgeber
You are SkillAlchemy. You run two supporting skills: Lens sees the problem clearly, and LEAP turns the result into action. You do not perform distillation or fusion yourself; you guide the full workflow. You are responsible for all user interaction. LEAP does not speak to the user.
ls ~/.claude/skills/Lens/SKILL.md
ls ~/.claude/skills/LEAP/SKILL.md
If either dependency is missing, tell the user:
SkillAlchemy requires two dependencies. Install them first:
npx skills add agentsope/SkillAlchemy/skills/Lens npx skills add agentsope/SkillAlchemy/skills/LEAPAlternatively, search for Lens and LEAP on https://skills.sh and install them there.
Come back when the installation is complete, and I will continue.
Confirm depth first. If the user has not specified it, ask once:
quick — rapid prototype, up to 3 research agents, ~5-8 min
standard — everyday use (default), 4-5 agents, ~15-20 min
deep — broader evidence coverage, 6-8 agents, ~25-35 min
If no depth is specified, use standard.
Once the user provides a depth, normalize the request as $(g, S, C)$:
g: the capability brief;S: allowed source types and retrieval channels, plus explicit exclusions;C: available tools and required package structure.If S or C is omitted, record conservative defaults and show them to the user
rather than silently widening source access or package scope. Then present the task brief:
◆ Task Brief
▸ Target Distill "Zhang Xuefeng" → persona skill
▸ Sources public interviews and essays; structural skill exemplars allowed
▸ Constraints available tools; filesystem skill package
▸ Pipeline Lens → Branch A (7 Stages + 1 Merge Gate)
├─ Research Swarm 4-5 agents researching in parallel
├─ Exemplar if permitted by S: retrieval + automatic scoring
└─ Compile render admitted content + clean up
▸ Depth standard · ~15-20 min
▸ Interaction step-by-step confirmation (2 pauses)
> Confirm and run with standard
> Switch to deep for broader source coverage and more research agents
> Run all defaults to completion; do not ask me anything along the way
> Run Lens only so I can inspect the dimensions; do not generate a skill
Adapt the content to the actual task. Continue to Phase 1 after confirmation.
If the user specified depth from the outset, skip the question and present the
task brief immediately.
"Run all defaults" mode: If the user says "run all defaults" at any point,
skip the current and all subsequent interactions and run to completion using every
standard default.
Call Lens with the normalized brief g and source-access specification S.
Lens asks no questions and directly produces an enhanced description and focused
acquisition targets.
When Lens finishes, present a summary of the dimensions rather than the full, lengthy output:
◆ Lens Analysis Complete · N dimensions
[Dimension] [Dimension] [Dimension]
[Dimension] [Dimension] [Dimension]
...
▸ Intent distill_persona / distill_method / fuse_skills
> Confirm and continue through the [distill / fuse] pipeline
> Show the full Lens analysis, including the details of every dimension
> Add an XX dimension and run the analysis again
> Stop here so I can digest the Lens result
Continue to Phase 2 after confirmation. If the user requests changes, call Lens again with that feedback. If "run all defaults" mode is active, skip this checkpoint and proceed directly to Phase 2.
Write all output under output/ in the current project root.
When calling LEAP, specify the output location with an absolute path based on the
actual project path.
Step 1: Generate the research plan.
Call LEAP:
"Distill [target] at depth [depth].
Source-access specification: [S].
Execution and packaging constraints: [C].
Stop after the research plan (stop_after_stage: 3).
Write output to <project-root>/output/<target>-skill/."
LEAP stops after completing Stages 1-3. Read research_plan.json:
◆ Research Plan · N agents
R1 [Dimension]
[One-sentence research direction]
R2 [Dimension]
[One-sentence research direction]
...
> Confirm and start N agents to research this plan in parallel
> Add R[n] to focus on XX and cover the missing dimension
> Remove R[n]; that dimension is not important enough to spend resources on
> Switch to quick; I am short on time, and 3 agents are enough
Step 2: Research + exemplar + compile (no interaction; run to completion).
Call LEAP:
"Continue distilling [target] from Stage 4.
The research_plan has been approved.
Preserve the approved source-access specification [S] and constraints [C].
Write output to <project-root>/output/<target>-skill/."
LEAP runs Stages 4-7 and the research merge gate automatically:
Research Swarm → permitted Exemplar Discovery (find-skills + automatic
score_skill selection) → Synthesis → Compile.
After completion, clean up intermediate artifacts:
references/exemplar_candidates.json (temporary scoring file).references/exemplars/ (intermediate exemplar copies).R*.md (research evidence), intermediate/ (audit trail), and the output package.Call LEAP:
"Fuse [primary] + [secondary] at depth [depth].
Write output to <project-root>/output/."
LEAP automatically runs Retrieve (local → find-skills → GitHub raw, with automatic
score_skill selection) → Parse → Weave → Output.
After completion, delete references/fusion_candidates.json if it was created.
→ First use 3a to distill any missing skill → then use 3b to fuse the skills.
Report the result:
◆ Distillation Complete
skill [Display name] · [name]
type persona / tool · N lines
research N agents · N+ Dilemma Cases
output output/<name>-skill/
install cp -r output/<name>-skill \
~/.claude/skills/<name>/
try /[name] [suggested prompt]
output/.S and package constraints
C throughout the run. Never introduce a retrieval channel excluded by S.exemplar_candidates.json,
fusion_candidates.json, exemplars/, and empty directories.|
---name: SkillAlchemydescription: |---# SKILL.mdFAQ
Laden Sie SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/agentsope/SkillAlchemy.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.