القائمة
Guide the user through importing a .claude/ directory into loomcycle yaml using the `loomcycle import claude-code` CLI — dry-run first, review the report, then write. Use when the user wants to move Claude Code agents/skills/MCP servers into a loomcycle config.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Configure a loomcycle runtime — providers, model tiers, user tiers, fallbacks, per-agent sampling and context-compaction, environment variables, deployment profiles (brew/in-system, containerized, true sandbox, server, multi-tenant, cloud), filesystem Volumes, the Bashbox in-process sandbox, the Path VFS, chunked-graph Documents, inbound webhooks, and third-party MCP servers. Use when the user wants to set up or tune loomcycle.yaml or its env, pick a deployment posture, wire provider routing/cost-cascades, gate plans, tune decoding (temperature/top_p) or compaction, lock down tool/sandbox/auth, enable or choose between Bash and the Bashbox sandbox (incl. its host-command fallback), name resources with Path, author chunked-graph Documents (and the SQL Memory they require), receive webhooks, or connect external MCP tools.
Diff two loomcycle AgentDef versions by def_id and show what changed in system_prompt, allowed_tools, max_tokens, and other fields. Use when the user wants to compare two versions of a self-evolving agent definition.
Walk through replaying a failed loomcycle run — inspect the failure, adjust the prompt or agent, and re-spawn. Use when a loomcycle run errored or produced a bad result and the user wants to retry with a fix.
Spawn a loomcycle evaluator agent to score the current Claude Code transcript (or a named run) and report the result. Use when the user wants an independent quality/score judgement of work just done via loomcycle.
| name | loomcycle-import-claude-code |
| description | Guide the user through importing a .claude/ directory into loomcycle yaml using the `loomcycle import claude-code` CLI — dry-run first, review the report, then write. Use when the user wants to move Claude Code agents/skills/MCP servers into a loomcycle config. |
| allowed-tools | Bash(loomcycle import claude-code*) Bash(loomcycle validate*) |
Guide the operator through RFC C2's loomcycle import claude-code CLI without
them having to remember its flags. This wraps the CLI, not an MCP tool —
the importer is a loomcycle subcommand.
Steps:
Locate the source. Confirm the path to the .claude/ directory to
import (default ./.claude/). Confirm loomcycle is on PATH (or the
operator's ${user_config.bin_path}).
Dry-run first — always. Run the importer in report mode and show the operator what would be imported before touching any file:
loomcycle import claude-code --from=<path-to-.claude/>
Render the report: agents (+ any v0.12.7 substrate-field heuristics like
# credentials: comments or schedule_def_scopes stubs), skills (flag
multi-file ones), MCP servers (note C1 recipe-library rewrites), skipped
slash commands, and the unmapped fields list. Call out anything lossy —
the importer is loud about it for a reason.
Decide on options with the operator:
--no-recipe-match if they want literal .mcp.json ports instead of
curated C1 recipe rewrites.--emit-recipes (requires LOOMCYCLE_MCP_RECIPES_ROOT) to also write
reusable recipe JSON to the overlay.--skills-dest=<dir> for where SKILL.md files land.Write when they're ready. Re-run with --write (add --force only if
they accept clobbering existing entries), targeting their config:
loomcycle import claude-code --from=<path> --write --diff=<loomcycle.yaml>
Validate the result. Run loomcycle validate <loomcycle.yaml> and
report the outcome. A "no provider resolved" error is expected if the
operator hasn't wired tier→provider→model policy yet — that's a config step,
not an import defect; point them at their user_tiers config.
This skill moves authoring content into loomcycle (the data-movement
direction). It is the counterpart to this plugin's runtime-control commands —
keep the two roles distinct and don't try to push definitions back out to
.claude/ (there is no reverse export).